dotnet setup: My problem is after creating a Setup and Deployment project for an
application I then install the application on a system. I remove a file from
the Application directory that has been created. Then If I attempt to run the
application by clicking the shortcut I created or the executable itself,
Windows Installer attempts to run my installer program again and then
replaces the file I deleted. I did some research and I believe this has to do
with the auto repair feature in .Net but I do not want this to happen. So in
the field when a file is removed it does not go looking for my install. Any

This is a Windows Installer feature. VS setup&deployment projects create MSI
files such that each file is capable of being restored with the repair
mechanism and there isn't anything in the IDE that lets you change that
behavior. Even if the shortcut didn't cause a repair, a user can go to
Add/Remove Programs (or right click the MSI file) and cause a repair to
restore missing files. If a particular file is optional, perhaps you can
create it from your application or at install time with a custom action so
that it's not seen by Windows Installer.
--
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

[quoted text, click to view]

I ran into this same problem several months ago. This happens because
the shortcut is created as an Advertised shortcut. To fix this I had
to use the Orca MSI Editor, included in the MSI SDK from Microsoft, to
change the shortcut tables of the MSI after it was created. In the
Shortcut table, replace the target cell of the shortcut(s) with the
path to the application, ie: [TARGETDIR]AppName.exe. Then delete the
Icon cell associated with the shortcut. I could not find a way to do
this from Visual Studio.



--
cellach
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message1803387.html

Compared to that, it's probably easier to just find a way to set the
DISABLEADVTSHORTCUTS property, such as put it in the property table with a
value of 1 or set it from the command line, but if the user decides to do a
repair on the product (say by right-clicking the MSI file) the missing file
will still be restored. None of these methods guarantee that the file won't
reappear. Leaving the component Guid null for the files in question is the
documented way of telling MSI you don't want the file repaired at all. I
suspect that most developers might prefer to just change the design so that
the app creates the file at install time rather than have the MSI file
install it, then with VS setups the're not altering the MSI file after every
build.
--
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280


[quoted text, click to view]

Has anyone found any other solutions to this. I am seeing this right now.

Thanks, Arra

**********************************************************************
Sent via Fuzzy Software @ http://www.fuzzysoftware.com/