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.

On Tue, Mar 3, 2009 at 7:35 PM, Ryan Rinaldi <[email protected]> wrote:

> VB can call C# code.  I'm not sure I understand your backwards
> compatibility requirement.
>
> -Ryan Rinaldi
> blog: http://ryanrinaldi.com
>
>
>
> On Tue, Mar 3, 2009 at 10:53 AM, Robin Nadeau <[email protected]> wrote:
>
>> It needs to be VB for backwards compatibility.
>>
>>
>> On Tue, Mar 3, 2009 at 11:45 AM, Brandon Beheens <
>> [email protected]> wrote:
>>
>>> Why does your mapping Nh project have to be vb?  They are really just
>>> poco classes.  Have you looked at fluent nhinernate?
>>>
>>> Brandon BehrensPrinciple Software Engineer
>>> TidalTV
>>> Http://www.TidalTV.com
>>> [email protected]
>>> (512) 659-7171 (c)
>>>
>>> On Mar 3, 2009, at 10:27 AM, Robin Nadeau <[email protected]> wrote:
>>>
>>> I'm trying to find a tool for generating mapping files and objects from
>>> the database, I've only found mygeneration, however I cannot find any
>>> mygeneration template that generates VB.NET code and mapping files for
>>> NHibernate 2.0. Anybody have suggestions?
>>>
>>> --
>>> Robin Nadeau, B.Eng.
>>> Software Developer
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Robin Nadeau, B.Eng.
>> Software Developer
>>
>>
>>
>
> >
>


-- 
Robin Nadeau, B.Eng.
Software Developer

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to