Stonkie
Well-known member
- Joined
- Sep 12, 2007
- Messages
- 279
- Programming Experience
- 1-3
Hi everybody,
I have to migrate an application to replace an old dll made in VB.net with a new one made in C#. One namespace is called LoadBoard.DAL, the other one Loadboard.DAL (notice the case difference?). Both dlls having similar class names, this brought hell upon an otherwise smooth operation!
VB.NET names are not case sensitive, so classes with the same names in both namespaces cannot be distinguished by the compiler. This means I cannot reference both dlls at the same time or all the conflicts are brought up. And I definitly cannot migrate the whole application in a one shot caffeine driven weekend. We need to stay buildable while I migrate.
So, is there any way that I can fix this name resolution problem without renaming any of the namespaces? Some kind of switch that says "resolve names as case sensitive for a few months while I migrate" would be awesome!
PS. I know it was a bad idea to write 2 data access layers with the same namespaces (except for the case), but I didn't have a say on it and there's no point dwelling on it now... I just need some kind of quick workaround until we flush the old dll for good when I'm done.
Thanks all for any insight you may provide
I have to migrate an application to replace an old dll made in VB.net with a new one made in C#. One namespace is called LoadBoard.DAL, the other one Loadboard.DAL (notice the case difference?). Both dlls having similar class names, this brought hell upon an otherwise smooth operation!
VB.NET names are not case sensitive, so classes with the same names in both namespaces cannot be distinguished by the compiler. This means I cannot reference both dlls at the same time or all the conflicts are brought up. And I definitly cannot migrate the whole application in a one shot caffeine driven weekend. We need to stay buildable while I migrate.
So, is there any way that I can fix this name resolution problem without renaming any of the namespaces? Some kind of switch that says "resolve names as case sensitive for a few months while I migrate" would be awesome!
PS. I know it was a bad idea to write 2 data access layers with the same namespaces (except for the case), but I didn't have a say on it and there's no point dwelling on it now... I just need some kind of quick workaround until we flush the old dll for good when I'm done.
Thanks all for any insight you may provide
