The template itself knows nothing about the type of database to which its connected. The template merely takes the database meta-data reported by MyGeneration and uses it to create outputs (.cs and .xml files) based on that meta-data.

If you’re having troubles using it with ORA11g then I would say that’s more a question for the MyGeneration forum. Sorry I cannot be more helpful~!

Good luck,

-Steve B.

Any suggestions?

MArk B.

I have a problem with MyGeneration templates.I was using this since 2 weeks but suddenly it giving me following error when I am executing.

Executing: DNN Controller C#
ERROR: [Zeus.ErrorHandling.ZeusRuntimeException] - Template Runtime Exception
- Canceled Template execution: DNN Controller C#

Thanks in advance…

I’m glad you were able to find value in the screencast series; thanks for the feedback!

We don’t really use the template-driven code-gen-the-DTO approach much any more so I have to confess to not having kept the templates up-to-date as NHibernate has moved forward into other capabilities and made minor changes that may invalidate the MyGeneration template(s) that were demonstrated in the screencasts.

That said, I know that a lot of the viewers of the screencasts DID continue to use the template-based code-gen approach and to my knowledge the change you mention that declares ALL of the public surface area of the class as ‘virtual’ is the only change that was required to adapt the template for NH 2.x. Given this, I frankly think you’re safe in proceeding to use that approach with your application.

For some background on how my views on template-driven code-gen have changed, see this post…

http://unhandled-exceptions.com/blog/index.php/2008/10/04/the-four-stages-of-object-relational-mapping-a-progression/

All that said, if you are practicing DB-first development (either because you have a legacy database to support or because that’s the level of complexity appropriate for your solution), the template-based DTO-gen approach has worked just fine for me on many applications in the past with great success so I wouldn’t worry about proceeding in that direction if its a good fit for your project.

Best of luck~!

-Steve B.

My company is just starting out with NHibernate and I’d like to thank you for your screencast series, which I have found invaluable in getting up to speed.

I just wanted to ask about the MyGeneration template you included in the source code.

My company has decided to go with the latest version of NHibernate, which left as is does not work with the MyGen template provided. Primarily my problems were with the IsDeleted, IsChanges and Clone methods not being virtual. This was easy enough to fix by editing the template.

My concern is that I’ll further along in the development cycle and discover more problems which are not so easy to fix.

I was wondering whether you had an updated version of the template that is NH 2 compatible, or if you knew of one out there?

Richard

Without the DB or more details its hard to know for certain, but my several ideas go like this:

* SQL Server 2008 introduced (finally!) correct support for schemas in SQL Server; its entirely likely that the MyGeneration template doesn’t take that into consideration since they were built for SQL 2005 where schema support was more…lets’ say “inconsistent”

* ensure all your tables are in the same schema and see if that helps

* try to revert your DB to SQL server 2005 and see if that helps

Failing any of that, if you want to send me a SQL script from which I can construct your DB along with the MyGeneration template you are using, I’d be glad to put it on my list of things to look into when I get a moment to breath (no promises when that will be).

HTH,

-Steve B.

Just found this blog. Great resource, but I’m having a little trouble adapting this lesson to my own needs. I have a ManyToMany relational table in my database (SQL Server 2008) but MyGeneration doesn’t seem to be picking it up as such. If I exclude it from the mapping manually, Visual Studio chokes on the build because the two Classes (tables) that are joined through that foreign table are expecting there to be a namespace for it.

The foreign table has only two columns, each are set as foreign keys from their respective sources. The proper foreign key relationships are defined in the DB. Not sure what else I’m missing. Any insight would be appreciated.

Thanks.