R
Ravnø Data
Guest
I am developing a Windows Forms Project including a Setup/deployment project.
Each time, I finish a new version, I
- rebuild and create *.msi file for install, fx pgm_7-0.msi - version 7.0
- save a copy of the project source code
Then I increase all version numbers:
- Assembly version to 7.1
- file version to 7.1
- publish version 7.1 (just in case)
- setup project version 7.1, upgrade productcode
- Setup project properties output file name to pgm_7-1.msi
This has worked fine for years - even through the project has lived in VS2008 -> VS2010 -> VS2013 and now VS2017
But as I went from 7.2 to 7.3 /7.4 it still produces a pgm_7-2.msi.
Looks like the output file name hangs in pgm_7-2.msi no matter what I do.
Any explanation ?
mvh ravnø
Continue reading...
Each time, I finish a new version, I
- rebuild and create *.msi file for install, fx pgm_7-0.msi - version 7.0
- save a copy of the project source code
Then I increase all version numbers:
- Assembly version to 7.1
- file version to 7.1
- publish version 7.1 (just in case)
- setup project version 7.1, upgrade productcode
- Setup project properties output file name to pgm_7-1.msi
This has worked fine for years - even through the project has lived in VS2008 -> VS2010 -> VS2013 and now VS2017
But as I went from 7.2 to 7.3 /7.4 it still produces a pgm_7-2.msi.
Looks like the output file name hangs in pgm_7-2.msi no matter what I do.
Any explanation ?
mvh ravnø
Continue reading...