Windows Develop Bookmark and Share   
 index > ClickOnce and Setup & Deployment Projects > Deployment project version using an AssemblyInfo.cs file
 

Deployment project version using an AssemblyInfo.cs file

Hi,

I have a project containing an AssemblyInfo.cs file where the version of the project is, and it is automatically increased during build. I also made a deployment project to install it, but I have the enter the version number manually. Is there a way to make the deployment project take the version from my other project so that they are both to the same version number without entering the deployment project version number manually?

Any help is appreciated!
Mathieu07  Monday, December 01, 2008 6:59 PM
No, there isn't. Typical installs might install many, many files, so it doesn't really help much to set the version of the setup from the version of one of the binaries that's being installed.You are really installing only one file I guess, and that's unusual, IMO.

PhilWilson  Tuesday, December 02, 2008 7:35 PM
No, there isn't. Typical installs might install many, many files, so it doesn't really help much to set the version of the setup from the version of one of the binaries that's being installed.You are really installing only one file I guess, and that's unusual, IMO.

PhilWilson  Tuesday, December 02, 2008 7:35 PM
All of the binaries are sharing the same version number, and that's the version number I wanted to use for the setup. Too bad it can't be done. Thanks for the answer!
Mathieu07  Tuesday, December 02, 2008 9:01 PM

You can use google to search for other answers

Custom Search

More Threads

• Install as Admin... .MSI wants to run *again* for each user
• How to Add publishing information in to c++.net project
• ClickOnce Only One Version
• Improperly Formatted
• config and ClickOnce deployment
• Setup Program Validation Error
• "Could not find File <path>\<filename>.InstallState" error due to first custom action failing and second rolling back
• Running application online
• Web deployment error w/ setup.exe
• Problems with MIME settings at the hosting provider