#c_ — Public Fediverse posts

Visual Studio 2026 Preview is here!

A new version of Visual Studio is materializing, and the first preview is now live! The next version of Visual Studio, which we’re talking about in an earlier article, isn’t called Visual Studio 2025, as you may think. The name of this version of Visual Studio set to revolutionize your whole development experience is called…

Visual Studio 2026!

You can see the below video that talks about the future of Visual Studio, which tells you what Visual Studio 2026 will introduce.

Please note that the features and the appearances shown in the below video are based on an internal build of Visual Studio 2026 (you can tell from the “INT PREVIEW” badge) and may not reflect their state in the final version.

https://www.youtube.com/watch?v=eQaZytCQsLEu0026amp;ab_channel=MicrosoftVisualStudio

First of all, a new logo has been revealed for Visual Studio 2026, and it has a more modern look than before. Gradients in the logo are now more visible than the Visual Studio 2022 logo.

When the first preview gets released hopefully before November, there will be over 5,000+ bugs fixed and over 300+ feature requests to be implemented across the entire Visual Studio 2026 suite. Additionally, updates have become a monthly update cadence, and this is currently being experimented with Visual Studio 2022 version 17.14.

Visual Studio 2026 will still use the legacy .NET Framework that is exclusive to Windows in its main process, but it will stay at 64-bit as 32-bit computers reduce in popularity.

Visual Studio 2026 will have a more modern UI that was teased to us in Visual Studio 2022 since two years ago. A more fluent design will be used to reduce visual clutter and to increase productivity. UI annoyances will be resolved to further maximize space and to improve user productivity.

You will be able to theme your Visual Studio 2026 installation to further make it your own, to place your own colors to your IDE in your style. Theme creation will also become easier than ever.

You will be able to build .NET 10 applications using Visual Studio 2026 to make them benefit from new features and to increase their performance.

To learn more, check out this excellent blog article from NDepend here.

#Net #C_ #csharp #dotnet #news #Tech #Technology #update #visualStudio #VisualStudio2025 #VisualStudio2026

Visual Studio 2025 is now Visual Studio 2026!

A new version of Visual Studio is materializing, and the first preview is set to be released soon. The next version of Visual Studio, which we’re talking about in an earlier article, isn’t called Visual Studio 2025, as you may think. The name of this version of Visual Studio set to revolutionize your whole development experience is called…

Visual Studio 2026!

You can see the below video that talks about the future of Visual Studio, which tells you what Visual Studio 2026 will introduce.

https://www.youtube.com/watch?v=eQaZytCQsLE&ab_channel=MicrosoftVisualStudio

First of all, a new logo has been revealed for Visual Studio 2026, and it has a more modern look than before. Gradients in the logo are now more visible than the Visual Studio 2022 logo.

When the first preview gets released hopefully before November, there will be over 5,000+ bugs fixed and over 300+ feature requests to be implemented across the entire Visual Studio 2026 suite. Additionally, updates have become a monthly update cadence, and this is currently being experimented with Visual Studio 2022 version 17.14.

Visual Studio 2026 will still use the legacy .NET Framework that is exclusive to Windows in its main process, but it will stay at 64-bit as 32-bit computers reduce in popularity.

Visual Studio 2026 will have a more modern UI that was teased to us in Visual Studio 2022 since two years ago. A more fluent design will be used to reduce visual clutter and to increase productivity. UI annoyances will be resolved to further maximize space and to improve user productivity.

You will be able to theme your Visual Studio 2026 installation to further make it your own, to place your own colors to your IDE in your style. Theme creation will also become easier than ever.

You will be able to build .NET 10 applications using Visual Studio 2026 to make them benefit from new features and to increase their performance.

To learn more, check out this excellent blog article from NDepend here.

#Net #C_ #csharp #dotnet #news #Tech #Technology #update #visualStudio #VisualStudio2025 #VisualStudio2026

Terminaux 7.0 Beta 4 Announcement

As we are closer to the final release (that we’ve prepared for you), we’ve released the fourth beta version of Terminaux 7.0 that concludes the beta program that we’ve started almost three months ago. Terminaux 7.0 brought many interesting changes, and this beta version is the latest representation of those improvements. We’ve primed the final version of Terminaux 7.0 for documentation and for testing to find bugs even before release.

We are very excited to announce that Terminaux 7.0 Beta 4 is now available on NuGet as version 7.0.0-beta4, which you can download to your project using the following command:

$ dotnet add package Terminaux --version 7.0.0-beta4

This version of Terminaux 7.0 brings many changes that were done after the third beta version released July 3rd. You can access the source code for the fourth beta version here on GitLab.

We’ve added theme color tools, which allows you to theme your Terminaux applications according to either the pre-defined theme type or the custom theme type that you define in your theme JSON file. This is a 1:1 implementation copied and moved straight from Nitrocid with appropriate modifications done, due to the older template tools being unsuitable for use with Nitrocid. Themes also support accents, which give a dynamic look to your Terminaux applications based on your color accent.

We’ve also added all features from Nitrocid’s shell implementation, effectively removing the implementation from the Nitrocid codebase. This is to make Terminaux applications using the shell features more powerful than never before. With features like MESH scripting, command redirects, and filesystem support, your applications now became more powerful than before! You can now more easily autocomplete the paths, and you can write scripts for your applications to automate the shell operations.

We’ve also added a new feature that most libraries don’t have, but appeals to users that prefer their native language. Starting from the fourth beta, your applications can now be localized! With the new localization feature powered by LocaleStation, you can now make your Terminaux application use your native language supported by our libraries! Common languages like French, Spanish, and Portuguese are available for you to try out, and you can use the existing APIs in the LocaleStation library to make Terminaux applications determine what language to use depending on your system culture settings, such as pt-BR for Portuguese (Brazil).

Of course, we’d improved the performance of your Terminaux applications when it comes to prompting users for a huge list of selections, which is tedious on the processor. We are speaking huge amounts like 700,000 choices! The final release brings more, but Terminaux 7.0 Beta 4 is the start of such improvements!

Are you ready for Terminaux 7.0 Beta 4?

#C_ #dotnet #news #Tech #Technology #terminal #terminaux #Terminaux7 #Terminaux70 #update

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 #news #Programming #Tech #Technology #update #visualBasic #visualStudio #VisualStudio2025 #vs #VS2025

Terminaux 7.0 Beta 2 Announcement

Since the first beta, we have done improvements to several Terminaux components that will improve your user and your developer experience to build your Terminaux applications without worry. We are so excited to announce that, today, we will release the second beta version of Terminaux 7.0 that allows you to try out the new improved beta.

You can download the second beta version of Terminaux from NuGet by looking for version v7.0.0-beta2.

The mouse support has been improved, bringing several essential improvements to the mouse event handler to make sure that you will be able to handle those events easier than never before. With the renewed event listener code, you can now use such support to get mouse and keyboard events to process input and execute functions based on it. Whether it’s a left click or a key press, you can easily identify the event using a new class, InputEventInfo.

Also, we have improved mouse positioning on Linux systems by changing the protocol used from the legacy X10 protocol that had a very low limit for mouse cursor position to the modern SGR protocol that supports bigger console sizes. This makes sure that you can use Terminaux applications seamlessly in a large terminal size without having to resize it to a smaller one.

In addition to that, we have employed a better and a more performant reverse RTL code that allows your Arabic and other RTL scripts to be displayed correctly in your console, if it doesn’t reverse such scripts automatically. For RTL users, you can now benefit from those improvements to make sure that your Terminaux applications become usable in RTL systems.

Adding on top of those improvements, we have done some general improvements worth doing in the second beta, while the third beta will feature some more exciting improvements that will make your Terminaux applications stronger than never before.

Why not try out the second beta version of Terminaux 7.0?

#Net #beta #C_ #Console #csharp #dotnet #libraries #Library #news #Programming #Tech #Technology #terminal #terminaux #Terminaux7 #Terminaux70 #update

Terminaux 4.3.x EOL reminder

To go ahead with the development of Terminaux as a whole, we’ve decided to remind you about the end of support of Terminaux 4.3.x series. This end of support decision is important as we are going forward with the project.

Today, we’d like to remind you of the end of support for this version series of Terminaux on July 7th, 2025. After this date, we will no longer provide further updates for this series, including performance and security updates.

Such announcements are short, because the end of life for a version series means that we will no longer provide the following updates:

• Any new feature updates (if any)
• Any new security updates
• Any new general improvement updates

From now to July 7th, we are planning to halt all development in preparation for the end of life date, unless something serious crops up, just before the date. A notice will be made to remind users about this end of support date.

#C_ #csharp #dotnet #news #Programming #Tech #Technology #terminaux #Terminaux4 #Terminaux43X #update

GamesRadar: Sonic fans are leading the charge on a new preservation tool that can help give any Xbox 360 game a native PC port. “…this new tool, called XenonRecomp, simply gives fan developers a path to creating PC versions of Xbox 360 games. As the GitHub page explains, it ‘converts Xbox 360 executables into C++ code, which can then be recompiled for any platform.’ It’s not magic – you […]

https://rbfirehose.com/2025/03/06/gamesradar-sonic-fans-are-leading-the-charge-on-a-new-preservation-tool-that-can-help-give-any-xbox-360-game-a-native-pc-port/

[Перевод] Правительство США: критически важное программное обеспечение должно отказаться от C/C++ к 2026 году

31 октября 2024 года, 11:00, автор: Дэррил К. Тафт Это самая жёсткая позиция правительства в отношении безопасности программного обеспечения, которая предупреждает производителей: устраняйте опасные методы программирования, иначе вас могут обвинить в халатности. Федеральное правительство предупреждает об опасных методах разработки программного обеспечения. Агентство по кибербезопасности и защите инфраструктуры США (CISA) и Федеральное бюро расследований (ФБР) публикуют жёсткие предупреждения о нарушениях базовых мер безопасности, которые продолжают затрагивать критически важную инфраструктуру. В недавнем отчёте, опубликованном совместно CISA и ФБР, о недостаточных мерах обеспечения безопасности продуктов производители программного обеспечения предупреждаются о нежелательности использования небезопасных для памяти языков программирования, таких как C и C++. «Разработка новых линеек продуктов для использования в критически важной инфраструктуре или [национальных критически важных функциях] NCF на языке, небезопасном для памяти (например, C или C++), когда есть доступные альтернативные языки, безопасные для памяти, которые можно использовать, несет в себе угрозу и значительно повышает риск для национальной безопасности, национальной экономической безопасности, здоровья и безопасности населения», — говорится в отчёте.

https://habr.com/ru/articles/856804/

#C_++ #БЕЗОПАСНОСТЬ #РАЗРАБОТКА_ПРОГРАММНОГО_ОБЕСПЕЧЕНИЯ

This version of Ubuntu started the development with one of the most significant changes ever done. This time, it’s about compiler optimization level used on Ubuntu packages by default. When this version of Ubuntu had started its development, the mailing list entry said the following:

* perl 5.40 and haskell / ghc 9.6.6 already migrated to the releasepocket, to avoid entanglement with other transitions.* dpkg-buildflags defaults to -O3 instead of -O2. This might require changes in package builds. Please be aware that we already build with -O3 on ppc64el, so look for possible packaging adjustments.

While the Perl one is irrelevant in this blog post, the second entry in the toolchain changes is interesting. The default build flags for all Ubuntu packages that are determined by dpkg-buildflags have been changed so that -O3 is being used as a default instead of -O2.

This means that all future builds for all Plucky Puffin packages will be more optimized. Because of this, the build times will increase, but that doesn’t affect the end user. As a result, the packages that are built with the third optimization level will be faster than before, which means that your computer will be faster the second you upgrade to 25.04.

However, the binary size for the packages will be bigger, and there is uncertainty whether all packages benefit from this level of optimization that will be applied to all the packages. Furthermore, all builds and tests will be run, so expect delays. After that, when you test 25.04 during the development cycle, you should experience performance improvements.

On a side note, Perl 5.40 was released to Ubuntu 25.04, which brings several new features, new analyzers, and breaking changes, such as the :reader attribute for field variables, the breaking changes related to use VERSION declarations, the Infinity (inf) and Not-a-Number (nan) constants in builtin static class (module), the medium-precedence Logical XOR ^^ operator, the try...catch...finally block being a stable Perl feature, and stable support for multiple value iterations for the for loop.

Let’s see what Ubuntu 25.04 Plucky Puffin will offer as the next LTS, 26.04 RR, gets closer to the development period.

https://officialaptivi.wordpress.com/2024/11/04/ubuntu-25-04-plucky-puffins-packages-are-more-optimized/

#O2 #O3 #2504 #Acceleration #C #C_ #Computer #computers #GCC #GCCCompiler #improvements #Linux #LinuxUbuntu #news #Optimization #performance #Plucky #PluckyPuffin #speed #Tech #technology #Ubuntu #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2504Puffin #UbuntuLinux #ubuntulinux #update

I spent a decent chunk of my Sunday hunting an elusive memory leak in a tool that I wrote years ago and still maintain. The memory leak has always been slow enough that I hadn’t cared to fix it, but after running out of RAM and crashing my Raspberry Pi (again!), I’d had enough.

This tool performs HTTP and ICMP requests on a regular schedule. Given that I’d only see a memory-related issue after weeks of operation, and that most of the time nobody actually logs in to it to perform any maintenance tasks, it was pretty clear that the problem had to lie somewhere in the HTTP or ICMP request code.

I was pretty confident that it wasn’t the ICMP code, because it’s very small and straightforward. The HTTP code, however, is, shall we say, less concise. Not only does it handle a lot of options, but also its implementation is made complicated by the fact that I wanted that code to be testable, and HttpClient and many of its related classes are notoriously unmockable.

My testable solution from some time ago has been to add HttpClientHandler into the ASP.NET DI container and request a new (transient) one for each request. This way, my unit tests could use a fake version of this class and take over the actual network calls. This made for a somewhat awkward, but very nicely testable, class.

While investigating the memory leak (by calling the HTTP checking function 300 times between taking memory snapshots), I saw a lot of leftover delegates that were handling SSL cert validation, which were set up because the tool has an option for custom TLS validation. I wasted a lot of time trying to deal with validation event subscriptions and such. Those were not the problem, as it turned out.

The problem was my incorrect use of the DI container. Turns out, the documentation on its limitations is pretty clear:

* Don’t register IDisposable instances with a transient lifetime. Use the factory pattern instead.
* Don’t resolve IDisposable instances with a transient or scoped lifetime in the root scope. The only exception to this is if the app creates/recreates and disposes IServiceProvider, but this isn’t an ideal pattern.

https://learn.microsoft.com/en-us/dotnet/core/extensions/dependency-injection-guidelines#general-idisposable-guidelines

Yep, that HttpClientHandler that I shoved into the DI container was absolutely a transient IDisposable. Regardless of whether I was disposing of it myself, the container still kept a reference to it. That was the memory leak. As the above quote shows, the documentation even suggests a workaround: using the factory pattern.

Changing the code to use the factory pattern to create an HttpMessageHandler instance, which I switched to the more modern SocketsHttpHandler for production code, while keeping the fake HttpClientHandler for test code, was not a difficult task. And the memory leak is gone!

https://trycatch.dev/2024/03/24/finding-and-fixing-a-tricky-memory-leak-in-net-code/

#NET #C_ #Programming

Bringing C++ to Godot with GDExtensions

After playing with Godot within its own rules, I decided to check out what is the experience of bringing in external C++ code into a Godot project through their GDExtensions system. Using it, I bring over two different implementations of toyBrot into a regular Godot project. One with C++ threads and another with OpenCL, pushing Godot being its […]

https://vilelasagna.ddns.net/coding/bringing-c-to-godot-with-gdextensions/

By: @[email protected]
#c_ #coding #GDExtensions #Godot #godotengine #GPGPU #multithreading #OpenCL

Imparare a programmare giocando

Volete imparare a programmare giocando? Oppure siete già in grado ma volete mettere alla prova le vostre conoscenze? Abbiamo quello che fa per voi!

https://www.lealternative.net/2020/10/07/imparare-a-programmare-giocando/

So you wanted to multi your threading, huh?

An introduction to a series where I talk about different parallelisation technologies for C++, comparing different implementations of the same algorithm. In this one, modern C++ STL

https://vilelasagna.ddns.net/multi-your-threads/so-you-wanted-to-multi-your-threading-huh/

By: @[email protected]
#c_ #coding #multithreading #multiyourthreading