Ok, the problem was inside my main application form where I must tell it to upgrade, all is well.
Just in case others would like to know how I set my Visual Studio 2012 (VS2012) Advanced Installer Project (AIP).
In my VS2012 app main form I added:
Code: Select all
public frmMain()
{
InitializeComponent();
//[b]IsFirstLaunch[/b]is a boolean set to true in settings
if (Properties.Settings.Default.IsFirstLaunch )
{
Properties.Settings.Default.Upgrade();
Properties.Settings.Default.IsFirstLaunch = false;
Properties.Settings.Default.Save();
}
}
The scenario below is ideal if you have many files in your VS2012 project that the 'Build Action' for those files is set to 'Content'.
In AIP Files and Folders:
- I only added my main app exe from my
bin\release folder so I can point shortcuts to it.
- I then created a folder called 'Release' that points to my main project
bin\release folder then made that folder a
Sync folder, I told the folder to
Install folder content into the parent folder and then added some exclusion files and file extensions
as well as excluding my main app exe as it is already included in the deployment package.
Before I create a deployment package:
In VS2012
- I change my build from Debug to Release
- I increase my application assemblies and files version
- I Clean then rebuild my main project
In AIP:
- Under Product Information - Product Details, I increase the Product Version and answer 'Major Upgrade' when asked.
- Under Resources - Files and Folders, I click my Release Sync folder and in the toolbar
Files and Folders Tools, I click the
Refresh button.
I can now build and run my deployment!
FOLLOW US
Get the latest news in Application Packaging