Help with redesign of VB6 modules

[MK]

Hi,

I'm currently looking into redesigning existing VB6 modules before I
port them to VB.NET and would like oppinions of whether to go with
classes or seperate class libraries (dlls).

There are currently 297 existing modules in the application I'm
working on. The majority are an interface to middleware services,
passing data back and forth from the front end. Any design suggestions
for porting to VB.NET is much appreciated.

Regards,

Michael

[Cor Ligthert [MVP]]

Certainly not all seperate class libraries everytime in a dll (assembly).
However you can put them in seperate namespaces to get them organised.

http://msdn2.microsoft.com/en-us/lib...za(VS.80).aspx

Cor

"MK" <mi*************@yahoo.comschreef in bericht
news:11**********************@i13g2000prf.googlegr oups.com...

Hi,

I'm currently looking into redesigning existing VB6 modules before I
port them to VB.NET and would like oppinions of whether to go with
classes or seperate class libraries (dlls).

There are currently 297 existing modules in the application I'm
working on. The majority are an interface to middleware services,
passing data back and forth from the front end. Any design suggestions
for porting to VB.NET is much appreciated.

Regards,

Michael

[Mr. Arnold]

"MK" <mi*************@yahoo.comwrote in message
news:11**********************@i13g2000prf.googlegr oups.com...

Hi,

I'm currently looking into redesigning existing VB6 modules before I
port them to VB.NET and would like oppinions of whether to go with
classes or seperate class libraries (dlls).

There are currently 297 existing modules in the application I'm
working on. The majority are an interface to middleware services,
passing data back and forth from the front end. Any design suggestions
for porting to VB.NET is much appreciated.

I would suggest you come up with a Framework of base classes/objects that
your other classes/objects can be derived from.

You can gain that knowledge by getting the CSLA Book for VB Business Object
and read it, put the CSLA Framework together to understand a framework, and
put the project together to use the CSLA Framework.

Now, it's not about implementing that CSLA Framework in your solution. It's
about learning from that CSLA Framework to help you make your own
classes/objects for a viable Oops solution.

http://www.lhotka.net/Article.aspx?i...b-e0059cc82ee7

[MK]

Thanks for the info it's a good start.