2009/3/4 Robin Nadeau <[email protected]> > We already have entities, developed in VB .NET, being used by custom > mappers. Those entities were developed with infer on, strict off, and > explicit off, meaning that it would be a pain to convert to C# with most > automatic tools. Also, it would be difficult to convince management that we > should take the time to convert our entities to C# for the only goal of > making it easier to use an O/R mapping tool.
What ? If you like the mapping generation trough MyGeneration download all C# templates and change it for VB. If you have a legacy DB with a legacy entities implementation in VB and now you want use NH, what you should do is write mappings by yourself (at most using something like FNH). -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
