problems with xSharp in Visual Studio

Public support forum for peer to peer support with related to the Visual Objects and Vulcan.NET products
Post Reply
User avatar
rwooters
Posts: 15
Joined: Fri Mar 04, 2016 10:56 pm

problems with xSharp in Visual Studio

Post by rwooters »

I am having problems with xSharp in Visual Studio.
1) blocking and commenting lines.
2) reformatting code.
3) search and replace.
...
I have reinstalled xSharp, but there has been no change. I did something to VS, but I don't know what.

I'm at a loss; any help would be great.

--------------------------------
Microsoft Visual Studio Community 2022
Version 17.11.5
VisualStudio.17.Release/17.11.5+35327.3
Microsoft .NET Framework
Version 4.8.09037


X# Visual Studio Project System 2.20.0.3
The X# Project system allows you to edit, compile and debug your X# application inside Visual Studio.
Copyright (c) XSharp BV 2015-2023. All rights reserved.
http://www.xsharp.eu
--------------------------------
Thanks,
Richard Wooters
FFF
Posts: 1584
Joined: Fri Sep 25, 2015 4:52 pm
Location: Germany

Re: problems with xSharp in Visual Studio

Post by FFF »

C'mon, if your customer would sent you "this" as bug report, you'd yell at him - how should anyone detect with this, what problem you really have?
Regards
Karl
(on Win8.1/64, Xide32 2.20, X#2.20.0.3)
User avatar
Chris
Posts: 4936
Joined: Thu Oct 08, 2015 7:48 am
Location: Greece

Re: problems with xSharp in Visual Studio

Post by Chris »

Hi Richard,

Do you mean those features do not do anything at all anymore? Or are not even available as commands at all?
Could be related to a recent update in VS 2022 where MS did some breaking changes (without giving a heads up), but this should be solved in the upcoming X# 2.21 release.
Chris Pyrgas

XSharp Development Team
chris(at)xsharp.eu
User avatar
robert
Posts: 4540
Joined: Fri Aug 21, 2015 10:57 am
Location: Netherlands

Re: problems with xSharp in Visual Studio

Post by robert »

Richard,

Due to an (undocumented) change in VS 2020 these features are no longer working with X# 2.20.
This is fixed in the upcoming 2.21 build.

Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
Post Reply