We offered a talk in Mountain View from the Southern Bay .Net individual people appointment on August fifth. This was a standard speak about ClickOnce implementation and ways to put it to use. Everyone from inside the room was a Windows Forms or WPF creator, which seems rarer and rarer nowadays as individuals migrate to web programs. There are plenty of inquiries, and plenty of good conversation about things that men would like changed in ClickOnce implementation.
More regularly wanted element because conference and also in the MSDN ClickOnce Forum should put in a ClickOnce software for several people in place of a particular user.
It is difficult since documents include stored in the user’s profile, in which the individual has actually read/write privileges. One of many style aim of ClickOnce would be to offer a deployment method that enables clientele to install programs without elevated benefits. Installing an application for many customers need rights.
Another style objective were to protect your client equipment from issues triggered by applications installations. Will you keep in mind a€?dll hella€?? It was the trouble that occurred whenever another software came along and changed a dll that you were determined by, and caused problems for the job, or the other way around.
In a ClickOnce deployment, it’s possible to include the vast majority of dll’s in your area with the deployment, instead setting up all of them in GAC aisle Profiel and/or windows program directory. (this might be leaving out, obviously, the .NET platform and various other necessity solutions for example SQLServer Express.) You may also deploy the SQL lightweight model dll’s or DirectX dll’s. This enables one preserve tight version controls regarding dll’s you use in your own deployment. Microsoft would have to figure out a method to handle this if application comprise implemented for many customers; when they were not careful, you might quickly land in dll hell again.
Alternatively, should they simply decided to place the data according to the completely Users visibility, again you’ve got the permissions challenge that Microsoft desired to handle with ClickOnce implementation, because the consumer cannot write to people files without elevated rights. Furthermore, If Microsoft put the deployed files from inside the a€?All Usersa€? folder, they’d must figure out what doing if UserA was logged on using the application, following UserB logged on and there is an update available. Can you start up UserA? Do you really forego the modify because UserA is operating the applying? Understanding UserA always will leave his profile logged on? How will you previously perform an update?
This demand happens to be passed on to Microsoft, but I haven’t heard about any intends to incorporate an alteration to the in .NET 4.0, so I wouldn’t count on any rapid information. Carrying out an all-users install are counter on the build plans of ClickOnce deployment, therefore I envision it will likely be something everybody has to call home with, no less than for the present time. Using XCopy or a setup & implementation package and running a incremental posting strategy will be the approach to take in the event that you completely have to have an All Users set up.
Connected
This entryway got and is also registered under ClickOnce Deployment, Microsoft development. Possible adhere any responses for this entry through the RSS 2.0 feed. You can create an answer, or trackback from your webpages.
Along these lines:
- Ed Multare States: | Answer
Please, can you tell me… How to create an DVD vehicle installer in which can placed… . Screens Software Installar (setup.exe and msi) . House windows Installer redistribuible . web FW 3.5 SP 1 resdistribuible . SQL 2005 Express redistribuible