How to fix the error that occurs when executing the GenerateTemporaryTargetAssembly task

Danila 25

When creating an sdk project with wpf elements, the error Could not copy the file ProjectName.csproj.nuget.dgspec.json occurs when building on the server. I see that the files csproj.nuget.g.props and nuget.g.targets are created and copied, but the file csproj.nuget.dgspec.json. msbuild is not being created. How can this problem be solved

Zhengye Xu-MSFT 95 Reputation points Microsoft Vendor

2023-09-25T06:41:30.2366667+00:00

Hi Danila,

Would it be convenient for you to describe the process of creating your project, I need detailed steps to reproduce this problem. Also do you have a screenshot of the error message in Visual Studio. If you can provide more information, I can better help you analyze this problem.
Basim Kadhim 26 Reputation points

2023-11-23T03:29:15.3466667+00:00
I'm having the same problem. We have a large solution that builds for me on my dev machine when I open the solution in Visual Studio to do the nuget restore, but when I try to put in an Azure DevOps pipeline with an explicit Nuget restore step prior to the build step, I get the error:

(GenerateTemporaryTargetAssembly target) -> C:\Program Files\dotnet\sdk\8.0.100\Sdks\Microsoft.NET.Sdk.WindowsDesktop\targets\Microsoft.WinFX.targets(408,7): error MSB3030: Could not copy the file "C:\DevOpsAgent\_work\47\s\DAS\AdminConsole\obj\AdminConsole.csproj.nuget.dgspec.json" because it was not found. [C:\DevOpsAgent\_work\47\s\DAS\AdminConsole\AdminConsole.csproj]

This happens to be the only WPF project in the solution and all other projects in the solution seem to build just fine.

I've also manually looked at the file it is complaining about and the Visual Studio nuget restore generates it, but the Azure DevOps nuget restore does not.

1 answer

Basim Kadhim 26 Reputation points

2023-12-11T17:50:53.8566667+00:00

For anybody else running into this issue, it turned out in my case that ensuring I was using a newer version of Nuget (5.x) instead of the 4.9.6 default version that my pipeline had been using by introducing a Nuget tool installer step at the beginning of my pipeline solved the issue. It seems that there is an issue with the older nuget version.
Please sign in to rate this answer.

1 person found this answer helpful.
Suchy, Joe 0 Reputation points

2024-04-10T21:46:54.18+00:00

This answer was honestly SUPER helpful! The error just seemed so random-ish and there wasn't really much to go on, so I really appreciate you sharing what you found!
Sign in to comment