You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Probably a duplicate of #10878, but I'm not 100% sure, so posting it anyways.
The 3.1.101 SDK dotnet build builds the repro just fine, while 3.1.200/201 fails with the following:
Fody: An unhandled exception occurred: [dotnet-fail-repro\Test.csproj]
Exception: [dotnet-fail-repro\Test.csproj]
Could not load file or assembly 'Mono.Cecil, Version=0.11.0.0, Culture=neutral, PublicKeyToken=1ca091877d12ca03'. The system cannot find the file specified. [dotnet-fail-repro\Test.csproj]
Type: [dotnet-fail-repro\Test.csproj]
System.IO.FileNotFoundException [dotnet-fail-repro\Test.csproj]
StackTrace: [dotnet-fail-repro\Test.csproj]
at InnerWeaver.Execute() [dotnet-fail-repro\Test.csproj]
at Processor.ExecuteInOwnAssemblyLoadContext() in C:\projects\fody\Fody\Processor.cs:line 150 [dotnet-fail-repro\Test.csproj]
at Processor.Inner() in C:\projects\fody\Fody\Processor.cs:line 122 [dotnet-fail-repro\Test.csproj]
at Processor.Execute() in C:\projects\fody\Fody\Processor.cs:line 51 [dotnet-fail-repro\Test.csproj]
Source: [dotnet-fail-repro\Test.csproj]
FodyIsolated [dotnet-fail-repro\Test.csproj]
TargetSite: [dotnet-fail-repro\Test.csproj]
Void Execute() [dotnet-fail-repro\Test.csproj]
[dotnet-fail-repro\Test.csproj]
I understand that it uses a third-party package (Fody), but since it works on the previous version of the SDK, it looks like a regression in SDK itself since it broke compatibility.
The text was updated successfully, but these errors were encountered:
Probably a duplicate of #10878, but I'm not 100% sure, so posting it anyways.
The 3.1.101 SDK
dotnet build
builds the repro just fine, while 3.1.200/201 fails with the following:I understand that it uses a third-party package (Fody), but since it works on the previous version of the SDK, it looks like a regression in SDK itself since it broke compatibility.
The text was updated successfully, but these errors were encountered: