clickonce

We're trying to deploy an unsigned clickonce application. For some users this fails with the below error, while for others its no problem. This is probably a security setting somewhere, but we have been unable to find it. Any tips on how to allow this application to be installed (bar signing it ) PLATFORM VERSION INFO Windows : 5.1.2600.196608 (Win32NT) Common Language Runtime : 2.0.50727.3615 System.Deployment.dll : 2.0.50727.3053 (netfxsp.050727-3000) mscorwks.dll : 2.0.50727.3615 (GDR.050727-3600) dfdll.dll : 2.0.50727.3053 (netfxsp.050727-3000) dfshim.dll : 4.0.31106.0 (Main.031106-0000)

We are currently deploying a WPF 4 application via ClickOnce and there is a scenario when the installation fails. If the user does not have .NET 4.0 Full install and attempts to install our application the framework installs fine, but the application fails to install. If we re-run the installation again the application installs fine. Here is a copy of the log: PLATFORM VERSION INFO Windows : 6.1.7600.0 (Win32NT) Common Language Runtime : 2.0.50727.4927 System.Deployment.dll : 2.0.50727.4927 (NetFXspW7.050727-4900) mscorwks.dll : 2.0.50727.4927 (NetFXspW7.050727-4900) dfdll.dll : 2.0.50727.4927

I'm trying to sign a ClickOnce .NET Application. I have a SSL cert that I use on a website, but I'm thinking that it is not up to the job. When I select the cert in Visual Studio I get an messsage box saying ' The selected certificate is not valid for code signing. Choose another certificate file '. The cert details look like this: whereas a temporary cert generated in VS looks like this: It seems to have a lot more going for it in terms of looks and general charisma. Do I need to get a new cert issued? What would I need to specify when ordering it to ensure it is up to the job of signing the

I have a problem with ClickOnce publishing of a WPF application. If the application is built (debug or release), it is running correctly. Application published by ClickOnce crashes. I tried to change Target Platform. Sometimes this change helps to solve problems, but not every time (1 of 20 cases). I have Visual Studio 2008 and the project has been upgraded from Visual Studio 2005. Any ideas? Thank you in advance! On the machine where the application is installed, drill down in the user profile to the ClickOnce cache, and look for the cached application files. The folder will have the exe and

I have an error during installing updating or fresh installing my ClickOnce publish on my app. This occurs on computers without the app installed and on those with the app already there. The pfx file I use for signing the project is the same as it was in previous versions so I don't think the certificate is the issue. + Exception reading manifest from <APPPATH>.exe.manifest: the manifest may not be valid or the file could not be opened. + The element 'assembly' in namespace 'urn:schemas-microsoft-com:asm.v1' has invalid child element 'SignedInfo' in namespace 'http://www.w3.org/2000/09/xmldsig

My .NET 2.0 application imports unmanaged 32 bit dll. The dll is loaded (first interop call happens) when user opens a file via a dialog within the application. When I deploy the application via clickonce with target platform "Any", users on 64 bit windows get BadImageFormatException when trying to open files from the application (at the moment the unmanaged dll is loaded). I understand this is due to incompabible bitness of the 64 bit process and the 32 bit unmanaged dll. I have redeployed the application using x86 as target platform. As I understand it, this should solve the bitness problem.

Ok, I have a ClickOnce app that I'm testing and I ask the user for a couple of pieces of information the first time they use load the app; Customer Id and Name. I then set the Properties so that they'll be saved across sessions. The property is Properties.Settings.Default["Customer ID"] and similar for name. So I uninstall the application through control panel and reinstall the application but the settings are still there! I go and find all directories for my application and delete out the settings but the application acts like it still has them. I can even step through the debugger and see

In the context of a click-once application that is being debugged locally with exception breaking on "Thrown" turned on in VS2010, I am experiencing the following error: Deployment Exception: "Store metadata "CurrentBind" is not valid." at System.Deployment.Application.ComponentStore.GetPropertyString(DefinitionAppId appId, String propName) when I execute the following line of code: if (System.Deployment.Application.ApplicationDeployment.IsNetworkDeployed) This exception is being caught and handled by .net code, and the application will not crash after experiencing this error. Unfortunately,

I customized my project using a solution I found in this question: Why doesn't ClickOnce in Visual Studio deploy content files from dependent assemblies? <ItemGroup> <AdditionalPublishFile Include="$(OutputPath)\**\*.rpt"> <Visible>False</Visible> </AdditionalPublishFile> </ItemGroup> <Target Name="BeforePublish"> <Touch Files="@(IntermediateAssembly)" /> <CreateItem Include="@(AdditionalPublishFile)" AdditionalMetadata="TargetPath=%(RecursiveDir)%(Filename)%(extension);IsDataFile=false"> <Output TaskParameter="Include" ItemName="_DeploymentManifestFiles" /> </CreateItem> </Target> it was