Yes, "ClickOnce" applications that choose to be installed get an entry added in the Start Menu that can be used to launch the application when disconnected from the network. Note however, it's still up to the application to make sure it can work offline...

You can use "ClickOnce" to deploy .NET Framework based applications built with any language, including C++.

quot;ClickOnce" can be used to deploy Windows Forms based application based on the .NET Framework. Since "ClickOnce" applications are deployed via the web, they can't be allowed to impact the client machine to a high degree. So if...

quot;ClickOnce" is the codename for a technology that ships in the .NET Framework 2.0 that allows Windows Forms based client applications to be downloaded & run over the Network. Quite simply, "ClickOnce" makes running a client application...

For a number of security related considerations, "ClickOnce" requires that the main entry point assembly (the .exe file) be compiled with the 2.0 version of the .NET Framework. Other assemblies in the application can still be compiled with previous versions...

For example, let's say you want to define an add-in model, or provide some base forms so my customers can extend to customize the look-and-feel of my app by just dropping in additional assemblies. How can you achieve this with "ClickOnce"...

No. Addins generally require special registration and integrated activation within the hosting application. The "ClickOnce" installer does not support machine level changes such as this.

Yes. When a "ClickOnce" application is activated via a URL, the application can obtain the QueryString of the URL used to activate the application.

That is the actual "ClickOnce" engine that is handling the update checks & downloads. It is launched when a "ClickOnce" application needs updated. It shuts itself down if not used for 15 minutes.

You can, but wouldn't you rather have a rich Windows Forms based UI? Also, console apps that require a command-line interface are beyond the scope of "ClickOnce" deployment in the .NET Framework 2.0. The primary reasons for this is that the install path...

Most applications won't have to know anything about "ClickOnce" to be deployed with "ClickOnce". In most cases, using "ClickOnce" is as simple as creating the necessary manifest files & placing the application on a server... for which we provide tools...

No. While Visual Studio makes deploying "ClickOnce" applications simple, there are several other ways to deploy "ClickOnce" applications. The .NET Framework SDK includes a tool named MAGE(Manifest Editor & Generator) that provides both a UI (mageui...

Yes and your app will still be auto-updateable via a network server you configured into the "ClickOnce" deployment when you created the CDs. This is a great solution for large applications or for applications that have pre-requisites installed with the...

No. All "ClickOnce" applications are installed per-user. Each user is totally isolated from one another and must install their own copy. If your application needs to be installed per-machine, you should use MSI.

ClickOnce" & MSI are separate but, complimentary application installer technologies. "ClickOnce" is targeted at web based per-user deployments. This has a lot of benefits, but also means you can't do anything & everything at install time. If...

ClickOnce" ships in the .NET Framework redist & supports all of the same operating systems & languages as the core .NET Framework. Specifically Windows 98 & up, except for NT4.