Skip to main content

Web Deploy - error NU1201: Project is not compatible with net5.0

At one of my clients, we use Web Deploy to deploy our ASP.NET Core applications on our on-premise IIS environment.

After upgrading an application to .NET 6, the build pipeline failed and the application wasn't deployed. Let’s find out what was causing the problem.

A look at the build logs revealed the following error message:

Determining projects to restore...

D:\b\3\_work\52\s\DocumentStorage\DocumentStorage.API\DocumentStorage.API.csproj : error NU1201: Project DocumentStorage.Domain is not compatible with net5.0 (.NETCoreApp,Version=v5.0). Project DocumentStorage.Domain supports: net6.0 (.NETCoreApp,Version=v6.0)

D:\b\3\_work\52\s\DocumentStorage\DocumentStorage.API\DocumentStorage.API.csproj : error NU1201: Project DocumentStorage.Infrastructure is not compatible with net5.0 (.NETCoreApp,Version=v5.0). Project DocumentStorage.Infrastructure supports: net6.0 (.NETCoreApp,Version=v6.0)

Failed to restore D:\b\3\_work\52\s\DocumentStorage\DocumentStorage.API\DocumentStorage.API.csproj (in 636 ms).

2 of 3 projects are up-to-date for restore.

##[error]Error: The process 'C:\Program Files\dotnet\dotnet.exe' failed with exit code 1

"C:\Program Files\dotnet\dotnet.exe" publish D:\b\3\_work\52\s\DocumentStorage\DocumentStorage.Proxy\DocumentStorage.Proxy.csproj --configuration Development /p:PublishProfile=Development /p:Password=*** /p:Username=****/p:AllowUntrustedCertificate=True

Microsoft (R) Build Engine version 17.0.0+c9eb9dd64 for .NET

Copyright (C) Microsoft Corporation. All rights reserved.

More information about the NU1201 error message can be found here: https://docs.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1201

For an unknown reason, it was still thinking that this application should be deployed as a .NET5.0 application which of course is not compatible with the application dependencies that where all using .NET6.0.

So what could make the application think that it was still a .NET5.0 application?

I found the answer in the Web Deploy configuration file(*.pubxml):

Inside this file there was a <TargetFramework> section and this was still pointing to .NET5.0. After changing this to .NET6.0, the error disappeared.

Labels:

Popular posts from this blog

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

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

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more