 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / New Users / September 2005MSI problem / question
I created a .MSI installer with a Setup project in VS.NET (2005) After some update to the code I decided to make a new release and I create a new .MSI. Now when, when I tested my .MSI it didn't install, complaining there was a previous version of the software which prevent it from installing. Although I did check the "RemovePreviousVersion" Is there a way around this very bad user experience? Also going in to the uninstall panel is quite tedious, how do I create an uninstall shortcut in my application's folder? Is this a minor upgrade? If so you need to run the installer with "msiexec /i <name-of-msi> REINSTALL=ALL REINSTALLMODE=vomus". For the user, the easiest thing is if you wrap the msi in a bootstrapper which makes the command line call for them. For the uninstall link, you want "msiexec /x <product-code-of-your-app> Rob > I created a .MSI installer with a Setup project in VS.NET (2005) > After some update to the code I decided to make a new release and I create a [quoted text clipped - 6 lines] > Also going in to the uninstall panel is quite tedious, how do I create an > uninstall shortcut in my application's folder? Thanks Rok, I'll try something like that..  SignatureIf you're in a war, instead of throwing a hand grenade at the enemy, throw one of those small pumpkins. Maybe it'll make everyone think how stupid war is, and while they are thinking, you can throw a real grenade at them. Jack Handey. > Is this a minor upgrade? If so you need to run the installer with > "msiexec /i <name-of-msi> REINSTALL=ALL REINSTALLMODE=vomus". For the [quoted text clipped - 15 lines] >> Also going in to the uninstall panel is quite tedious, how do I create an >> uninstall shortcut in my application's folder? It may be a very bad user experience, but it's a common beta user experience. The purpose of releasing beta software is to find the bugs in it. As a result, one should always expect bugs in beta software. If there were no bugs, it would be RTM software! SignatureHTH, Kevin Spencer Microsoft MVP .Net Developer Neither a follower nor a lender be. >I created a .MSI installer with a Setup project in VS.NET (2005) > After some update to the code I decided to make a new release and I create [quoted text clipped - 6 lines] > Also going in to the uninstall panel is quite tedious, how do I create an > uninstall shortcut in my application's folder? I don't quite get it?!?! I'm just trying to make the install/upgrade process of my apps as smooth as possible here... SignatureIf you're in a war, instead of throwing a hand grenade at the enemy, throw one of those small pumpkins. Maybe it'll make everyone think how stupid war is, and while they are thinking, you can throw a real grenade at them. Jack Handey. > It may be a very bad user experience, but it's a common beta user > experience. The purpose of releasing beta software is to find the bugs in [quoted text clipped - 11 lines] >> Also going in to the uninstall panel is quite tedious, how do I create an >> uninstall shortcut in my application's folder? >I don't quite get it?!?! > I'm just trying to make the install/upgrade process of my apps as smooth > as possible here... You can file a bug report: http://lab.msdn.microsoft.com/productfeedback/ As for making the install/upgrade process of your apps as smooth as possible, you have basically 2 choices: 1. Wait until November and get the RTM version. (Keep an eye out for any interim releases that might fix your issue) 2. Use Visual Studio.Net 2003. When it comes to beta software, it's always "caveat emptor." ;-) SignatureHTH, Kevin Spencer Microsoft MVP .Net Developer Neither a follower nor a lender be. >I don't quite get it?!?! > I'm just trying to make the install/upgrade process of my apps as smooth [quoted text clipped - 15 lines] >>> Also going in to the uninstall panel is quite tedious, how do I create >>> an uninstall shortcut in my application's folder? > 1. Wait until November and get the RTM version. > (Keep an eye out for any interim releases that might fix your issue) > 2. Use Visual Studio.Net 2003. > > When it comes to beta software, it's always "caveat emptor." ;-) Well I don't think it's a beta problem. I already used Setup project a while ago and IIRC they already displayed this exact same problem. I'm afraid it's not a bug of the MSI file / and/or setup project, but a "feature"; although a rather annoying one. Well, if you checked "Remove Previous Version" I would think it's a bug. but that's just me. SignatureHTH, Kevin Spencer Microsoft MVP .Net Developer Neither a follower nor a lender be. >> 1. Wait until November and get the RTM version. >> (Keep an eye out for any interim releases that might fix your issue) [quoted text clipped - 8 lines] > I'm afraid it's not a bug of the MSI file / and/or setup project, but a > "feature"; although a rather annoying one. > Well, if you checked "Remove Previous Version" I would think it's a bug. > but that's just me. mmhh... right, let be more optimistic, let's post a bug report on the MSDN website! but it was a bug already there in VS2003 IIRC >>> 1. Wait until November and get the RTM version. >>> (Keep an eye out for any interim releases that might fix your issue) [quoted text clipped - 8 lines] >> I'm afraid it's not a bug of the MSI file / and/or setup project, but a >> "feature"; although a rather annoying one. BTW Kevin I had an answer from MS support. It's very simple, I should also change the version number property of the MSI and.. Voila!! > Well, if you checked "Remove Previous Version" I would think it's a bug. > but that's just me. [quoted text clipped - 11 lines] >> I'm afraid it's not a bug of the MSI file / and/or setup project, but a >> "feature"; although a rather annoying one. What did you use to create the MSI. Was it the Disco32 from the Wininstall? Nick > BTW Kevin I had an answer from MS support. > It's very simple, I should also change the version number property of the [quoted text clipped - 15 lines] > >> I'm afraid it's not a bug of the MSI file / and/or setup project, but a > >> "feature"; although a rather annoying one. > What did you use to create the MSI. Was it the Disco32 from the > Wininstall? VS2005 (work with 2003 too), New Project => Setup project There is a Program called Disco32 which is included in the WinInstall software made by Veritas. You can download it for free, or if you want the whole version then you can use the trial version and see how it works. It is very simple, it creates a share where all the msi files and other necessar files will be placed. You first run the Discovery - "Before snapshot" which basically takes a snapshop of your C:/. After that you install the application on your PC, and then you run the After snapshot. It's a logical process, the difference between the After and Before snapshot contanis the MSI file and other directories, files and registry keys that were added / modified to your PC. Use the AD and create an MSI install package and assign it thru the Group Plolicy, pay attention about differences between assigning / publishing the MSI packages. The MSI part is all self explainable. You must know Active Directory and Group Policeis to be able to finish the project. Nick > > What did you use to create the MSI. Was it the Disco32 from the > > Wininstall? > > VS2005 (work with 2003 too), New Project => Setup project Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.