X# VS integration changes

This forum is meant for questions and discussions about the X# language and tools
Post Reply
JohnBonnett88
Posts: 50
Joined: Mon Mar 07, 2022 12:34 am

X# VS integration changes

Post by JohnBonnett88 »

Hi All,

I think a recent update to VS has broken some of the X# integration.

Yesterday I upgraded my VS to Visual Studio Professional 2022 (64-bit) - Version 17.11.0

Before that I had some Format options on the Edit menu when looking at an X# document, as follows:
On the Edit/Advanced menu in VS I used to have two entries Format Document (Ctrl+K Ctrl+D) and Format Selection (Ctrl-K Ctrl+F)

I have been used to using that Format Document option to automatically indent C# documents and only recently discovered that it worked on X# too, but it has now stopped for X# documents with this VS update, so I thought I should let people know. The options are still there for C# documents.

Best Regards,
John
User avatar
robert
Posts: 4412
Joined: Fri Aug 21, 2015 10:57 am
Location: Netherlands

Re: X# VS integration changes

Post by robert »

John,
Thanks for the report.
It looks like Microsoft has changed something without notifying the 3rd party.
I'll take a look at this.

Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
JohnBonnett88
Posts: 50
Joined: Mon Mar 07, 2022 12:34 am

Re: X# VS integration changes

Post by JohnBonnett88 »

Robert,

Another thing I noticed is that the buttons to comment out and uncomment a block of code are now greyed out, so something has changed there too.

John
Juliet46780
Posts: 1
Joined: Wed Sep 11, 2024 8:01 am
Location: Poland

Re: X# VS integration changes

Post by Juliet46780 »

hey it sems like the recent Visual Studio update might have afected the X# integration, especialy the formating options.i recomend checking if the X# extension is stil enabled in Visual Studio.sometimes, updates can reset setings or disable extension.if the isue persist, consider reporting it on the X# forum or checking for any updates from the X# team.they might have a fix or workaround for this! :-)
Post Reply