clickonce

I am using the built-in My.Settings functionality in VB.NET to save application settings. This is very convenient but I notice that each time I release a new version, the settings are lost. Why and how can I prevent it? You need to manually update your application settings, I use this easy method: Create a boolean setting called MustUpgrade, User scope, default to True. Then write a method to check if My.Settings requires updating, and call it's Update() method if so. Flag your settings as updated, and save. Call this somewhere in your app load. The Upgrade() method will update your Settings

I published a ClickOnce application from Visual Studio 2012, and selected the .NET 4.0 runtime and Microsoft Report Viewer 2012 as prerequisites. I also selected to download the prerequisites from the vendor's website. When I try to install the application on a client PC, I receive the following error: Setup has detected that the file 'C:\Users\MyUsername\AppData\Local\Temp\VSD537C.tmp\DotNetFX40\dotNetFx40_Full_setup.exe' has changed since it was initially published. The log provides no additional details. If I manually install the .NET runtime, then I receive the same error for the report

I have a Windows Forms application developed using C# in .NET framework 3.5, Service pack 1. The application can be published based on the development database as well as the production database. I am using MSBuild community tasks to publish my application. I do not face any problems while publishing the application to different location, namely a development location and a production location. Issue: After installing the development application into my machine, I am unable to install the production application. It gives me an error saying: You cannot start application TEST from this location

I am deploying a .NET VSTO application via click once. The application's main assembly needs to be registered for COM interop as part of the installation process. I know that this can be done by writing code to execute "REGASM assembly.dll /tlb", but the problem is that the target workstations that will be installing my application don't have administrative rights, so the regasm fails when trying to register the type library. My question is, how can I register my .net assembly for com interoperability when I don't have administrative access? You could use registration-free activation of COM

I am trying to launch a ClickOnce application via a link on a web page. The link has to go to the server to request a transaction GUID before it can launch the application. The code works like this: function clickHandler() { $.post('/gettransactionid.aspx', function(tranId) { console.log("BEFORE"); window.location = "/deploy/Company.Domain.Product.application?" + tranId; console.log("AFTER"); }); return false; } This works perfectly fine in Firefox but in IE it peforms a navigation and doesn't open the clickonce application. The console.log BEFORE and AFTER are shown in the console window in

I've set up my simple project in Visual Studio 2008 to use a ClickOnce installer. I've specified that the ClickOnce manifests should be signed by our comapny's PFX file. When I set this up in Visual Studio it asked for the password for the PFX file, which I gladly supplied. Everything works fine when I build and publish from within Visual Studio. It also works fine building from MSBuild on my machine. However, when I try to build it using MSBuild on our build machine, I get the following error: ERROR MSB3321 in C:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(1805,7) :