Public Variables exposed thru type library in DLL registered for COM interop

Correct me if my nomenclature is off.  We just converted a large VB6 DLL to VB .NET and will be using it in a Visual C++ executable.  When we import the type library in Visual C++, the Global / Public variables in each class are not exposed like they used to be.

Is there any way to have the Public variables exposed through the COM interface like they used to be?  We can’t switch our exe to use managed code (CLR), but any other suggestions are welcome.
bigsteve87Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

VBRocksCommented:
Are you using an Interface in your dll?  I think it may be necessary to expose your methods.

Here's a link that discusses this issue:
http://www.15seconds.com/issue/040722.htm

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.