clickonce

So I created an Outlook Add-in and used the click-once setup to deploy it. The setup runs fine when the user is administrator, but otherwise: no go. Running the setup with "run as..." and logging in as admin works, but than the add-in is installed under the admin, not the current user. The addin doesn't show up in outlook. I tried following this guide: http://blogs.msdn.com/mshneer/archive/2008/04/24/deploying-your-vsto-add-in-to-all-users-part-iii.aspx But I get stuck at part I: http://blogs.msdn.com/mshneer/archive/2007/09/04/deploying-your-vsto-add-in-to-all-users-part-i.aspx I follow the

I have a Windows Forms application that I recently re-wrote in WPF , and I need to release it to my end users. I'd like to be able to have the users go to the ClickOnce install point for the WPF application and have their Windows Forms application removed, so they don't have both on their machine. What's the best way (read: easiest for users) of accomplishing this? I have thought about creating an prerequisite command line to detect the old version and uninstall, but I would like to avoid having to write something like that where it only gets run once. RobinDotNet I think you actually SHOULD

How do I do it? Is there any reason I shouldn't? I have a winform ClickOnce App that has about 13mbs in DLLs that are not mine so I would have no need/ability to update them at any regular intervals. DevExpress(3), Microsoft ReportViewer, Microsoft SQL Replication. Microsoft SQL SMO. Without them being included in my ClickOnce App my whole program comes in at about 1.5mbs and with our remote sites having limited vpn connectivity I really need to get it down there. I can't send 15mbs across our network to all users everytime I make a minor app change. Thanks UPDATE FOR CLARITY For clarification

I have a problem with a ClickOnce deployment of a Windows Forms application. When I built the new setup, and tried to export it overwriting as usual the previous setup, Visual Studio came up stating that my certificate is expired. This behaviour is described in You receive an error message when you try to update a Visual Studio 2005 ClickOnce application after the certificate that was used to sign the installation expires and there is a workaround in RenewCert - Working Version . But these solutions are not applicable in my situation. Another workaround involves taking back the system date of

I am using ClickOnce to deploy a C# application. It is available online only, so I cannot disable the application to check update every time it starts. Every time when it gets launched from url, you will see a "verifying application requirement" window. This is fine. However, the time it takes for this window to disappear varies greatly. Sometimes it's instant, sometimes it takes a few seconds. Anyone know why this is the case and how to speed up this verifying process? I am using process p = Runtime.getRuntime().exec("explorer myURL") to launch the application. I don't know if it matters or

I've just started to get the following error in my clickonce application. I have just installed visual studio 2013 on my machine prior to this "Application validation did not succeed. Unable to continue. when i click into details I get Activation of C:\Temp\ClickOnce\myApp\myApp.application resulted in exception. Following failure messages were detected: Strong name signature not valid for this assembly Microsoft.mshtml.dll. I also get two warnings but I do not believe they are the cause of the problem The manifest for this application does not have a signature. Signature validation will be

Is it possible to build a web deploy package containing a clickonce application that can be deployed to a web server using the standard webdeploy tool? Here would be the ideal process: MSBuild "YourFullyQualifiedProjectName.csproj/vbproj" /T:Package obj\Debug\Package\YourFullyQualifiedProjectName.deploy.cmd /Y The reasoning behind this would be so we can build the whole solution including web packages, run all tests, then deploy only after tests pass. I've currently looked at doing a file-based deploy to a temp folder, copy that into a web project, then package the web project. Is there a