16,012,759 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View .NET questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by dalkeeper (Top 7 by date)
dalkeeper
23-Jul-14 9:26am
View
Installing from this new version now gives me the Repair or Replace dialog, no matter if the version is newer or not. I Can select remove and run it again to get the final result I need, but how can the installer be told to automatically remove the old version then install the new one?
Thanks again for your help!
dalkeeper
23-Jul-14 9:23am
View
Think I found the culprit. There was a folder in my solution working folder called Install, which contained a 'applicationnameinstall.vbproj'. Even though I would have expected that the 'Find in Files' feature would have found this, it had the 1.5.2 string in it. I think this may have been created when I was trying to figure out what the 'Click Once' installation option was all about, but in any case, deleting it and the other 2 files in this folder (autorun.inf and WiRunSQL.vbs) allowed me to rebuild an application.msi with the correct version in it.
dalkeeper
23-Jul-14 9:08am
View
Thanks for the input but I don't understand how or where to apply this in my solution. The thread at the link seems to apply to the Wix 'control language' and doesn't look anything like the format of assemblyinfo.vb. Is there somewhere else in my VB solution that I need to look?
dalkeeper
23-Jul-14 9:00am
View
Brute force applied - I manually changed that embedded version in the application.msi file to 2.0.0, and the installer ran giving me the options to Repair or Replace the application. I chose Repair, and it appeared to perform an install, but the version showing in "Programs and Features" still shows 1.5.2. I ran it again, and selected Remove, then ran again, and it upgraded the product code.
dalkeeper
23-Jul-14 8:34am
View
Here's an interesting thing - I brought the application.msi file into a hex editor and found the string "1.5.2ProductVersion" in there just after the product code.
VSDAllowLaterFrameworkVersionsVSDNETCFGVsdLaunchConditionsVSDCA_VsdLaunchConditionsNOT InstalledxxxxxxProductNameProductCode{xxxxxxxxxxxxxxxxxxxxxxxxxxxx}1.5.2ProductVersioncompany nameManufacturerARPCONTACT1033ProductLanguagePREVIOUSVERSIONSINSTALLEDSecureCustomPropertiesNEWERPRODUCTFOUNDPREVIOUSVERSIONSINSTALLED;NEWERPRODUCTFOUND[VSDVERSIONMSG]ERRCA_CANCELNEWERVERSIONNEWERPRODUCTFOUND AND NOT Installed[VSDUIANDADVERTISED]ERRCA_UIANDADVERTISEDProductState=
Does this shed any light on the cause?
dalkeeper
22-Jul-14 23:54pm
View
Deleted
Thanks Sergey,
In the file AssemblyInfo.vb I had the lines:
<assembly: assemblyversionattribute("2.0.0.*")="">
<assembly: assemblyfileversionattribute("2.0.0.0")="">
which had to have been put there by the properties settings, but no AssemblyInformationalVersion. So I added that and now have:
<assembly: assemblyversionattribute("2.0.0.0")="">
<assembly: assemblyfileversionattribute("2.0.0.0")="">
<assembly: assemblyinformationalversion("2.0.0.0")="">
But, no joy. Still, the installer fails to remove the previous version (not very gracefully or informatively either), and the uninstaller still shows version 1.5.2. I cannot understand where it would get that version since I can't find it with "find in files".
dalkeeper
22-Jul-14 23:53pm
View
Hi, Sergey,
In the file AssemblyInfo.vb I had the lines:
[assembly: assemblyversionattribute("2.0.0.*")]
[assembly: assemblyfileversionattribute("2.0.0.0")]
which had to have been put there by the properties settings, but no AssemblyInformationalVersion. So I added that and now have:
[assembly: assemblyversionattribute("2.0.0.0")]
[assembly: assemblyfileversionattribute("2.0.0.0")]
[assembly: assemblyinformationalversion("2.0.0.0")]
But, no joy. Still, the installer fails to remove the previous version (not very gracefully or informatively either), and the uninstaller still shows version 1.5.2. I cannot understand where it would get that version since I can't find it with "find in files".
Show More