13 answers to a€?Installing a ClickOnce Application regarding usersa€?

I gave a chat in hill see at southern area Bay .Net individual class fulfilling on August fifth. It was a general explore ClickOnce implementation and how to put it to use. Everyone in space ended up being a Windows paperwork or WPF creator, which appears rarer and rarer nowadays as folks migrate to web solutions. There have been some concerns, and lots of close debate about items that everyone wants changed in ClickOnce implementation.

The most regularly wanted feature in that appointment along with the MSDN ClickOnce community forum is to install a ClickOnce application regarding customers in place of a particular consumer.

This is certainly tough because the records tend to be kept in the consumer’s visibility, where the individual has read/write benefits. One of many style objectives of ClickOnce should supply a deployment techniques enabling consumers to set up software without elevated benefits. Installing a loan application for all customers requires benefits.

Another layout goals were to protect the consumer equipment from issues brought on by applications installations. Do you really remember a€?dll hella€?? This was the challenge that occurred whenever another program arrived and changed a dll that you were determined by, and brought about issues for your application, or vice versa.

In a ClickOnce implementation, you are able to add all of the dll’s locally utilizing the deployment, in place of installing them within the GAC or even the house windows program directory. (it is leaving out, naturally, the .NET Framework as well as other prerequisite software such as for example SQLServer present.) You may also deploy the SQL Compact Edition dll’s or DirectX dll’s. This allows one keep rigid version control on the dll’s which you use in your implementation. Microsoft would need to ascertain a means to manage this in the event that application had been implemented for every consumers; should they just weren’t mindful, you could potentially quickly land in dll hell once more.

Alternatively, should they simply thought we would put the data under the completely customers visibility, once again you have the permissions difficulty that Microsoft sought for to address with ClickOnce deployment, because the individual cannot write to the people data files without increased privileges. In addition, If Microsoft saved the deployed records inside a€?All Usersa€? folder, they would need determine what to complete if UserA got logged on by using the program, and UserB logged on and there had been an update offered. Do you realy kick-off UserA? Do you ever forego the upgrade because UserA is already operating the application? What’s UserA usually simply leaves his profile logged on? How could you ever create an update?

This consult might handed down to Microsoft, but We haven’t been aware of any plans to feature an free chat room albanian alteration to the in .NET 4.0, so I wouldn’t count on any quick results. Creating an all-users apply are counter on build needs of ClickOnce deployment, therefore I imagine it will likely be something everyone has to call home with, at least for now. Making use of XCopy or a setup & implementation plan and going your personal incremental upgrade methodology would be the path to take if you completely have to have an All Users set up.

Linked

This admission got and it is submitted under ClickOnce implementation, Microsoft Technology. You’ll adhere any reactions to the entryway through the RSS 2.0 feed. You’ll be able to keep a reply, or trackback from your own site.

Like this:

1. Ed Multare States: | Respond Back

Please, are you able to let me know… how to make an DVD automobile installer in which can set… . Microsoft windows Program Installar (setup.exe and msi) . Screens Installer redistribuible . web FW 3.5 SP 1 resdistribuible . SQL 2005 Present redistribuible