i suspect this is a bit of a silly question - but it has had me stumped for days!

I have two MSIs - and older one and a newer one.

Making sure all was correct - i manually went ahead and created an MSP. Which seems to work fine and was created with no errors.

However when trying to run the new MSP - it just takes me to the MSIs "Repair/remove" screen - i assumed there may be some screen i will need to add - and hit the repair button. However when i checked afterwards - the test.txt did not update.

The MSI was created using VS2003.net - and i created just a default MSI. What i suspect is that VS2003.net does not have some kind of system for dealing with patches built into the default settings.

I am curious if there is a large - rather obvious step i have missed out along the way to create the MSI to handle updates.

Can anyone give me any advice on this? I suspect its just a case of adding a few extra dialogs which handle the MSP - however i cannot seem to find a way of making the MSI within VS2003.net to setup the MSI to handle patches.

Any advice? Is what i am attempting to do just not possible?

thanks in advance!
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity



hey ik praat nederlands geen frans en ook geen inglish dus wil k de iets zegge ja eh ik heb en hacker op msp en k wil hem hacke hoe moet d

Answered 05/21/2014 by: martina stoessel
White Belt

Please log in to comment