|
|
 |
|
|
| Chat Transcript |
|
| |
 |
 |
ClickOnce: Curing Deployment Headache
Host: Gaurav Khanna, Developer Evangelist, Microsoft |
September 17, 2004 |
|
|
|
| |
Gkhanna_MS : Good afternoon
Gkhanna_MS : Welcome to ClickOnce chat...
Gkhanna_MS : Do we have any questions to get started ?
Gkhanna_MS : I am all waiting...
Gkhanna_MS : Or would you like me to give you a background on ClickOnce?
Moderator_MSDNIndia : (Boszoman) What kind of scenarios would one use this technology in?
Gkhanna_MS : Good start...
Gkhanna_MS : Well, ClickOnce is a deployment technology for Smart Clients
Gkhanna_MS : If you have built Smart Clients, you will know that as of today, to deploy them
Gkhanna_MS : one uses No-touch Deployment
Gkhanna_MS : Here is a backgrounder link on No-touch:
Gkhanna_MS : http://msdn.microsoft.com/library/en-us/dv_vstechart/html/vbtchNo-TouchDeploymentInNETFramework.asp
Gkhanna_MS : However, there are some issues with No-Touch Deployment
Gkhanna_MS : 1) Smart Client applications cannot check for updates on their deployment server
Gkhanna_MS : 2) They cannot incrementally update themselves
Gkhanna_MS : If one were to make such applications capable of auto-updating feature
Gkhanna_MS : that would be expected to be written and implemented by the developer of the application.
Gkhanna_MS : In ClickOnce, a smart client auto-update system is built into the framework
Gkhanna_MS : which is responsible for checking for application updates automatically...
Gkhanna_MS : Obviously, these are smart client applications written using .NET FX 2.0
Gkhanna_MS : to take advantage of ClickOnce
Gkhanna_MS : but the developer doesnt write any code for update check
Gkhanna_MS : or to pull down updates.
Gkhanna_MS : If an update is detected, it can be pulled down incrementally
Gkhanna_MS : or in whole by the ClickOnce
Gkhanna_MS : subsystem
Gkhanna_MS : it makes the updating of Smart Clients very easy
Gkhanna_MS : so thats a bit of backgrounder of
Gkhanna_MS : ClickOnce
Gkhanna_MS : now I can more specific queries
Moderator_MSDNIndia : (bozoman)so is ClickOnce a replacement for No-touch in .NET 2.0?
Gkhanna_MS : Well, its actually builds on the same concept as No-touch
Gkhanna_MS : and enhances it with more features
Gkhanna_MS : So, you could say its being the next version of smart client deployment mechanism
Gkhanna_MS : BTW
Gkhanna_MS : here is a MSDN TV show that discusses ClickOnce
Gkhanna_MS : http://msdn.microsoft.com/msdntv/episode.aspx?xml=episodes/en/20040108ClickOnceJC/manifest.xml
Gkhanna_MS : And here is an article from MSDN Magazine that explains it..
Gkhanna_MS : http://msdn.microsoft.com/msdnmag/issues/04/05/clickonce/default.aspx
Gkhanna_MS : I am ready for more questions?
Gkhanna_MS : Ok..
Gkhanna_MS : so while you think about the questions, let me tell a bit more in detail about how ClickOnce works..
Gkhanna_MS : In ClickOnce terms, we "publish" an application
Gkhanna_MS : The Publishing process involves creating two XML manifests - Application and Deployment manifests
Gkhanna_MS : So to deploy a smart client app using ClickOnce, we point the user to the Deployment
Gkhanna_MS : manifest
Gkhanna_MS : which contains the details of the server containing the application manifest
Gkhanna_MS : The app manifest contains details of the assemblies constituting the application, their strong names
Gkhanna_MS : security details and other details.
Gkhanna_MS : The clickOnce subsystem, part of CLR 2.0, pulls the
Gkhanna_MS : assemblies based upon the
Gkhanna_MS : application manifest
Gkhanna_MS : and install on the user's system
Gkhanna_MS : Later, the system will use this information to check for application updates
Gkhanna_MS : and pull them for update.
Gkhanna_MS : I am ready for more questions now
Gkhanna_MS : Ok..
Gkhanna_MS : let me ask you..
Gkhanna_MS : how many of you
Gkhanna_MS : write smart clients?
Gkhanna_MS : Well?
Gkhanna_MS : no answer to that ?
Gkhanna_MS : Ok.. how about queries on .NET FX 2.0 ?
Gkhanna_MS : Something more general ?
Gkhanna_MS : Well..
Moderator_MSDNIndia : click one part of longhorn?
Gkhanna_MS : ClickOnce is proposed to enhance even more in Longhirn
Gkhanna_MS : For instance
Gkhanna_MS : in .NET Fx 2.0
Gkhanna_MS : ClickOnce is supposed to use the regular
Gkhanna_MS : file transfer mechanisms
Gkhanna_MS : which are not reliable - incase of breakups in the transfer
Gkhanna_MS : but in Longhorn time frame,
Gkhanna_MS : its proposed to use BITS - the background intelligent transfer service
Gkhanna_MS : for its file transfer for updates
Gkhanna_MS : so incase of a transfer
Gkhanna_MS : breakup, ClickOnce using BITS will be able to resume the transfer
Gkhanna_MS : giving more reliability.
Gkhanna_MS : More questions ?
Gkhanna_MS :
Moderator_MSDNIndia : (mayank)How can ClickOnce help me ?
Gkhanna_MS : Well.. as I said.. ClickOnce is the upcoming smart client deployment
Gkhanna_MS : mechanism that will allow compliant applications to check for updates
Gkhanna_MS : and also auto-update themselves
Gkhanna_MS : without requiring the devs to write any bit of code.
Gkhanna_MS : http://msdn.microsoft.com/msdnmag/issues/04/05/clickonce/default.aspx
Gkhanna_MS : Check this MSDN Mag article that explains it..
Moderator_MSDNIndia : (mayank) so is click one going to Replace Traditional VB.net ???
Gkhanna_MS : ClickOnce is a deployment mechanism - and has got nothing to do with VB.NET
Gkhanna_MS : its an enhancement over no-touch deployment and will be its replacement
Gkhanna_MS : in .NET FX 2.0
Moderator_MSDNIndia : (mayank)what abt Security in ClickOnce ??
Gkhanna_MS : Its follows the same philosophy as in no-touch -
Gkhanna_MS : when deployed, the smart client will be executed in
Gkhanna_MS : a security sandbox - however, VS 2005/.NET FX 2.0 has the capability
Gkhanna_MS : to calculate the required permissions for the application
Gkhanna_MS : the deployment manifest will contain those details
Gkhanna_MS : and when deployed, the calculated permissions will be applied to
Gkhanna_MS : the appdomain in which the application executes
Gkhanna_MS : Does that answer ?
Gkhanna_MS : Any more questions ?
Moderator_MSDNIndia : (mayank) Basic Diff bet no-touch deployment and Click Once..process looks same in both so why to use clickonce ??
Gkhanna_MS : hmm
Gkhanna_MS : No-touch doesnt get support
Gkhanna_MS : for auto-update of apps or checking for updates
Gkhanna_MS : ClickOnce, amongst other things, does that
Gkhanna_MS : Thank you Anoop
Gkhanna_MS : thank you all for participating.
Gkhanna_MS : Have a great weekend
|
|
| |
|
|
|
