Why does my installer not work?

  • Thread starter Thread starter Hari
  • Start date Start date
H

Hari

Hi,

I need to create an MSI for my app. I've followed the link from
msdn.
http://msdn2.microsoft.com/en-us/library/aa446504.aspx . But when i
run the installer it shows that the app has been successfully
installed, but i can see my app nowhere. Then i changed the path
variables in the installer class to point to the app. This has made
the situation even worse. Now i'm even unable to uninstall the app. It
shows a warning saying ' The directory is not empty, and an error
occured during uninstallation.' What could be wrong? I would
better like to post the sample app if theres any possibility. I'm
totally struck. PLZ HELP!


- Hari
 
but i can see my app nowhere.

What do you have "Folder" set to for the item "Primary output from (app
name)"?
Have you looked in \Program Files for a folder with the same name as your
app?
Are the files there but no icons?
shows a warning saying ' The directory is not empty, and an error
occured during uninstallation.'
Click to expand...

I'd just use Active Sync to browse the device's disk and delete the files
using that.



Pete
 
I have just used this to successfully create a MSI for a Windows Mobile app.
However, I did not follow the script exactly since I think there is a
problem with it at the point where it says to add a system folder.

That would be at Figure 12.

What I did was after adding the system folder was to add a subfolder to it
named Temp, then add a subfolder to Temp named WMInfo, the name of my
application. It was in the WMInfo folder where I put the Built Outputs from
my WmInfoCab file and my WmInfo.ini file (which I created inside of Visual
Studio since when I ran the installation, it did not like something about
the ini file created with Notepad but did not object to one created in VS)

In the application folder I added the primary output from the InstallerDll.
It appeared to me that if you followed the instructions (which on the whole
are very good), this might have also ended up in the system folder.

Honestly, since all of this was quite complicated, it surprised me when
everything worked.
 
Back
Top