- Like most people, I didn’t realize that the VERSIONINFO resource was only a 16-bit number. Consequently, using my GenerateAssemblyFileVersionTask in the brand spanking new year produces date numbers of 70103, which will produce a CS167 compiler error. To continue to use a “date” like format, I updated VersionFile.cs (in Wintellect.Build.Tasks) to use a scheme like the Visual Studio team uses, 01MMDD. Since it was easy enough, I tweaked the code to account for the year change so January 3, 2008 is 020103. To keep versioning straight, I also bumped up the point release to .1.
- Fixed the install to uninstall the two previous versions and properly check for newer versions.
We deliver solutions that accelerate the value of Azure.
Ready to experience the full power of Microsoft Azure?
Start Today