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

Consider updating the shipped roslyn files? #156

Open
AraHaan opened this issue Aug 16, 2023 · 4 comments · May be fixed by #157
Open

Consider updating the shipped roslyn files? #156

AraHaan opened this issue Aug 16, 2023 · 4 comments · May be fixed by #157

Comments

@AraHaan
Copy link

AraHaan commented Aug 16, 2023

Is it possible to update roslyn 4.1.0 that gets packaged into this to a much more updated version that ships with the .NET SDK / Visual Studio 2022 itself?

@AraHaan
Copy link
Author

AraHaan commented Aug 16, 2023

Edit: looks like there is roslyn 4.7 and roslyn 4.8 as well.

AraHaan added a commit to AraHaan/RoslynCodeDomProvider that referenced this issue Aug 16, 2023
@AraHaan AraHaan linked a pull request Aug 16, 2023 that will close this issue
@MattBussing
Copy link

I love the idea of updating to latest! Do you have reasons you need the 4.8 version over the 4.1 version, other than you want to stay up date? Listing the reasons could help the developers choose to prioritize this work.

@AraHaan
Copy link
Author

AraHaan commented Jun 11, 2024

To be able to use the latest bug fixes in the compiler, as well as being able to use things like C# 12 on .NET Framework cshtml files for my web applications. Also would help for future migration to core to be not as painful as well as it would mean updating all of the cshtml files anyways to the newer language versions of C#. Also because I made a version of this that also includes a few performance fixes as well and everything seems to work so far without issues anyways.

@MattBussing
Copy link

Great reasons!

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.

2 participants