Browse by Tags
All Tags » Deploy & Update (RSS)
-
|
Here are three articles that describe Registration-Free COM: Registration-Free COM Interop How To Build and Service Isolated Applications and Side-by-Side Assemblies for Windows XP by RoseMarie FitzSimons and Henry Borys Simplify App Deployment with ClickOnce...
|
-
|
I'm testing the ClickOnce, but when I publish the project my referenced library isn't copied and there isn't any reference in the deploy or manifest files. Does ClickOnce supports this? How can I add the library in the deploy manifest files...
|
-
|
No, the app is downloaded to the same location in the app-store and runs with exactly the same set of permissions as defined in the application manifest regardless of how it is deployed.
|
-
|
No. Note, Visual Studio supports publishing an application to a web server over FTP.
|
-
|
No. However, you can add a link to help by specifying a supportUrl in deployment manifest. ClickOnce will create a shortcut to this URL for you. You cannot add additional entries to start menu.
|
-
|
The install UI cannot be overridden by the application. Standard install UI is an important part of making “ClickOnce” applications trustworthy. It is possible to only use the default UI for a small portion of your application & use the “ClickOnce...
|
-
|
Yes. However, all of the normal Assembly.LoadFrom() restrictions apply, and it is definitely advised against. In most cases, you would be better served to use the On-Demand capability of the System.Deployment APIs.
|
-
|
No. You can indicate which files are required & which are optional. Only required files are downloaded on initial deployment & update. An application can use the System.Deployment APIs to have the optional parts of the application downloaded when...
|
-
|
Yes, there are even multiple ways to accomplish this. Staging rollouts is useful for testing (ex. only deploying a new application updates to a beta user group) & for scalability (ex. rolling out an update to a 1000 users a day). The simplest option...
|
-
|
“ClickOnce” deployments reside on either web or file servers. The standard methods & techniques used to scale those types of servers can be used for “ClickOnce” applications. For example, large web application will often be hosted on some type of...
|
-
|
No, “ClickOnce” uses the System.NET class libraries to do it’s downloads. BITS is not supported on all of the platforms the .NET Frameworks ships on.
|
-
|
The install location of "ClickOnce" application cannot be managed by the application. This is an important part of making "ClickOnce" applications safe, reversible, and easy to administer.
|
-
|
At any given time, “ClickOnce” will have stored 2 versions of an application; the previous version & the current version. You can not configure how many versions “ClickOnce” keeps.
|
-
|
No, they are completely independent.
|
-
|
No, only “ClickOnce” can modify the contents of the “ClickOnce” store. Note each application has a data directory that resides in the store that the application can modify the contents of.
|
-
|
On XP: %userprofile%\Local Settings\Apps (e.g. C:\Documents & Settings\joe\Local Settings\Apps) On VISTA: %userprofile%\AppData\Local\Apps (e.g. C:\users\joe\AppData\Local\Apps)
|
-
|
Cache quota is 250MB. Remember, this cache size only applies to online-only apps, installed apps are not effected. There will be a way to configure this size.
|
-
|
Yes, “ClickOnce” supports HTTP 1.1 compression. Simply enable this on your web server & the files “ClickOnce” downloads will be compressed.
|
-
|
No. “ClickOnce” only downloads the files and assemblies that have changed.
|
-
|
For installed applications, users can use the Add/Remove programs UI to undo the last update. Users can only undo the last update, & only if it was an optional update. That version is marked as undesired in that user’s app store & the user will...
|
-
|
Yes, this is as simple as replacing the deployment manifest on the server you updated with the deployment manifest of the previous version you want to rollback to.
|
-
|
When launching via the network, the update will just happen. When launching via the Start Menu for installed apps, the admin can specify whether the update is required or whether the update is optional, in which case the user is prompted to choose to...
|
-
|
Use this option if you have a critical need to insure users receive updates as quickly as possible. Also, this is the default in Visual Studio because you would otherwise have to launch an application twice after publishing an update to see the expected...
|
-
|
This is the option you should typically use. It is best for fast application startup time and to optimize for offline use. “ClickOnce” will always launch the application immediately and the user doesn’t have to wait for the update check, which particularly...
|
-
|
Whenever a “ClickOnce” application is launched by clicking on a link, either URL or UNC, “ClickOnce” will check for an update & update the application. Thus when running an app from the network, the app will always be up to date… just like web applications...
|
-
|
Online applications are meant to be similar to web applications. You run the app, but when you close it, it’s gone. Installed applications are meant to be closer to traditional client applications. In terms of actual differences: Installed applications...
|