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

Support VS 2022 #18

Open
Waxime64 opened this issue Oct 15, 2021 · 7 comments
Open

Support VS 2022 #18

Waxime64 opened this issue Oct 15, 2021 · 7 comments

Comments

@Waxime64
Copy link

Visual studio 2022 is out soon. Please rebuild for this version

@thHube
Copy link

thHube commented Nov 23, 2022

It is out now. Can we get support for vs2022? please please please please?

@Waxime64
Copy link
Author

I switch directly in VS2022 to code style
tools-> options -> text editor -> "language" -> code style
and you can set "Format on save"

@nneesshh
Copy link

maybe you guys can try my fork: https://github.com/nneesshh/astyle-extension, fo vs2022 only.

@Amaroker
Copy link

@nneesshh, thank you very much!

It works when "Format on save" is checked. However, I would prefer to use keyboard mappings like before. Do you know how to make this work?

When I look in an old VS2017 setup, I see there were two options available in Options->Environment->Keyboard:
Edit.FormatDocumentAStyle
Edit.FormatSelectionAStyle

But these were not added in VS2022.

@Amaroker
Copy link

Amaroker commented Apr 3, 2023

It also used to be possible to select these options in the menu.

astyle

Any ideas how to get them back? Or would it be possible to add them manually somehow? External tools can be added from the menu "Tools->External Tools" but I don't know how to configure it for AStyle.

There are some issues when using "Format on save". For example, when a file with unsaved changes is closed, Visual Studio pops up a "Save changes" message. If you select "Don't Save", it will still trigger AStyle format and then the file is not restored to its previous state.

@nneesshh
Copy link

nneesshh commented Apr 13, 2023

nneesshh@bfad5e3

@Amaroker You can try again.
I don't know vsct well,I just search the text from your pic and fixed the vsct and guid, haha...

@Amaroker
Copy link

@nneesshh Perfect, it works! Thank you once again!

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

No branches or pull requests

4 participants