Changing files will need new installer?

[j_alza]

Hello,

I going to make some changes in my solution. Until now I had files from 3 projects added to my installer:

• App.Content Files
  
• App.Localized resources
  
• App.Primary output
  
• ComDll.Content Files
  
• ComDll.Primary output
  
• AnotherDll.Localized resources
  
• AnotherDll.Primary output
  

Now I want to remove ComDll and add NewComDll, so these will installer files (NewComDll instead of ComDll):

• App.Content Files
  
• App.Localized resources
  
• App.Primary output
  
• NewComDll.Content Files
  
• NewComDll.Primary output
  
• AnotherDll.Localized resources
  
• AnotherDll.Primary output
  

I have configured the installer to uninstall previous versions, setting the parameters in 1. Organize Your Setup: General Information and Upgrade Paths. I have the following questions:

If I use the same installer (removing ComDll and adding NewComDll), when installing the new version, will the installer be able to delete old ComDll files?
Is it better to create a new installer project adding the old one to Upgrade Paths?

Thank you,
Jon.

[NameTooShort]

Hi Jon,

You can use the same project to perform the major upgrade by updating the files and modifying the product code, package code, and version number.
You will still need to create an Upgrade Paths entry to create a proper upgrade.

[j_alza]

Hi kyi, thank you for your help!