VS 2026

[wriedmann]

Hi Robert,
I'm in the process of changing my development notebook, planned for December.
Should I install VS 2026 (Community) or better an older version?
I can postpone also the migration to the new machine as my current machine works well, and I plan to migrate only for security purposes.
Wolfgang

[ArneOrtlinghaus]

Our colleague Hansjörg has already made some tests with VS2026 and did not find any problems regarding X#.
But we cannot use the version currently because the Devexpress controls still do not support VS2026.

But as the installation of Visual Studio is so smooth I would say that it is not a big problem to install VS 2022 now and have VS2026 installed later on the same machine.

Arne

[ic2]

Hello Wolfgang,

Making X# work for any VS version takes a lot of resources. Even if it works on paper (Robert will tell if it does), you will encounter issues which are probably mostly solved for VS2022/2019.

I've got VS 2019 and 2022 and they both work independently so I why not install 2 VS versions? I sometimes work in VS2022 and most of the time in VS2019. I have not seen any advantage in VS2022 yet.

VS2026 'what's new' is probably mostly CoPilot. AI is very good in producing code which does not work as you can see in my post https://www.xsharp.eu/forum/topic/5703?p=34976#p34976. In the best case, it helps you find a working solution, in the worst case it will cost you extra time; in my case I expected some small issue I overlooked, not that in the solution presented a method was used which could never work as Chris wrote to me.

In short, I would not be in a hurry to install VS2026, let alone as the only VS on your new system.

Dick

[wriedmann]

Hi Arne,
ok, thank you! Personally I would like to keep only one installed VS version on my system, and since my main tool is XIDE, it should not be a showstopper.
@Dick: thank you too, but I prefer to have only one VS installation, and a 2026 installation would last longer than a 2022 installation.
My current system has "only" a 2019 installation.
Wolfgang

[HansjoergP]

Hi Wolfgang,
until now I have no issues with Visual Studio 2026. The only small problem is that in the output during build there is some verbose output von X#. It seems to be really stable (To tell the truth, it even seems more stable to me than VS2022.).
For us at the moment the only small problem is, that it is not possible to use the designer with Devexpress. But support has been announced for December.
Regards
Hansjörg

[JohnBonnett88]

Hi All,

Here is is some feedback on my experience so far with VS2026. I have the Professional version on my work machine and the Community one on my home machine. I have had no problems at all with X# integration on the Community version. It has been a different story at work with the Professional version.

I have one large, about 60 projects, solution that uses X# at work. After installing VS2026 and X# 2.24.0.1, I opened this solution and all the X# projects loaded properly but all the C# projects did not load, complaining about Microsoft.Net.Sdk. After chasing error messages up on the web (I could share some details on this if anyone wants) I eventually got the C# stuff behaving, but had to rerun the installer for X# again. Then everything worked as expected.

A remaining problem I have with X# at work is that, each day when I start VS2026, I find my X# projects do not load until I install X# again. I have no such problem with the Community version. As a clue to what may be wrong, if I try to reload one of the unloaded X# projects, I get this message "The type initializer for 'XSharp.Project.ErrorListManager' threw an exception."

Cheers,
John Bonnett

[JohnBonnett88]

Hi All,

Just a little more feedback on needing to reinstall X# each day, I watched the install process carefully and I noticed that in the process of uninstalling X# and reinstalling it I saw some odd messages in both the command shell window while uninstalling and in the normal window when reinstalling. I have both VS2022 and VS2026 at present.

Both windows referred to both "Visual Studio 2022 (17.14)" and "Visual Studio 2022 (18.0)". That is not a typo, and I think that second one should be 2026. That may be a clue to what is happening.

After running this, VS2026 happily loads my X# projects, but perhaps not tomorrow.

Cheers,
John

[HansjoergP]

Hi,

yesterday after updating Visual Studio to version 18.0.1 I had the same problem with 'XSharp.Project.ErrorListManager' threw an exception.". I don't get it to work after that. I have made now a downgrade to 18.0.0 and it seems to work again

Hansjörg

[robert]

Guys,
Our installer runs a tool to check which versions of VS are installed on your machine (see attachment).
When the last installer was created, there was no VS 2026 and the installer API does not include the "name" of the VS version.
So the installer "guesses" VS 2022. This will not be a problem at runtime.

Btw: On my machine, the tool lists the following versions:

Robert

Code: Select all

InstanceId: 37eaece3 (Complete)
InstallationVersion: 17.14.36717.8 (4785137139908616)
InstallationPath: C:\Program Files\Microsoft Visual Studio\2022\Enterprise
Product: Microsoft.VisualStudio.Product.Enterprise
Workloads:
    Microsoft.VisualStudio.Workload.CoreEditor
    Microsoft.VisualStudio.Workload.ManagedDesktop
    Microsoft.VisualStudio.Workload.VisualStudioExtension

InstanceId: 583bdc27 (Complete)
InstallationVersion: 18.3.11218.70 (5066563200876614)
InstallationPath: C:\Program Files\Microsoft Visual Studio\18\Insiders
Product: Microsoft.VisualStudio.Product.Enterprise
Workloads:
    Microsoft.VisualStudio.Workload.CoreEditor
    Microsoft.VisualStudio.Workload.ManagedDesktop
    Microsoft.VisualStudio.Workload.VisualStudioExtension

InstanceId: 7bb986ab (Complete)
InstallationVersion: 16.11.36631.11 (4503649272659979)
InstallationPath: C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional
Product: Microsoft.VisualStudio.Product.Professional
Workloads:
    Microsoft.VisualStudio.Workload.CoreEditor
    Microsoft.VisualStudio.Workload.ManagedDesktop
    Microsoft.VisualStudio.Workload.VisualStudioExtension

InstanceId: ab95df66 (Complete)
InstallationVersion: 15.9.36631.12 (4222165706014732)
InstallationPath: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional
Product: Microsoft.VisualStudio.Product.Professional
Workloads:
    Microsoft.VisualStudio.Workload.CoreEditor
    Microsoft.VisualStudio.Workload.ManagedDesktop
    Microsoft.VisualStudio.Workload.VisualStudioExtension

[HansjoergP]

Hello Robert,

the installation works fine. We have also to persons in our company which are working with VS2026 18.0.1. Im the only one who had problems to use this version. For me VS2026 18.0.0 works fine. I have made now an rollback, and the problems are gone. Before that (with 18.0.1) I had also 'XSharp.Project.ErrorListManager' threw an exception." and all projects are unloaded...

Regards
Hansjörg