Approach towards patches, updates in Desktop Applications
I would like to create a desktop application for which if changes are made in the customer module, or inventory module I would like to send a patch to clients and not the whole installation.
How could I implement such a thing in VB.NET. Any professionals who have ever followed such an approach.
How could I implement such a thing in VB.NET. Any professionals who have ever followed such an approach.
You will have to split your application into multiple DLLs (one for customer, one for inventory, ...).
ASKER
Yes, emoreau, I have often heard that. But could you tell me where I can find a sample project implemented in such manner. That would really help a lot.
BTW armoghan, I believe thats something new in .NET, but am looking for a simple workout with VB.NET projects.
Thanks.
BTW armoghan, I believe thats something new in .NET, but am looking for a simple workout with VB.NET projects.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have a look at an article I wrote a year ago: http://www.utmag.com/September2003/Page11.asp
ASKER
emoreau I read the page 11 but am still not confident with that approach or havent understood it completely.
armoghan, could u somehow provide me a link where i could see such a project, it could be just two things like Inventory and Supplier. I just want to see how they are linked together. And how this all works through code. Thanks
armoghan, could u somehow provide me a link where i could see such a project, it could be just two things like Inventory and Supplier. I just want to see how they are linked together. And how this all works through code. Thanks
Have you read pages 11 to 15?
Download the example (link on page 15). There is a sample of getting forms from another assembly (a .dll) and displaying it with the main application without having it knowing the existence of external forms at build time. There is also a config file to give the main form names and location of these external forms.
Download the example (link on page 15). There is a sample of getting forms from another assembly (a .dll) and displaying it with the main application without having it knowing the existence of external forms at build time. There is also a config file to give the main form names and location of these external forms.
ASKER
ok, I will look into it. Have downloaded it already. Thanks
Points to emoreau
ASKER
sorry for the delay. been out of station.
Anyways armoghan had the better solution. Thanks emoreau for your expertise also.
Anyways armoghan had the better solution. Thanks emoreau for your expertise also.
see this article for informaiton
http://www.codeproject.com/csharp/PluginsInCSharp.asp