

Maybe the Project's format didn't keep up with the latest. Most of the finds about compatibility issue question were about "after upgrading Windows" or "after upgrading Visual Studio", but I had no such precede. There wasn't even a key entry in the regedit, so I Googled more. It was obviously VS compatibility problem at first sight.
VISUAL STUDIO COMMUNITY MAC DOTNET NOT FOUND DEBUGGER CODE
NET Core:Ĭopy Code E:\.\Atrium\src\Atrium.Server\ : error : Unrecognized Guid format. My personal preference is Visual Studio, but what I have seen in the FSharp Slack is mostly Visual Studio Code.

What are my tools (which IDE supports Bolero).

Now what to do? Let's check out, how can I debug the problem. "e:\.\Atrium\src\Atrium.Client\obj\Debug\netstandard2.0\blazor\bootjson-references.txt" Write-boot-json "obj\Debug\netstandard2.0\" -references "e:\.\Atrium\src\Atrium.Client\obj\Debug\netstandard2.0\blazor\""Įxited with code 1. "e:\.\Atrium\src\Atrium.Client\obj\Debug\netstandard2.0\blazor\" references "e:\.\Atrium\src\Atrium.Client\obj\Debug\netstandard2.0\blazor\īootjson-references.txt" -embedded-resources Write-boot-json "obj\Debug\netstandard2.0\" (String assemblyPath, String assemblyReferences, String embeddedResourcesSources,īoolean linkerEnabled, String outputPath)Īt .Ĭ:\Users\MR-TaNk\.nuget\packages\\ģ.0.0-preview6.19307.2\targets\(633,5): error MSB3073: IEnumerable`1 embeddedContent, Boolean linkerEnabled)Īt .BootJsonWriter.WriteFile (String assemblyFileName, String entryPoint, String assemblyReferences, See: Ītrium.Client -> e:\.\Atrium\src\Atrium.Client\bin\Debug\netstandard2.0\ĮXEC : error : Could not load type '.JsonSerializerOptions'įrom assembly ', Version=4.0.0.0, Culture=neutral,Īt .BootJsonWriter.GetBootJsonContent Restore completed in 513,38 ms for e:\.\Atrium\src\Atrium.Server\. Copy Code Restore completed in 300,97 ms for e:\.\Atrium\src\Atrium.Client\.
