Skip to main content

ClickOnce 3.5 and .NET 4.0 problems

Last week we discovered some strange behavior in the ClickOnce implementation for Visual Studio 2010.

We created a clickonce setup from the Visual Studio 2010 command line by using

msbuild /target:publish

This created a setup file, an application manifest and all the required files as you should expect.  Important to notice is that it’s a Visual Studio 2010 solution but we are compiling against the .NET 3.5 framework(Target=.NET 3.5).

If we try to install this ClickOnce application on a system that does not have .NET 4.0 installed everything works.

However when we try to install the application on a .NET 4.0 system, the installation blows up with following error:

* Activation of \\dev\test.application resulted in exception. Following failure messages were detected:

                        + Deployment manifest is not semantically valid.

                        + Deployment manifest is missing <compatibleFrameworks>.

This error is telling us that the manifest file is not correct as the <compatibleFrameworks> section is missing in the XML file. This section is a required section for a .NET 4.0 manifest but NOT for a .NET 3.5 manifest. As this application is a .NET 3.5 application, he shouldn’t complain.

It seems like a .NET 4.0 system incorrectly assumes that it has to install the application by using the .NET 4.0 clickonce system.

Strange thing is that if we create the build by using the Publish properties inside the Visual Studio 2010 IDE, everything works. This is especially annoying because we use the same functionality on our build server to automatically create our application packages.

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more