Skip to content
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

New Validator Requires .NET 8 #255

Closed
Narnian12 opened this issue Jan 11, 2024 · 5 comments · Fixed by #256
Closed

New Validator Requires .NET 8 #255

Narnian12 opened this issue Jan 11, 2024 · 5 comments · Fixed by #256

Comments

@Narnian12
Copy link

When trying to install and run the new validator on our .NET 6 project, we are running into the following error:

NU1202: Package Firely.Fhir.Validation.R4 2.0.0 is not compatible with net6.0 (.NETCoreApp,Version=v6.0). Package Firely.Fhir.Validation.R4 2.0.0 supports: net8.0 (.NETCoreApp,Version=v8.0)

We definitely have plans to update to .NET 8, but it looks to still have the "Early Access" flag (at least in the Azure Portal), so we are not upgrading just yet.

Are there plans to allow this validator to work in older .NET versions?

@ewoutkramer
Copy link
Member

ewoutkramer commented Jan 12, 2024

We planned to ship .NET 8 + netstandard2.1 in line with our policy to support both the newest .NET + "anything that supports netstandard", but we didn't actually ship netstandard2.1. Working on it.

@ewoutkramer
Copy link
Member

By the way, in the meantime, you can simply change the target framework to net6.0 and recompile the project yourself, I just checked it, it compiles without any problems under net6.0.

@Narnian12
Copy link
Author

Sounds good, thank you so much!

@mmsmits mmsmits linked a pull request Jan 16, 2024 that will close this issue
@mmsmits mmsmits closed this as completed Jan 16, 2024
@mmsmits
Copy link
Member

mmsmits commented Jan 16, 2024

Just released version 2.0.1 support netstandard2.1, so this should build now on in a NET6 project

@Narnian12
Copy link
Author

Perfect, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants