Browse by Tags
All Tags » ClickOnce » General (RSS)
Sorry, but there are no more tags available to filter with.
-
|
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"...
|
-
-
|
Yes, although the top level exe must be built with Whidbey.
|
-
|
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 use “ClickOnce” to deploy .NET Framework based applications built with any language, including C++.
|
-
|
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...
|
-
|
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...
|
-
|
No. “ClickOnce” only deals with deploying applications. The Windows Forms control in the browser technology is effectively unchanged.
|
-
|
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...
|
-
|
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...
|
-
|
“ClickOnce” is the successor to the V1 No-Touch deployment technology. “ClickOnce” builds upon V1 & addresses the key limitations & issues with the V1 technology. The V1 No-Touch deployment technology is still supported in V2 of the .NET Framework...
|
-
|
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...
|
-
|
If you need to do extensive install time custom actions, MSI would probably be a beter choice than ClickOnce.
|
-
|
Yes. One option is to use the VS Bootstrapper. The Bootstrapper will bundle all of your apps necessary pre-requisite’s, install them when run & then start the “ClickOnce” application install. The Bootstrapper must be run the 1st time each user uses...
|
-
-
|
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.
|
-
|
No. All “ClickOnce” applications are installed per-user.
|
-
|
“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" 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...
|
-
|
You can check the useragent value in your server side code or in javascript on the html page (hint… see the Publish.htm page that VS generates). The useragent string will contain the version of the .NET Framework installed on that client.
|
-
|
Really whatever way works best for you. Ex. You can have your users install the .NET Framework before using “ClickOnce” or use management tools like SMS to push out the .NET Framework across your enterprise. To help with deployment, Visual Studio provides...
|
-
|
"ClickOnce" simply uses a MIME type for activation, which is configured by the .NET Framework 2.0 setup. This allows a "ClickOnce" app to be launched by any client that uses standard Windows url activation. This includes Internet Explorer...
|
-
|
No. "ClickOnce" does not use any special protocols to transfer files. So you can use a regular file share, IIS or any web server. If you are using a web server, there are a few additional considerations. First, you may need to configure the...
|
-
|
“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.
|
-
|
You need to have the .NET Framework 2.0 installed on the client. And you need a place to publish your app to where your end users can access, such as a web server, file share, or media such as CD/DVD.
|
-
|
"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...
|
