Hi,
You may try to apply the CLSCompliant attribute to the assembly containing
the VB .NET component and see what the compiler complains about...
In general, I think there should be no problem with constants. Have you also
checked the VB .NET component with the Object Browser? Probably it's just
IntelliSense that cannot see the constants?
--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE
"W1ld0ne [MCSD]" <W1*******@hotmail.com> wrote in message
news:e5*************@TK2MSFTNGP12.phx.gbl...
We are writing a C#.net component that uses a VB.net component, that has a
couple of public const's in it, but C# chooses not to see them. What's up
with that. The only way we can get it to work is to use public variable...
?!?
Anyone have any ideas on that?
Thanks
David Taylor