How do I make an application (.exe file) that update the version of another application?
I already made a installer for my application using the Setup Project in VS2008, but this kind of project also allow you to make a update installer?

This update installer would replace the old version of application and would run a script (if it's necessary) to change the database.

Thanks

---

Get a life. Go party!

Hi JobaDiniz,

Once you publish a new version, you don't need to publish .NET Framework prerequisite again since your user has already install the prerequisite from the previous version.

To change updated assembly version, you can right click the assembly project file, in the "Application" tabpage, there is a button named "Assembly Information...", click the button, the popup dialog show you the version number.

If you have anything unclear, please feel free to tell me.

Sincerely,
Kira Qian

---

Please mark the replies as answers if they help and unmark if they don't.

Hi JobaDiniz,

You can put a * to the version number. This document well discuss that
http://msdn.microsoft.com/en-us/library/system.reflection.assemblyversionattribute%28VS.71%29.aspx

The version number has four parts, as follows:
<major version>.<minor version>.<build number>.<revision>

A version number such as [assembly:AssemblyVersion("1.2.*")] specifies 1 as the major version, 2 as the minor version, and accepts the default build and revision numbers. A version number such as [assembly:AssemblyVersion("1.2.15.*")] specifies 1 as the major version, 2 as the minor version, 15 as the build number, and accepts the default revision number. A version number such as [assembly:AssemblyVersion("1.2.*.6")] specifies 1 as the major version, 2 as the minor version, accepts the default build number, and specifies 6 as the revision number.

Sincerely,
Kira Qian

---

Please mark the replies as answers if they help and unmark if they don't.

Hi JobaDiniz,

>I already made a installer for my application using the Setup Project in VS2008, but this kind of project also allow you to make a update installer?

Do you mean you want to update to a new version without uninstalling the current application? If I understood correct, I think the RemovePreviousVersions property is the right one for this question. You can set that property to True. Once you release a new version, you'd remember to upgrade the assembly version and assembly file version. Installer will replace the old assembly with the new one when you install it.

>This update installer would replace the old version of application and would run a script (if it's necessary) to change the database.

I think this can be done with custom action, you can prepare some update script and run it during installation with custom action code.

If I misunderstood you, please feel free to tell me.

Sincerely,
Kira Qian

---

Please mark the replies as answers if they help and unmark if they don't.

I think the RemovePreviousVersions property is the right one for this question. You can set that property to True. Once you release a new version, you'd remember to upgrade the assembly version and assembly file version. Installer will replace the old assembly with the new one when you install it.

My installer have 250mb, because I set to download the prerequisites from the same path of application, this is, I do not download it from web.
Because of that, if I just change the property RemovePreviousVersion, the update installer will continue having 250mb, and I do not want this, because it's needless.

And how I upgrade the assembly version and assembly file version?

---

Get a life. Go party!

Hi JobaDiniz,

Once you publish a new version, you don't need to publish .NET Framework prerequisite again since your user has already install the prerequisite from the previous version.

To change updated assembly version, you can right click the assembly project file, in the "Application" tabpage, there is a button named "Assembly Information...", click the button, the popup dialog show you the version number.

If you have anything unclear, please feel free to tell me.

Sincerely,
Kira Qian

---

Please mark the replies as answers if they help and unmark if they don't.

I understood, thanks.

Is there a way that the assembly's version is automatically upgraded?
I mean, everytime we build, the version change...

---

Get a life. Go party!

Hi JobaDiniz,

You can put a * to the version number. This document well discuss that
http://msdn.microsoft.com/en-us/library/system.reflection.assemblyversionattribute%28VS.71%29.aspx

The version number has four parts, as follows:
<major version>.<minor version>.<build number>.<revision>

A version number such as [assembly:AssemblyVersion("1.2.*")] specifies 1 as the major version, 2 as the minor version, and accepts the default build and revision numbers. A version number such as [assembly:AssemblyVersion("1.2.15.*")] specifies 1 as the major version, 2 as the minor version, 15 as the build number, and accepts the default revision number. A version number such as [assembly:AssemblyVersion("1.2.*.6")] specifies 1 as the major version, 2 as the minor version, accepts the default build number, and specifies 6 as the revision number.

Sincerely,
Kira Qian

---

Please mark the replies as answers if they help and unmark if they don't.