#4766 - Support netstandard2.0 when using net6.0 utility#4779
#4766 - Support netstandard2.0 when using net6.0 utility#4779TWhidden wants to merge 1 commit intodotnet:mainfrom
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@imcarolwang, can you check to see if this is still a problem with the latest sdk? If it is, can you validate this fixes things? Ideally we would have a test scenario to validate this, but I don't know how easy that would be to do with how we do our tests? |
|
This is no longer an issue with the latest SDK. This PR was intended to resolve issue #4766, but the problem was actually addressed in PR #4772. The issue occurred in the bootstrapper project, which was created for reusing referenced assembly types purpose. The tool was updating the project's target framework from net6.0 to netcoreapp2.0 when the user's project targeted netstandard2.0. The fix now ensures that the bootstrapper project targets the latest .NET version available on the user's machine, and this solution has been effective so far. We validated this scenario manually. There's an automation case testing type reuse scenario but targeting the latest .net version, not netstandard2.0. I'll try to add one later along with the current test suite fix (PR #5052). |
|
Closing as issue has since been resolved |
When targeting netstandard2.0, using 2.0.3 dotnet-svcutil under net6.0, the generation process will fail stating the following error:
SC : error CS8630: Invalid 'nullable' value: 'Enable' for C# 7.3. Please use language version '8.0' or greaterUsing
latesttag to target what is latest available on the developers machine.This edit only modifies the csproj file used during the generation process