Unable to build the project from source

[deadlocklogic]

Maybe not necessarily CppSharp related.
I am trying to run build/build.sh and I am getting lots of similar errors:

C:\Program Files\dotnet\sdk\7.0.302\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(135,5): error NETSDK1145: The Apphost pack is not installed and NuGet package restore is not supported. Upgrade Visual Studio, remove global.json if it specifies a certain SDK version, and uninstall the newer SDK. For more options visit   https://aka.ms/targeting-apphost-pack-missing  Pack Type:Apphost, Pack directory: C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Host.win-x64, targetframework: net6.0, Pack PackageId: Microsoft.NETCore.App.Host.win-x64, Pack Package Version: 6.0.16 [C:\Users\user\OneDrive\Documents\Development\CppSharp\build\vs2019\projects\Common.CLI.vcxproj]

Note: I have vs2019 and vs2022 installed on my machine.
Any clues?

[deadlocklogic]

I had to uninstall dotnet 7.0.
After this I got an error which needs dotnet 6.0 and it is even installed on my machine. But apparently vs2019 doesn't support dotnet6.0.
I had to replace 6.0 by 5.0 in config.props and Helpers.lua.
So maybe somebody can fix this or make the build script generate a vs2022 solution.
Thanks.

[tritao]

@josetr Any idea how we can improve this? Do we need to auto-detect or allow the user to select the .NET SDK version someway?

[tritao]

@deadlocklogic Looks like I added this a few months ago: https://github.com/mono/CppSharp/pull/1718/files

Can you check it if helps at all?

[deadlocklogic]

Ok I will try it out and see what I get.
BTW I got everything to build correctly after replacing 6.0 by 5.0 but I will try your PR maybe we can improve this for others.

[deadlocklogic]

@tritao Unfortunately this PR still gives the same problem:
NETSDK1045: The current .NET SDK does not support targeting .NET 6.0. Either target .NET 5.0 or lower, or use a version of the .NET SDK that supports .NET 6.0.

[deadlocklogic]

I got around this by simply opening the solution in vs2022.
@tritao I begun the custom scripting branch here.
Thanks.