Let's say I make 4 plug-ins: A, B, C, and D. And for the purposes of this discussion, how about I put in some versions:
A: 4.0
B: 1.3
C: 2.9
D: 0.5
And let's say, I'm about to release version 0.6 of plug-in D. Now, plug-in D requires version 2.5 or greater of plug-in C and this is a minor update (meaning bug fixes only.) I would like to publish the new version of plug-in D to the web and have VS2005:
1.) Check for updates to all the plug-ins
2.) Tell the user of any new updates and their affect (major/minor) on the system
3.) Provided that the user approves the update, and the user has all of the required versions, installs the new version for the user.
What is the best way to do this Should I make an update plug-in Is there already something canned for this kind of thing
Web Based Plug-in publishing/updates
johtib
When you say plug-in, do you mean an Add-in for Visual Studio, or a component model for your own program
If you need to enable updating your Add-in for Visual Studio, you can use a URL in place of a filename in the .Addin file, and when the user is connected to the internet the component will be downloaded off the web as necessary and the .NET loader should find and download the latest version.
Craig