If DLL is obsolete, how to manage different modules?

[Guest]

if I have several modules, say Inventory, Order Processing
and General Ledger in my system.
Each module is a window applicatiion.
Each becomes a project.
If DLL is obsolete, how do I call them after login?
How do I manage them in other words?

 

[Herfried K. Wagner [MVP]]

if I have several modules, say Inventory, Order Processing
and General Ledger in my system.
Each module is a window applicatiion.
Each becomes a project.
If DLL is obsolete, how do I call them after login?

What do you mean with "DLL is obsolete"?

 

[Guest]

When I read web sites of Visual Studio .Net 2005 beta,
perhaps the term "obsolete" is too strong,
Can I say that VB.NET will not create DLL programs?

 

[Cor Ligthert]

Herfried,

I got the idea that I am the only one of the regulars from this newsgroup
who answers Combobox questions.

It is not true, by instance Ken and Jay don't avoid those. However when I
checked it at Google, I saw that you don't do that in a way you answer all
the other messages.

Any reason?

Cor

 

[Herfried K. Wagner [MVP]]

Say if you have many vb.net window applications.
After user logins, user can call different window applications
as user wants.
How do you implement it?

\\\
System.Diagnostics.Process.Start("C:\Foo.exe")
///

I am not sure if this is what you are after.

 

[pc leung]

I am just learning how to write VB.NET.
If each window application is a DLL, after login, user call a DLL to his
wanted
window application. If each window application is EXE, then it can be called
by double-clicked. It will be dangerous.

How will vb.net handle this dynamically?
For example, sometimes this client buys more modules,
while other clients only buy one module.
Say each module is a window application or another.
I am very new to vb.net.
What is the common way of handling this?

 

[Herfried K. Wagner [MVP]]

I am just learning how to write VB.NET.
If each window application is a DLL, after login, user call a DLL to his
wanted
window application. If each window application is EXE, then it can be called
by double-clicked. It will be dangerous.

How will vb.net handle this dynamically?
For example, sometimes this client buys more modules,
while other clients only buy one module.
Say each module is a window application or another.
I am very new to vb.net.
What is the common way of handling this?

Maybe sort of plugin mechanism is a good choice:

<URL:http://dotnet.mvps.org/dotnet/samples/codingtechnique/downloads/PlugIns.zip>

 

[pc leung]

Thank you HerFried

There are two directires: Interface and LateBinding.
Do I need both?

 

[Herfried K. Wagner [MVP]]

There are two directires: Interface and LateBinding.
Do I need both?

No. I would take a closer look to the solution with the interface. The
other sample is only a demonstration of late binding.