Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Administered by:

Server stats:

215
active users

eupolicy.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.8

#visualstudio

3 posts3 participants0 posts today
Public *
Tor Lillqvist

Sigh, Visual Studio Installer has the feature to "rollback" to a previous version with just one click. But only for one step back. (For me, it was from 17.14.5 to 17.14.2.) When you have done that, it doesn't offer any further rollbacks. Irritating. #VisualStudio

Edit: But oh well, I figured out another way to work around my problem.

Public *
Aptivi

Visual Studio 2025 is very close!

When Visual Studio 2022 version v16.14 was released, a blog post that was related to the release has teased the next major version of Visual Studio as follows:

Lastly, we’ve started work on the next major version of Visual Studio, planned for release later this year. We’ll be sharing more details here soon—follow the blog to stay up to date with the latest Visual Studio news.

This is especially true, since Visual Studio 2025 will be announced very soon later this summer to introduce major features and to introduce a redesigned UI that matches the Windows 11 aesthetics.

This is one hint, but we have two more hints to talk about.

Usually, Microsoft releases a preview of the next Visual Studio minor version at about the same time as the final official release of the minor version that was previously in the preview stage. For example, when Visual Studio v16.13 was released this February, the first preview of v16.14 was also released at the same day of the former version release. An interesting hint has been pointed out when Microsoft decided not to release Visual Studio v16.15 Preview 1 at the same day of the v16.14 release, because the Visual Studio 2022 preview release notes says this:

Visual Studio 2022 v17.14 is now generally available (see release notes). However, we recommend that all current Preview Channel users stay on Preview to continue receiving the latest updates and early access to upcoming features. This is especially important if you’re using the .NET 10 SDK, as some preview SDK features are not yet supported in the stable release.

Stay tuned for more details later this summer about what’s coming next for Visual Studio…

Another hint mentions that we are approaching closer to the Visual Studio 2022 mainstream support ending date, which is assigned to January 12th, 2027, and there are no announcements of the next major version of Visual Studio made until now. This is interesting, considering that Visual Studio 2022 went globally available as version v17.0 was released on November 8th, 2021, after a five-month preview that started June 19th, 2021.

This means that we are heading towards a major milestone four years after the last major milestone, and that Visual Studio 2025 v18.0 will undergo many major changes, which will improve developer experience. We expect the first preview to be released this summer, with the final release being on November 2025 with the airing of .NET 10.0 LTS.

This follows a similar pattern with the release of Visual Studio 2022 with .NET 6.0 LTS together on November 8th, 2021.

We are very excited about the release of Visual Studio 2025 v18.0 and .NET 10.0.

What does it mean for our apps?

Our applications will be migrated to .NET 10.0 days after the final release to ensure that all systems can get this version of .NET easily, while we’re monitoring the rollout of this version of .NET across several Linux distributions, including Ubuntu.

Our applications, once migrated to .NET 10, will experience improved performance and better support for various features. This is part of our goal to provide better user experience across releases of projects like Nitrocid KS.

The next major version of Nitrocid, which will be released early next year, will use this version of .NET and will require at least Visual Studio 2025 to build, to ensure that we use this version of .NET at its maximum potential.

#Net#C_#dotnet
Public
Christian Drumm 🇪🇺🧗🚵

Does anyone know if there’s already a petition or initiative in #Germany ot the #EU calling on higher education institutions (Universitäten and Fachhochschulen) to switch to #opensource software?

Specifically, I’m looking for efforts to stop the use of #Microsoft (Windows, Outlook, Exchange, MS Office, etc.) in administration and to move away from teaching tools like #Word,#Excel, or #visualstudio.

I'm looking for something similar to this:
👉 openpetition.de/petition/onlin

openPetitionAppell an die Hochschulrektorenkonferenz zur Nutzung sozialer Medien - Online petitionWir fordern die Hochschulen in Deutschland auf, ihre Accounts bei X (vormals Twitter) baldmöglichst still zu legen. Die Präsenz bei X/Twitter wird aufgrund der dort betriebenen Desinformation und politischen Hetze nicht dem Aufklärungsanspruch der Hochschulen gerecht. Gleichzeitig sollten Präsenzen auf Mastodon (https://de.wikipedia.org/wiki/Mastodon_(Software)) und anderen Servern im Fediverse (https://de.wikipedia.org/wiki/Fediverse) aufgebaut werden, deren dezentrale und moderierte Gestaltung
#digitalsouverenity
Public
Simon Tatham

Two things I learned this week about #MSVC / #VisualStudio:

1. If vcvars64.bat is not behaving itself for some reason, you can set VSCMD_DEBUG=1 and it will print more diagnostics. 2 and 3 print more still: 3 is an "OMG redirect to a file and sort through it later" level of verbosity.

2. If you do this, the script stops for a noticeable time just after printing "Sending telemetry". One of the reasons it's so slow is that it's phoning home! You can set VSCMD_SKIP_SENDTELEMETRY=1 to turn that off, improving speed as well as privacy.

This is commented in one of the sub-scripts VsDevCmd.bat with the command
REM Send Telemetry if user's VS is opted-in
but, of course, I have no memory of seeing any opt-in box to tick.

ExploreLive feeds
About