Archive for August, 2005

I have noticed  few question raised on the deployment features of clickonce in our group as well as in msdn chats .i tried to check how clickonce behaves if i am keeping my version constant but i am chaning the files in (network file shares or website…let say this as server) where u ve deployed.
 
I found that the client is not being asked for the update as ususal like the updator.again after i checked the config files i found that clickonce too depends on the version and if the client and server version mismatch that is if there is a newer version availabel in server the client is being asked whether to go for the new one or the old one(skip upgrade).
 
Howvere for critical update you can force the client update and for this only you have to do is specify a  minimum required versiona s ur new version.Howvere if you want to get rid of the older version files in ur deployment folder you have to delete them by hand or provide a cleaning utility urself.
 
To add few more into the deployemnet scenario you can specify the pre-requisite with as well for a note understanding the configuration of clicckonce as well as the security policy will be a handful.
 
 
Now the question whether i can apply the repairing or patching in clickonce :-remember what ur repairing or patching is dpoing is it updating the version (any major,minor,build,revision) if yes go ahead the client ll be asked as it ll see the new er version .
 
 
I ll discuss the security,downloader and fusion caching of clickonce in next post.
 
For more into clcik once you can watch the video here :-
 
 
Below discussion provides the upadtes and bits on patches and upadates and how you go for the same.
 
1.What is the exact difference betweem Patching and Repairing?
 
Patching is the process of installing an update to the application.  Normally a patch is much smaller than the original installation media since only a handful of files have changed.  A repair is an attempt to fix a broken application by reinstalling the associated resources (files, registry keys, shortcuts).  During a repair, Windows Installer will ensure that all patches that have been applied are used in restoring the resources.  It’s important to note that the application of a patch uses the same maintenance mode installation transaction mechanism as a repair.
 
2.Which is the best option to upgrade an application Patching Or Repairing?
 
Repairing isn’t a method for upgrading an application. Technically you have two options for updating an application: (1) appying a Windows Installer patch or (2) performing a recache/reinstall using the full updated .MSI image.  Generally #1 is preferred because it’s much smaller in size so it’s easier to distribute.  There’s a third concept called major upgrades in which you’d use a MSI package to perform that.  (A MSP is possible, but the recommendation is MSI).  A major upgrade uninstalls the old product and installs the new product.
 
3.When should we create MSI package and when MSP package (after First Time
Installation through MSI)?
 
The MSI package is used on first time installation.  If you’re only going to update a handful of files, then use a MSP (patch) to perform the update.  If however this is a major rev of the product, then use a major upgrade package (.MSI).
 
4.Whether the tools provided for Patch Creation (ORCA.exe, PatchWiz.dll ,
MsiMsp.exe) reliable or there is any other way to do so ?
 
Yes, those tools are reliable and supported.  The authoring tools use patchwiz to build MSPs.
 
5. Does the MSI has capability to Upgrade an application or it simply
reinstalls the application ?
 
It has both capabilities.
 
 
Here is fellow member in .netindiagroup small article on the same
 
The last paper i read on concurrency was in last issue of msdn mag on concurrency here http://msdn.microsoft.com/msdnmag/issues/05/08/Concurrency/default.aspx 
 
however this pdf from msresearch is a wonderful piece:-