getting wix, app and choco version in line. about chocolateygui HOT 6 CLOSED

Not sure about you, but typically, we handle this with a CommonAssemblyInfo.cs file, and the version number in this file is updated each build, and is referenced everywhere that needs it. That way, you don't have to update the same information in multiple places.

from chocolateygui.

Never had to deal with this so no idea. How do you reference it.

from chocolateygui.

The CommonAssemblyInfo.cs is essentially a "partial" file. So you create a link to the common file, and remove the AssemblyInfo and AssemblyFileVersion from the AssemblyInfo.cs file. When it compiles, it takes the Version numbers from the Common file. You can do a similar thing with the wix project. Happy to make these changes, but I have asked Xavier a question related to this, so going to hold off until I hear from him about it.

from chocolateygui.

Okay, looks like this is pretty much complete. Now, we just need to decide on how we are controlling the version number. The build script, at the minute, hard codes the version into the default.ps1 file, however, there is a way to retrieve the build number from the git repo using tags and commit history (that is the code that is currently commented out in that file). This is quite a "clean" way of doing it, but it would need some setup and testing, so need some feedback as to whether we want to proceed down this route.

Can you let me know what you think?

from chocolateygui.

I have played with this, and I "think" that I have it working, just running a full build on MyGet just now.

Used this:

http://wptheming.com/2011/04/add-remove-github-tags/

as a reference.

from chocolateygui.

Woot, it works!

from chocolateygui.