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.

Sign up for GitHub

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

Jump to bottom

Update to .NET 6 #252

Open
daveaglick opened this issue Nov 29, 2022 · 2 comments
Open

Update to .NET 6 #252

daveaglick opened this issue Nov 29, 2022 · 2 comments
Labels
🚨 Breaking Change Potentially breaks existing users General Enhancement New feature or request

Comments

@daveaglick
Copy link
Member

With .NET Core 3.1 going out of support, the time has finally come to update the Statiq target to .NET 6. This is also pushed a little bit by ongoing Buildalyzer updates to target .NET 6 which we need to be able to consume: phmonte/Buildalyzer#221.
@daveaglick daveaglick added General Enhancement New feature or request 🚨 Breaking Change Potentially breaks existing users labels Nov 29, 2022
@phmatray
Copy link

phmatray commented Dec 3, 2022

Would it be possible to adopt the C# 11 standard?
.NET6 is a relevant choice because it is an LTS but .NET7 brings some improvements in the area of code generation.

@daveaglick
Copy link
Member Author

There's certainly no reason your own consuming application couldn't target .NET 7, even if the Statiq dependencies are targeting .NET 6. Especially if what you're after is better codegen scenarios since those are mostly driven by the compilation process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🚨 Breaking Change Potentially breaks existing users General Enhancement New feature or request
Milestone
No milestone
Development

No branches or pull requests
2 participants
@daveaglick @phmatray