-
Notifications
You must be signed in to change notification settings - Fork 23
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
2022 #38
Comments
@rjpeck2, I've been looking at this in my own fork, following the instructions here and example here, but I've run into trouble. The short story is, I've got a Line Endings Unifier 2022 extension building perfectly! However some step in the migration from I'm going to create a draft PR for a discussion on how to fix the 2019 dependency problem, but meanwhile, if you want Line Endings Unifier in your VS2022, you're welcome to grab my fork, build the Note that since that will be a local install, I don't believe that it will be automatically updated if Line Endings Unifier 2022 is actually published to the Visual Studio Marketplace in future. |
Would be great to see a version of this for 2022! |
I was not able to properly build @naine's PR, at least not in Visual Studio 2022. The build tools were outdated and I had big issues with the reference assemblies. So I decided to build further on his fork and and as a result successfully migrated to the Feel free to build it locally or publish it to the markeplace. Take note that this package only works with VS2022. |
Are you planning on updating the extension for 2022 ???
The text was updated successfully, but these errors were encountered: