System.IO.FileLoadException: Could not load file or assembly NuGet.Frameworks, Version=6.2.0.146

[jeffkl]

System.IO.FileLoadException: Could not load file or assembly NuGet.Frameworks, Version=6.2.0.146

[jeffkl]

Yes you've discovered the problem with NuGet.Frameworks being referenced by Microsoft.NET.Test.Sdk:

• Microsoft.NET.Test.Sdk
  • Microsoft.TestPlatform.TestHost
    • Microsoft.TestPlatform.ObjectModel
      • NuGet.Frameworks

This causes your unit test to need that particular version in the output directory and causes collisions. Specifically, the error includes Could not find or load a specific file. This is because MSBuild is loading NuGet assemblies that ship with .NET SDK/Visual Studio which can be different than the version than are in the package dependency graph of your app. I try to keep MSBuild.ProjectCreation updated to match the latest version that is out there but have fallen behind. Do you want to send a PR to update the version used by MSBuild.ProjectCreation?

[craigktreasure]

A workaround appears to be to apply a transitive update for NuGet.Frameworks to update to the latest version.

[craigktreasure]

Well, for the record, it looks like you already have a more recent update (6.2.0) to that dependency checked in, but haven't shipped an updated release. 8.0.0 currently depends on 6.1.0. The latest is 6.2.1. I'm happy to submit a PR to update to 6.2.1. We'd just need an updated release following that update.

[craigktreasure]

To be honest, i'm surprised Dependabot isn't helping out here.

[jeffkl]

I was getting bombarded with emails from dependabot every single day so I changed the frequency to monthly 😄 My curse for having so many repos. I can try changing it to weekly so you don't have to send a PR.

4755c0d

[craigktreasure]

Haha, i completely understand. I think i can manage the one character PR 😉.

[craigktreasure]

Looks like Dependabot beat me to it.

[jeffkl]

Fixed by #175 and available in https://github.com/jeffkl/MSBuildProjectCreator/releases/tag/v8.2.1