I have my .NET code published in two servers
http://server1/<ApplicationNam e>/Publish.htm and
http://server2/<ApplicationNam e>/Publish.htm, and if i open IE on the client
machine and type the link (http://server1/<ApplicationNam e>/Publish.htm) it
would install the application in the client machine from server1.
1) Changing the server location on the same client machine (i.e.
http://server2/<ApplicationNam e>/Publish.htm) should override the existing
installation, and should not reinstall the application again as it does
currently. Currently you can install from a different server via IE, but the
user ends up with two copies of the application installed. Is this possible
to accomplish if so how ?
I understand that multiple users can't install (i.e. unlike Windows
Installer installation which installs for everyone and puts a shortcut on
desktop) , My specific question is installing the application for a single
user from multiple Servers. Is it possible i could not find any articles
which talk about this problem.
2) Is it possible to pop up a message to the user on client machine if the
updates were not applied for more than week. I know i can put this logic in
my code but for that i need to know where are the ClickOnce update details
are stored within the client machine. (i.e. When it was installed last Vs
today's date if it is more than a week i can pop up the message)
3) Currently the Installation procedure puts the Application shortcut on
start menu and doesn't have the option of installing for everyone. Is it
possible to provide this option so that it puts a shortcut on desktop, if so
how do we accomplish ?
During my investigations i came to know that ClickOnce installation puts an
entry in the registry and also creates bunch of folders under "C:\Documen ts
and Settings\pchint la\Local Settings\Apps\2 .0\" (Manifest files also exist in
this location). I tried changing the client machine's registry and the
manifest files to have the server name changed but still the application
remembered the old server location from which it was installed
(http://server1/<ApplicationNam e>/Publish.htm). Which makes me feel that
there is something else which associates the installation server name along
with the application executables and binaries apart from the registry and
manifest file.
