Deployment of already installed Appllication in .NET.
-
I have installed my application which is built in C#.NET in the client machine. I have used Set-Up Project for this. After then i have done slight modifications to my application and again i tried to reinstall the application. But it is giving the message like 'Another version of this project is already installed.Installation of this version cannot continue.To configure or remove the existing version of this product, Use Add/Remove Programs on the Control Panel'. Is there any way other than uninstalling and again installing the application. Mahesh Dara.
-
I have installed my application which is built in C#.NET in the client machine. I have used Set-Up Project for this. After then i have done slight modifications to my application and again i tried to reinstall the application. But it is giving the message like 'Another version of this project is already installed.Installation of this version cannot continue.To configure or remove the existing version of this product, Use Add/Remove Programs on the Control Panel'. Is there any way other than uninstalling and again installing the application. Mahesh Dara.
Assuming that you didn't break any existing components and you didn't introduce any new components that aren't compiled into the assembly, you don't need to reinstall the application, just copy the new files over the old ones. If you have to use a setup project for some reason, you need to build the original setup project in a way that identifies that it can be updated and then create the subsequent releases as update packages. I know this is possible with installshield... I'm betting it works when you create setup projects as well. Otherwise, yes, you have to uninstall it and re-install it. What a piece of work is man, how noble in reason, how infinite in faculties, in form and moving how express and admirable . . . and yet to me, what is this quintessence of dust? -- Hamlet, Act II, Scene ii.
-
I have installed my application which is built in C#.NET in the client machine. I have used Set-Up Project for this. After then i have done slight modifications to my application and again i tried to reinstall the application. But it is giving the message like 'Another version of this project is already installed.Installation of this version cannot continue.To configure or remove the existing version of this product, Use Add/Remove Programs on the Control Panel'. Is there any way other than uninstalling and again installing the application. Mahesh Dara.
I had this problem when I was using wildcards in the AssemblyVersion. The way I solved it was as follows: 1. Created a class where the system constants are kept.. namespace myCo.Constants { public class SystemConstants { ... public const string SystemVersion = "2004.03.27.02"; ... } } 2. Included the class in every AssemblyInfo file in the solution, and used the constant in the AssemblyVersion... ... using myCo.Constants; ... ... ... [assembly: AssemblyVersion(myCo.Constants.SystemConstants.SystemVersion)] ... ... 3. In the setup project for the app, I use the version number, converted as follows: SystemVersion in Code Version In Setup 2004.03.27.02 04.03.2702 When the version is changed in the setup project, the system will give you a warning that the ProductCode and PackageCode should also be changed, and if you answer "Yes", the system will update them for you. Also I have the "DetectNewerInstalledVersion" and "RemovePreviousVersions" set to true, that way the new version deletes any previous versions, but does not allow an older version to be installed. Once we went to this procedure, I have never had a single problem with installs. In my app, every time a version is released, a permanent copy of all the source is then archived, and the SystemVersion constant is updated accordingly, so is the setup project Version. Since the SystemVersion is in one place, it is easy to modify all of the assemblies, we have multiple setup projects, which are a bit of a pain, since I do them manually, but I do remember seeing an article here in CP that does the setup projects. Hope this helps...
-
I had this problem when I was using wildcards in the AssemblyVersion. The way I solved it was as follows: 1. Created a class where the system constants are kept.. namespace myCo.Constants { public class SystemConstants { ... public const string SystemVersion = "2004.03.27.02"; ... } } 2. Included the class in every AssemblyInfo file in the solution, and used the constant in the AssemblyVersion... ... using myCo.Constants; ... ... ... [assembly: AssemblyVersion(myCo.Constants.SystemConstants.SystemVersion)] ... ... 3. In the setup project for the app, I use the version number, converted as follows: SystemVersion in Code Version In Setup 2004.03.27.02 04.03.2702 When the version is changed in the setup project, the system will give you a warning that the ProductCode and PackageCode should also be changed, and if you answer "Yes", the system will update them for you. Also I have the "DetectNewerInstalledVersion" and "RemovePreviousVersions" set to true, that way the new version deletes any previous versions, but does not allow an older version to be installed. Once we went to this procedure, I have never had a single problem with installs. In my app, every time a version is released, a permanent copy of all the source is then archived, and the SystemVersion constant is updated accordingly, so is the setup project Version. Since the SystemVersion is in one place, it is easy to modify all of the assemblies, we have multiple setup projects, which are a bit of a pain, since I do them manually, but I do remember seeing an article here in CP that does the setup projects. Hope this helps...
Thanks for your suggestion. If i change the version no. of the setup project everytime when i rebuild then it's working fine i.e.,it is not giving any msg and it's reinstalling the whole application. Upto here fine.but is there anyway to automate the process of changing the version number of setup project everytime when i rebuild.