Hi,
I have been tasked to upgrade a project from VB6 to VB.NET, i have a number
of problems of which most i have now solved but i am still very perplexed by
one problem. The VB6 application has one class whose instance property is
declared as GlobalMultiUse and this class defines properties that are shared
between a number of other applications in use that will soon be converted to
..NET.
The problem is that during initial testing the new class in .NET declared as
Public with a Publi Sub New does not share across other applications.
Example:
ApplicationA (references DLLA which contains the public class)
when ApplicationA runs it sets up some of the properties in DLLA,
gConnection is one of the properties, which is held in a public module.
ApplicationB when it runs "should" return the already set connection string,
however this does not happen.
The corresponding effect is possible and indeed is in use in VB6, my
question is, how can you implement the same functionality in .NET now that
Microsoft (in thier infinite wisdom) has removed the GlobalMultiUse property
of class instancing, has anyone else come across this problem before, and
does anyone know of a workaround.
The end result is that DLLA should behave in the same way as it does in VB6
(as a server for global properties and methods which are shared between
applications), if this is not possible then .NET may not be suitable for the
needs of our client.
Thanks for any help in advance
Neil