Skip to content

#4766 - Support netstandard2.0 when using net6.0 utility #4779

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

TWhidden
Copy link

@TWhidden TWhidden commented Jan 8, 2022

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 greater

Using latest tag to target what is latest available on the developers machine.

This edit only modifies the csproj file used during the generation process

@dnfadmin
Copy link

dnfadmin commented Jan 8, 2022

CLA assistant check
All CLA requirements met.

@imcarolwang
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@HongGit HongGit added the tooling An issues related to any tool shipped from this repo. label Jan 25, 2022
@mconnew
Copy link
Member

mconnew commented May 21, 2025

@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?

@imcarolwang
Copy link
Contributor

imcarolwang commented May 22, 2025

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).

@mconnew
Copy link
Member

mconnew commented May 23, 2025

Closing as issue has since been resolved

@mconnew mconnew closed this May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tooling An issues related to any tool shipped from this repo.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants