MSBuild 16.4 MSB3644 Error .NET 8 Deployment Center Sync

Ables, Bradley 35 Reputation points
2024-04-11T12:52:50.5866667+00:00

I have 3 API projects repo'd in devops and hosted on windows 2016 servers (App Services) that were using the app service continuous deployment sync functionality.

So far, everyday i have deployed small code changes to all three environments. One by one each of these projects has failed to deploy via this method.

I upgraded these projects a few months ago to .NET8, and made the coorelating changes to the service to support that with no issue.

The Error I am getting is below.

C:\Program Files (x86)\MSBuild-16.4\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(1175,5): error MSB3644: The reference assemblies for .NETFramework,Version=v8.0 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks

I am not sure how to interact with the msbuild in this manor, nor do I fully understand what the issue is all of a sudden.

In the meantime I've been utilizing pubx profiles.

ASP.NET Core
ASP.NET Core
A set of technologies in the .NET Framework for building web applications and XML web services.
4,175 questions
Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,895 questions
0 comments No comments
{count} votes

Accepted answer
  1. Michael Taylor 48,311 Reputation points
    2024-04-11T14:20:53.84+00:00

    The error indicates a build error, not a deployment one. Can you confirm that the build is failing and not the deployment?

    The error looks like to me a mismatch of frameworks. Did you happen to upgrade this project from NET Framework 4.x to NET 8? There is no NET Framework 8 which is what the error seems to be indicating to me. Migrating from NF 4.x to NET 8 is not a simple change in the target version. For example the project property identifying the framework changes from TargetFrameworkVersion to TargetFramework. Of course all this should be caught during the build.


0 additional answers

Sort by: Most helpful