[omniORB] Managed code in Visual Studio .NET

[Josu Larranaga]

Hello,

I didn't success on the port from VC6 to VC7. I tried to use programs 
compiled on VC7 with a VC6 compiled OmniORB dll,
it had lots of problems on the heap deallocation, some on the ' _var' 
type variable release, some on memory corruption,
tracing omniORB  tcp packages showed errors, problems when more than 16K 
were exchanged,  etc.
I didn't pay much attention to it,  as many sources errors were 
identified. In order work out the problem  you should compile omniORB 
first on VC7.
if you try in usual way you will  get a python.h include definition 
error, so you have better compile python first with VC7. It would be 
nice you could
have python compiled on managed code.

Javier Osa wrote:

>
>	I wish to migrate code from VC6 to VC7 in Visual Studio .NET. My proyect is
>a client DLL (tccedulacli.dll) that gets a reference of ORB server Object
>from nameservice and calls one of his methods.
>
>	I have used a Managed C++ Class Library project because I want to use it
>from NET components.
>
>	This DLL runs fine in VC6 but when it runs under VC7 results in exceptions
>being thrown at run-time ...
>
>".....
>		An unhandled exception of type 'System.TypeLoadException' occurred in
>tccedulacli.dll
>		Additional information: Could not load type omniObjectManager from
>assembly TCCedulaCli, Version=1.0.891.28114, Culture=neutral,
>PublicKeyToken=null.
>....."
>
>	This exception occurs when the constructor of an '_var' type variable of my
>own classes defined in IDL file is called, but doesn`t occurr if the '_var'
>type variable is Object_var.
>	Has someone succeeded with ORB clients from Managed code in VS.NET?
>
>	Thanks
>
>		Xavier Osa
>
>
>_______________________________________________
>omniORB-list mailing list
>omniORB-list@realvnc.com
>http://www.realvnc.com/mailman/listinfo/omniorb-list
>
>