clickonce

My app uses ClickOnce tehcnology. Today I needed to run it as administrator. I modified the manifest file from <requestedExecutionLevel level="asInvoker" uiAccess="false" /> to <requestedExecutionLevel level="requireAdministrator" uiAccess="false" /> However VS cannot compile the project: Error 35 ClickOnce does not support the request execution level 'requireAdministrator'. I think it's impossible to use them at once. Isn't it? I need to change the system time, can I do that in application level? Can I emulate it, so app. can do what I want. I change time +2 hours then put back for a second.

I know it is a very commonly faced problem. But, there is a slight difference, my WPF installs perfectly and runs on Windows 7 and Windows 8 OSes. But, when tried to install on a VM running Windows XP, it gives the following Error: Cannot continue. The application is improperly formatted. Details : PLATFORM VERSION INFO Windows : 5.1.2600.196608 (Win32NT) Common Language Runtime : 4.0.30319.1 System.Deployment.dll : 4.0.30319.1 (RTMRel.030319-0100) clr.dll : 4.0.30319.1 (RTMRel.030319-0100) dfdll.dll : 4.0.30319.1 (RTMRel.030319-0100) dfshim.dll : 4.0.31106.0 (Main.031106-0000) SOURCES

My ClickOnce installation fails with an error: File, WindowsFormsProject.exe, has a different computed hash than specified in manifest. I use MSBuild to generate ClickOnce deployment package. The relevant line from the build script: <MSBuild Targets="Publish" Projects="WindowsFormsProject.csproj" ContinueOnError="false" /> The WindowsFormsProject.csproj has a Post-Build step that signs the executable, as follows: signtool sign /a $(ProjectDir)\obj\$(PlatformName)\$(ConfigurationName)\$(TargetFileName) The trouble is, when I look at the build log I see that the manifest is generated BEFORE the

Is there any way to specify a command line argument for msbuild that will apply only to one project (i.e. project-level not solution-level), when building a multi-project solution? The reason I ask is because I want to enable side-by-side installs of a click-once deployment. Let me give an example: 1) This works MSBuild "C:\Dev\MyProj\MyProj.Shell\MyProj.Shell.csproj" /p:SkipInvalidConfigurations=true /target:publish /p:OutputPath="C:\Dev\Temp\" /p:ApplicationVersion=1.2.3.4 /p:ProductName="My Proj" /p:Configuration="Release" /p:Platform="Mixed Platforms" /verbosity:diagnostic 2) This doesn't

I publish Windows Forms application using ClickOnce. The installation is quite big considering the overall size of this app. It's something over 15 MB. If I compress locally built application it is squeezed to 2.5 MB. Can ClickOnce deployment be compressed somehow? If not, is anyone using IIS compression to speed up transfers? Would that help? As far as I know, you can't really manually compress your assemblies. However, you absolutely can use IIS compression. From my testing with a bandwidth monitor, it makes a significant difference. And once it's set up, you never have to think about it, it

We have a sqlserver (WinForms) application that is deployed with ClickOnce that talks directly to the database. If we are forced to port it to oracle, can ODP.NET be used with ClickOnce. (The users may not have admin rights on their PCs) Background This data import application is used by a handful of users at each customer’s site it uses intergraded logon to connect to SQL Server. Most users access the system var an Asp.net application, or a WinForms (clickOnce) application that talks to a web service. see also " How to write a .Net application that works with both SqlServer and Oracle " EDIT:

I have one Windows application which is deployed using ClickOnce technology. Is there a way to change the icon of that application which is shown in the image? ManjuVijayan The following code is what I used for solving the problem. I used Stack Overflow question Custom icon for ClickOnce application in 'Add or Remove Programs' . private static void SetAddRemoveProgramsIcon() { //only run if deployed if (System.Deployment.Application.ApplicationDeployment.IsNetworkDeployed && ApplicationDeployment.CurrentDeployment.IsFirstRun) { try { Assembly code = Assembly.GetExecutingAssembly();

I have a ClickOnce application that about 120 customers are using. This week, I found out two customers declined an update in January and were stuck on an old version. I discovered this by deleting an ASP script the old versions used on our server. The customers that aren't updating get a 404 and call to ask why. One customer clicked our install button again and got the latest version no problem. The other clicked our install button and gets an "Application validation did not succeed" error. The details of the error are SomeImage.gif "has a different computed hash than specified in manifest."