|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
New Version NumberI have a released .NET 2.0 windows application (version 1.0.0.0) that is
written in C#. The solution has a project and a setup project. It works great. I made some tweaks to the application and want to release it as version 1.1.0.0 and have that be the visible identification in Control Panel | Add Change Programs. I can make this change with Orca: build the solution, use Orca to change the version, and then use the output from Orca. What is the recommended way to define the new version (and other solution identifying information) without using Orca? This question was moved to another newsgroup.
Show quote "Thom Little" <t***@tlanet.net> wrote in message news:uWIwwSxwGHA.4256@TK2MSFTNGP06.phx.gbl... >I have a released .NET 2.0 windows application (version 1.0.0.0) that is >written in C#. The solution has a project and a setup project. It works >great. > > I made some tweaks to the application and want to release it as version > 1.1.0.0 and have that be the visible identification in Control Panel | Add > Change Programs. > > I can make this change with Orca: build the solution, use Orca to change > the version, and then use the output from Orca. > > What is the recommended way to define the new version (and other solution > identifying information) without using Orca? > > -- > -- Thom Little -- www.tlanet.net -- Thom Little Associates, Ltd. > -- > > > |
|||||||||||||||||||||||