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

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

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

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more