J
jimfollett1 via DotNetMonster.com
Hey all,
I was wondering if you could put me out of my misery (hopefully, not literaly)
..
I am currently trying to port some VB6 code to VB.NET because of a possible
significant performance improvement on a very large simulation based system.
All my variables are currently encapsulated in public UDTs. If I could
access these COM UDTs from a .NET dll, I will be sorted for porting the
important engine of the system without having to change any VB6 GUIs. I got
through the quagmire that is CCW (Com Callable Wrappers) and have a working .
NET dll with respect to accessing the .NET dll from VB6, but can't seem to
pass my UDTs from COM to .NET. They are complex multi-tiered, nested UDTs
within UDTs.
The question: can UDTs be passed (marshalled) from COM to .NET? If not,
should I scrap the UDTs, create a .NET structure or class and instantiate
that within COM in the first place?
cheers,
James
I was wondering if you could put me out of my misery (hopefully, not literaly)
..
I am currently trying to port some VB6 code to VB.NET because of a possible
significant performance improvement on a very large simulation based system.
All my variables are currently encapsulated in public UDTs. If I could
access these COM UDTs from a .NET dll, I will be sorted for porting the
important engine of the system without having to change any VB6 GUIs. I got
through the quagmire that is CCW (Com Callable Wrappers) and have a working .
NET dll with respect to accessing the .NET dll from VB6, but can't seem to
pass my UDTs from COM to .NET. They are complex multi-tiered, nested UDTs
within UDTs.
The question: can UDTs be passed (marshalled) from COM to .NET? If not,
should I scrap the UDTs, create a .NET structure or class and instantiate
that within COM in the first place?
cheers,
James