clickonce

I am facing a problem that when I publish my ClickOnce application through MSBuild (4.0), the publish.htm (or default.htm) isn't created in the app.publish folder. When publishing through Visual Studio, it gets crated... In my .csproj file I have the following properties set, and it still not working... <CreateWebPageOnPublish>true</CreateWebPageOnPublish> <WebPage>default.htm</WebPage> Any ideas? Thanks I found a good solution here . You can use a template for publish.htm with {VERSION} placeholder inside. MSBuild Community Tasks are required for the FileUpdate task. BUILD_VERSION -

I have a ClickOnce environment like this: \Fileserver\ClickOnceApps\App1.application C:\Documents and Settings\user\Start Menu\Programs\publisher\app1.appref-ms My understanding is the .apppref-ms file is a glorified link to the app.application file. Does it do anything else? Nir If you open the appref-ms file in a text editor you'll see it contains the Url for the application, culture, processor architecture and key used to sign the application, so yes, it's just a link. The difference between those "Application Reference" files and shortcuts (.lnk) is that the application reference points to

I installed Visual Studio 2012 and went to go publish one of our applications, that is targeted at the .NET 4.0 framework. Due to the setup on these machines, we can not target 4.5 at this time. We are also using the 'Download prerequisites from the same location as my application' feature. When going to deploy from Visual Studio 2012, I get the following error: To enable 'Download prerequisites from the same location as my application' in the Prerequisites dialog box, you must download file 'DotNetFX40\dotNetFx40_Full_x86_x64.exe' for item 'Microsoft .NET Framework 4 (x86 and x64)' to your

Could someone tell me the difference between the publishing folder location and the installation folder URL? Is there any reason why these two wouldn't be the same? RobinDotNet You enjoyed my answer in the MSDN Forums so much, I'm posting the link to the answer here as well. ;-) If you are publishing and installing from the same URL, you can just fill in the publishing file location and be done. The reason there are two is so if you want to publish to one place, but have an installation URL that's different, you can do that. For example, you might want to publish to your server using ftp, in

I have a WPF Solution I am building in VSTS Online. Below is my basic Build Definition: In Visual Studio 2017 locally I've assigned a Click Once Certification (PFX). Everything builds and compiles fine locally. The Build fails with the following error: Cannot import the following key file: . The key file may be password protected. To correct this, try to import the certificate again or import the certificate manually into the current user's personal certificate store. What setting/step do I need to include to ensure the PFX file is seen and the password is set? Using this code to import

We're developing a C# WPF (.Net 4.0) application that requires screen "recording". We've evaluated ByteScout's Screen Capture SDK (free trial available), and it does exactly what we need to it. However, the problem is that our application is designed to be deployed by ClickOnce, to our clients' machines (not on our network), and who will likely be logged in as limited, non-administrative users. The SDK has a redistributable component, but this requires to be installed separately - no good for ClickOnce. ByteScout seemingly address this need in their documentation, under the section