Daniel Plaisted
Daniel Plaisted
@ryanholden8 It looks like for Arm64 you have the 6.0.401 SDK, but for x64 you only have version 3.1.423. Probably VS for Mac is using the x64 SDK which is...
@mrward @emaf This looks like it may be an issue with VS for Mac and possibly the SDK resolver. Can you investigate / route appropriately?
@jeffhandley Is this the same issue as #28049? In this case it looks like switching to the .NET 8 SDK is breaking some stuff related to preview features in ASP.NET....
Do you also want to take this for 7.0.1xx GA?
@terrajobst It sounds what might be happening here is that a project stops working when moving from the .NET 6 SDK to the .NET 7 SDK, as it targets .NET...
@jeffhandley Can you handle tracking any changes for .NET 8 you might want to do for this?
What happens if you build and run from the command line using `dotnet run`? What about if you build from the command line with `msbuild /restore` and then run the...
It looks like you're overriding the `OutputPath` of the projects so that they all output to the same folder. Can you try removing that to see if you still see...
@masonwheeler Based on the error message it looks like a reference assembly is being copied to the output instead of an implementation assembly, but looking at the binlog I didn't...
I think the issue is this, from `ProtocolSaveTest.csproj`: ```xml ..\Pansynchro.Connections.MSSQL\obj\Debug\net6.0-windows\ref\Pansynchro.Connectors.MSSQL.dll ``` That is a direct reference to the reference assembly, which is probably causing it to be copied to the...