#c_ — Public Fediverse posts

Addressing plans for BassBoom and MediaBoom v1.0

Since BassBoom was released, it went through several iterations of improvements, including library updates and new features, such as the radio station playback support. Over time, we needed to extend support for more music extensions other than the MPEG ones, such as Advanced Audio Codec (AAC) files and wave files (WAV), so we were plotting a plan to create a separate experimental branch of BassBoom before we eventually called it MediaBoom, finally separated as a separate app.

The two versions, BassBoom v1.0 and MediaBoom v1.0, are currently being worked on as we focus on the more essential things to make sure that we provide you with the best BassBoom and MediaBoom releases. We will conduct thorough checks for every single line of code written in both projects. Currently, MediaBoom’s repository didn’t see any sign that the real development had started, beyond just experimental code that wrapped around libmpv.

Of course, all this planning and execution takes time, but when we take time, we do our due diligence to ensure that BassBoom v1.0 and MediaBoom v1.0 get released as soon as they’re ready.

Currently, there is no ETA as to when those two launches actually happen, but we will be more transparent about those two projects as soon as we start development on them.

#Net #bassboom #C_ #csharp #dotnet #MediaBoom #news #Tech #Technology #update

Addressing plans for BassBoom and MediaBoom v1.0

Since BassBoom was released, it went through several iterations of improvements, including library updates and new features, such as the radio station playback support. Over time, we needed to extend support for more music extensions other than the MPEG ones, such as Advanced Audio Codec (AAC) files and wave files (WAV), so we were plotting a plan to create a separate experimental branch of BassBoom before we eventually called it MediaBoom, finally separated as a separate app.

The two versions, BassBoom v1.0 and MediaBoom v1.0, are currently being worked on as we focus on the more essential things to make sure that we provide you with the best BassBoom and MediaBoom releases. We will conduct thorough checks for every single line of code written in both projects. Currently, MediaBoom’s repository didn’t see any sign that the real development had started, beyond just experimental code that wrapped around libmpv.

Of course, all this planning and execution takes time, but when we take time, we do our due diligence to ensure that BassBoom v1.0 and MediaBoom v1.0 get released as soon as they’re ready.

Currently, there is no ETA as to when those two launches actually happen, but we will be more transparent about those two projects as soon as we start development on them.

#Net #bassboom #C_ #csharp #dotnet #MediaBoom #news #Tech #Technology #update

Addressing plans for BassBoom and MediaBoom v1.0

Since BassBoom was released, it went through several iterations of improvements, including library updates and new features, such as the radio station playback support. Over time, we needed to extend support for more music extensions other than the MPEG ones, such as Advanced Audio Codec (AAC) files and wave files (WAV), so we were plotting a plan to create a separate experimental branch of BassBoom before we eventually called it MediaBoom, finally separated as a separate app.

The two versions, BassBoom v1.0 and MediaBoom v1.0, are currently being worked on as we focus on the more essential things to make sure that we provide you with the best BassBoom and MediaBoom releases. We will conduct thorough checks for every single line of code written in both projects. Currently, MediaBoom’s repository didn’t see any sign that the real development had started, beyond just experimental code that wrapped around libmpv.

Of course, all this planning and execution takes time, but when we take time, we do our due diligence to ensure that BassBoom v1.0 and MediaBoom v1.0 get released as soon as they’re ready.

Currently, there is no ETA as to when those two launches actually happen, but we will be more transparent about those two projects as soon as we start development on them.

Photo by Catherine Kalmykova on Unsplash

#Net #bassboom #C_ #csharp #dotnet #MediaBoom #news #Tech #Technology #update

Addressing plans for BassBoom and MediaBoom v1.0

Since BassBoom was released, it went through several iterations of improvements, including library updates and new features, such as the radio station playback support. Over time, we needed to extend support for more music extensions other than the MPEG ones, such as Advanced Audio Codec (AAC) files and wave files (WAV), so we were plotting a plan to create a separate experimental branch of BassBoom before we eventually called it MediaBoom, finally separated as a separate app.

The two versions, BassBoom v1.0 and MediaBoom v1.0, are currently being worked on as we focus on the more essential things to make sure that we provide you with the best BassBoom and MediaBoom releases. We will conduct thorough checks for every single line of code written in both projects. Currently, MediaBoom’s repository didn’t see any sign that the real development had started, beyond just experimental code that wrapped around libmpv.

Of course, all this planning and execution takes time, but when we take time, we do our due diligence to ensure that BassBoom v1.0 and MediaBoom v1.0 get released as soon as they’re ready.

Currently, there is no ETA as to when those two launches actually happen, but we will be more transparent about those two projects as soon as we start development on them.

#Net #bassboom #C_ #csharp #dotnet #MediaBoom #news #Tech #Technology #update

Addressing plans for BassBoom and MediaBoom v1.0

Since BassBoom was released, it went through several iterations of improvements, including library updates and new features, such as the radio station playback support. Over time, we needed to extend support for more music extensions other than the MPEG ones, such as Advanced Audio Codec (AAC) files and wave files (WAV), so we were plotting a plan to create a separate experimental branch of BassBoom before we eventually called it MediaBoom, finally separated as a separate app.

The two versions, BassBoom v1.0 and MediaBoom v1.0, are currently being worked on as we focus on the more essential things to make sure that we provide you with the best BassBoom and MediaBoom releases. We will conduct thorough checks for every single line of code written in both projects. Currently, MediaBoom’s repository didn’t see any sign that the real development had started, beyond just experimental code that wrapped around libmpv.

Of course, all this planning and execution takes time, but when we take time, we do our due diligence to ensure that BassBoom v1.0 and MediaBoom v1.0 get released as soon as they’re ready.

Currently, there is no ETA as to when those two launches actually happen, but we will be more transparent about those two projects as soon as we start development on them.

#Net #bassboom #C_ #csharp #dotnet #MediaBoom #news #Tech #Technology #update

Get ready for .NET Conf 2025 on November 11th!

As we are approaching to the final release of .NET 10.0, a conference for .NET developers has been finally set to be scheduled for November 11th, and this event lasts three days up to November 13th. This conference talks about what’s new in .NET 10.0 and Visual Studio 2026, where they both introduce new features and improvements to enhance your developer experience.

Joining the conference is free, and you can mark the schedule on your calendar using the below button.

The below main events will happen in this conference:

• November 11th (8 AM to 6 PM PST): This is a big day for .NET developers where .NET 10.0 and Visual Studio 2026 will be showcased for new features and improvements, as well as the Code Party that you can win some great prizes.
• November 12th (9 AM to 5 PM PST): This showcases a deep dive into .NET, Azure, and AI.
• November 13th (5 AM to 5 PM PST): This is a community event with speakers around the world.

After the main events, there comes two additional days, which are the Student Zone on November 14th that is a beginner-friendly virtual event where experts teach you how to build awesome projects using C# and .NET, and November 13th to 15th where the community events are held.

There will also be giveaways and digital swags where you receive them with many valuable perks, such as digital goods worth over $5,500, like high-value software licenses and other goodies.

The speakers in this conference event will be (in alphabetical order):

• Allie Barry
• Brady Gaster
• Cathy Sullivan
• Damian Edwards
• David Fowler
• Gaurav Seth
• Maddy Montaquila
• Mads Kristensen
• Maria Naggaga Nakanwagi
• Mike Kistler
• Rachel King
• Safia Abdalla
• Scott Hanselman

Join the .NET Conf for free!

#Net #Net10 #Net100 #NETConf #NETConf2025 #C_ #dotnet #F_ #fsharp #news #Tech #Technology #update #VB

Get ready for .NET Conf 2025 on November 11th!

As we are approaching to the final release of .NET 10.0, a conference for .NET developers has been finally set to be scheduled for November 11th, and this event lasts three days up to November 13th. This conference talks about what’s new in .NET 10.0 and Visual Studio 2026, where they both introduce new features and improvements to enhance your developer experience.

Joining the conference is free, and you can mark the schedule on your calendar using the below button.

The below main events will happen in this conference:

• November 11th (8 AM to 6 PM PST): This is a big day for .NET developers where .NET 10.0 and Visual Studio 2026 will be showcased for new features and improvements, as well as the Code Party that you can win some great prizes.
• November 12th (9 AM to 5 PM PST): This showcases a deep dive into .NET, Azure, and AI.
• November 13th (5 AM to 5 PM PST): This is a community event with speakers around the world.

After the main events, there comes two additional days, which are the Student Zone on November 14th that is a beginner-friendly virtual event where experts teach you how to build awesome projects using C# and .NET, and November 13th to 15th where the community events are held.

There will also be giveaways and digital swags where you receive them with many valuable perks, such as digital goods worth over $5,500, like high-value software licenses and other goodies.

The speakers in this conference event will be (in alphabetical order):

• Allie Barry
• Brady Gaster
• Cathy Sullivan
• Damian Edwards
• David Fowler
• Gaurav Seth
• Maddy Montaquila
• Mads Kristensen
• Maria Naggaga Nakanwagi
• Mike Kistler
• Rachel King
• Safia Abdalla
• Scott Hanselman

Join the .NET Conf for free!

#Net #Net10 #Net100 #NETConf #NETConf2025 #C_ #dotnet #F_ #fsharp #news #Tech #Technology #update #VB

Get ready for .NET Conf 2025 on November 11th!

As we are approaching to the final release of .NET 10.0, a conference for .NET developers has been finally set to be scheduled for November 11th, and this event lasts three days up to November 13th. This conference talks about what’s new in .NET 10.0 and Visual Studio 2026, where they both introduce new features and improvements to enhance your developer experience.

Joining the conference is free, and you can mark the schedule on your calendar using the below button.

The below main events will happen in this conference:

• November 11th (8 AM to 6 PM PST): This is a big day for .NET developers where .NET 10.0 and Visual Studio 2026 will be showcased for new features and improvements, as well as the Code Party that you can win some great prizes.
• November 12th (9 AM to 5 PM PST): This showcases a deep dive into .NET, Azure, and AI.
• November 13th (5 AM to 5 PM PST): This is a community event with speakers around the world.

After the main events, there comes two additional days, which are the Student Zone on November 14th that is a beginner-friendly virtual event where experts teach you how to build awesome projects using C# and .NET, and November 13th to 15th where the community events are held.

There will also be giveaways and digital swags where you receive them with many valuable perks, such as digital goods worth over $5,500, like high-value software licenses and other goodies.

The speakers in this conference event will be (in alphabetical order):

• Allie Barry
• Brady Gaster
• Cathy Sullivan
• Damian Edwards
• David Fowler
• Gaurav Seth
• Maddy Montaquila
• Mads Kristensen
• Maria Naggaga Nakanwagi
• Mike Kistler
• Rachel King
• Safia Abdalla
• Scott Hanselman

Join the .NET Conf for free!

#Net #Net10 #Net100 #NETConf #NETConf2025 #C_ #dotnet #F_ #fsharp #news #Tech #Technology #update #VB

Get ready for .NET Conf 2025 on November 11th!

As we are approaching to the final release of .NET 10.0, a conference for .NET developers has been finally set to be scheduled for November 11th, and this event lasts three days up to November 13th. This conference talks about what’s new in .NET 10.0 and Visual Studio 2026, where they both introduce new features and improvements to enhance your developer experience.

Joining the conference is free, and you can mark the schedule on your calendar using the below button.

The below main events will happen in this conference:

• November 11th (8 AM to 6 PM PST): This is a big day for .NET developers where .NET 10.0 and Visual Studio 2026 will be showcased for new features and improvements, as well as the Code Party that you can win some great prizes.
• November 12th (9 AM to 5 PM PST): This showcases a deep dive into .NET, Azure, and AI.
• November 13th (5 AM to 5 PM PST): This is a community event with speakers around the world.

After the main events, there comes two additional days, which are the Student Zone on November 14th that is a beginner-friendly virtual event where experts teach you how to build awesome projects using C# and .NET, and November 13th to 15th where the community events are held.

There will also be giveaways and digital swags where you receive them with many valuable perks, such as digital goods worth over $5,500, like high-value software licenses and other goodies.

The speakers in this conference event will be (in alphabetical order):

• Allie Barry
• Brady Gaster
• Cathy Sullivan
• Damian Edwards
• David Fowler
• Gaurav Seth
• Maddy Montaquila
• Mads Kristensen
• Maria Naggaga Nakanwagi
• Mike Kistler
• Rachel King
• Safia Abdalla
• Scott Hanselman

Join the .NET Conf for free!

#Net #Net10 #Net100 #NETConf #NETConf2025 #C_ #dotnet #F_ #fsharp #news #Tech #Technology #update #VB

Get ready for .NET Conf 2025 on November 11th!

As we are approaching to the final release of .NET 10.0, a conference for .NET developers has been finally set to be scheduled for November 11th, and this event lasts three days up to November 13th. This conference talks about what’s new in .NET 10.0 and Visual Studio 2026, where they both introduce new features and improvements to enhance your developer experience.

Joining the conference is free, and you can mark the schedule on your calendar using the below button.

The below main events will happen in this conference:

• November 11th (8 AM to 6 PM PST): This is a big day for .NET developers where .NET 10.0 and Visual Studio 2026 will be showcased for new features and improvements, as well as the Code Party that you can win some great prizes.
• November 12th (9 AM to 5 PM PST): This showcases a deep dive into .NET, Azure, and AI.
• November 13th (5 AM to 5 PM PST): This is a community event with speakers around the world.

After the main events, there comes two additional days, which are the Student Zone on November 14th that is a beginner-friendly virtual event where experts teach you how to build awesome projects using C# and .NET, and November 13th to 15th where the community events are held.

There will also be giveaways and digital swags where you receive them with many valuable perks, such as digital goods worth over $5,500, like high-value software licenses and other goodies.

The speakers in this conference event will be (in alphabetical order):

• Allie Barry
• Brady Gaster
• Cathy Sullivan
• Damian Edwards
• David Fowler
• Gaurav Seth
• Maddy Montaquila
• Mads Kristensen
• Maria Naggaga Nakanwagi
• Mike Kistler
• Rachel King
• Safia Abdalla
• Scott Hanselman

Join the .NET Conf for free!

#Net #Net10 #Net100 #NETConf #NETConf2025 #C_ #dotnet #F_ #fsharp #news #Tech #Technology #update #VB

LocaleStation’s Deprecation

LocaleStation was released as part of the ongoing effort back in June 2025 to give all our libraries a chance to be translatable to your native language. This kind of effort was studied under the assumption that we’d achieve simpler and faster localization. However, our expectations fell short when we had discovered the massive first startup performance impact on Windows systems.

This performance impact was especially noticeable on Windows systems where applications like Nitrocid would suffer from longer startup times in both the main application entry point and the addon loading point. This slow down is considered to be unacceptable, especially when an “unrelated” feature would cause this slow down. This is because of the Windows Defender’s Antimalware Service Executable process taking up a majority of the CPU cycles in analyzing the localization files in the first JIT compilation of all libraries and applications that depend on LocaleStation’s generated files.

As a result, we’ve decided to shut down LocaleStation as a library, and convert all the existing JSON files, with appropriate modifications, to a standard culture-specific resources file that is managed by .NET.

With Terminaux, we’ve conducted an experimental branch based on the Terminaux 8.0.0 branch that can be found in the x/exp/v8.0.x-loc-resx-poc branch. We’ve used an internal program that converts LocaleStation-compatible JSON files that you can see like below:

{    "lang": "eng",    "name": "English",    "cultures": [ "en-US", "en-GB" ],    "locs": [        {            "loc": "TEXT_HELLO_WORLD",            "text": "Hello world!"        },        {            "loc": "TEXT_HI",            "text": "Hi!"        }    ]}

…to the .resx format as in below:

<?xml version="1.0" encoding="utf-8"?><root>    <!--     Microsoft ResX Schema     Version 2.0    The primary goals of this format is to allow a simple XML format     that is mostly human readable. The generation and parsing of the     various data types are done through the TypeConverter classes     associated with the data types.    Example:    ... ado.net/XML headers & schema ...    <resheader name="resmimetype">text/microsoft-resx</resheader>    <resheader name="version">2.0</resheader>    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">        <value>[base64 mime encoded serialized .NET Framework object]</value>    </data>    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>        <comment>This is a comment</comment>    </data>    There are any number of "resheader" rows that contain simple     name/value pairs.    Each data row contains a name, and value. The row also contains a     type or mimetype. Type corresponds to a .NET class that support     text/value conversion through the TypeConverter architecture.     Classes that don't support this are serialized and stored with the     mimetype set.    The mimetype is used for serialized objects, and tells the     ResXResourceReader how to depersist the object. This is currently not     extensible. For a given mimetype the value must be set accordingly:    Note - application/x-microsoft.net.object.binary.base64 is the format     that the ResXResourceWriter will generate, however the reader can     read any of the formats listed below.    mimetype: application/x-microsoft.net.object.binary.base64    value   : The object must be serialized with             : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter            : and then encoded with base64 encoding.    mimetype: application/x-microsoft.net.object.soap.base64    value   : The object must be serialized with             : System.Runtime.Serialization.Formatters.Soap.SoapFormatter            : and then encoded with base64 encoding.    mimetype: application/x-microsoft.net.object.bytearray.base64    value   : The object must be serialized into a byte array             : using a System.ComponentModel.TypeConverter            : and then encoded with base64 encoding.    -->    <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />    <xsd:element name="root" msdata:IsDataSet="true">        <xsd:complexType>        <xsd:choice maxOccurs="unbounded">            <xsd:element name="metadata">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" />                </xsd:sequence>                <xsd:attribute name="name" use="required" type="xsd:string" />                <xsd:attribute name="type" type="xsd:string" />                <xsd:attribute name="mimetype" type="xsd:string" />                <xsd:attribute ref="xml:space" />            </xsd:complexType>            </xsd:element>            <xsd:element name="assembly">            <xsd:complexType>                <xsd:attribute name="alias" type="xsd:string" />                <xsd:attribute name="name" type="xsd:string" />            </xsd:complexType>            </xsd:element>            <xsd:element name="data">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />                </xsd:sequence>                <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />                <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />                <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />                <xsd:attribute ref="xml:space" />            </xsd:complexType>            </xsd:element>            <xsd:element name="resheader">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />                </xsd:sequence>                <xsd:attribute name="name" type="xsd:string" use="required" />            </xsd:complexType>            </xsd:element>        </xsd:choice>        </xsd:complexType>    </xsd:element>    </xsd:schema>    <resheader name="resmimetype">    <value>text/microsoft-resx</value>    </resheader>    <resheader name="version">    <value>2.0</value>    </resheader>    <resheader name="reader">    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>    </resheader>    <resheader name="writer">    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>    </resheader>      <data name="NKS_COMMON_ANYKEY" xml:space="preserve">    <value>Press any key to continue...</value>  </data>  <data name="NKS_KERNEL_NOAPMSIMULATION" xml:space="preserve">    <value>It&apos;s now safe to turn off your computer.</value>  </data>  <data name="NKS_KERNEL_ENVERROR" xml:space="preserve">    <value>Kernel environment error:</value>  </data>  <data name="NKS_KERNEL_FATALERROR" xml:space="preserve">    <value>Nitrocid KS has detected a problem and it has been shut down.</value>  </data>  <data name="NKS_KERNEL_STARTING_DEVMESSAGE" xml:space="preserve">    <value>You&apos;re running the development version of the kernel. While you can experience upcoming features which may exist in the final release, you may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_RCMESSAGE" xml:space="preserve">    <value>You&apos;re running the release candidate version of the kernel. While you can experience the final touches, you may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_UNSUPPORTED" xml:space="preserve">    <value>We recommend against running this version of the kernel, because it is unsupported. If you have downloaded this kernel from unknown sources, this message may appear. Please download from our official downloads page.</value>  </data>  <data name="NKS_KERNEL_STARTING_ALPHAMESSAGE" xml:space="preserve">    <value>You&apos;re running the alpha version of the kernel. You may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_BETAMESSAGE" xml:space="preserve">    <value>You&apos;re running the beta version of the kernel. You may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data></root>

Our recent experiments proved that the resources method was faster than the LocaleStation method when it comes to first startup times due to Windows Defender. We have removed this library from the list of supported libraries, and that all development of LocaleStation will stop.

The specification will remain maintained, and the Aptivi Development Toolkit (ADT) will provide tools that we’ve developed internally to make dealing with those files easier than before.

We are still working on the rollout of the .resx file for all libraries, and this may take multiple library releases, depending on the severity of the situation.

#C_ #csharp #dotnet #Language #libraries #Library #Localization #news #Tech #Technology #update

LocaleStation’s Deprecation

LocaleStation was released as part of the ongoing effort back in June 2025 to give all our libraries a chance to be translatable to your native language. This kind of effort was studied under the assumption that we’d achieve simpler and faster localization. However, our expectations fell short when we had discovered the massive first startup performance impact on Windows systems.

This performance impact was especially noticeable on Windows systems where applications like Nitrocid would suffer from longer startup times in both the main application entry point and the addon loading point. This slow down is considered to be unacceptable, especially when an “unrelated” feature would cause this slow down. This is because of the Windows Defender’s Antimalware Service Executable process taking up a majority of the CPU cycles in analyzing the localization files in the first JIT compilation of all libraries and applications that depend on LocaleStation’s generated files.

As a result, we’ve decided to shut down LocaleStation as a library, and convert all the existing JSON files, with appropriate modifications, to a standard culture-specific resources file that is managed by .NET.

With Terminaux, we’ve conducted an experimental branch based on the Terminaux 8.0.0 branch that can be found in the x/exp/v8.0.x-loc-resx-poc branch. We’ve used an internal program that converts LocaleStation-compatible JSON files that you can see like below:

{    "lang": "eng",    "name": "English",    "cultures": [ "en-US", "en-GB" ],    "locs": [        {            "loc": "TEXT_HELLO_WORLD",            "text": "Hello world!"        },        {            "loc": "TEXT_HI",            "text": "Hi!"        }    ]}

…to the .resx format as in below:

<?xml version="1.0" encoding="utf-8"?><root>    <!--     Microsoft ResX Schema     Version 2.0    The primary goals of this format is to allow a simple XML format     that is mostly human readable. The generation and parsing of the     various data types are done through the TypeConverter classes     associated with the data types.    Example:    ... ado.net/XML headers & schema ...    <resheader name="resmimetype">text/microsoft-resx</resheader>    <resheader name="version">2.0</resheader>    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">        <value>[base64 mime encoded serialized .NET Framework object]</value>    </data>    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>        <comment>This is a comment</comment>    </data>    There are any number of "resheader" rows that contain simple     name/value pairs.    Each data row contains a name, and value. The row also contains a     type or mimetype. Type corresponds to a .NET class that support     text/value conversion through the TypeConverter architecture.     Classes that don't support this are serialized and stored with the     mimetype set.    The mimetype is used for serialized objects, and tells the     ResXResourceReader how to depersist the object. This is currently not     extensible. For a given mimetype the value must be set accordingly:    Note - application/x-microsoft.net.object.binary.base64 is the format     that the ResXResourceWriter will generate, however the reader can     read any of the formats listed below.    mimetype: application/x-microsoft.net.object.binary.base64    value   : The object must be serialized with             : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter            : and then encoded with base64 encoding.    mimetype: application/x-microsoft.net.object.soap.base64    value   : The object must be serialized with             : System.Runtime.Serialization.Formatters.Soap.SoapFormatter            : and then encoded with base64 encoding.    mimetype: application/x-microsoft.net.object.bytearray.base64    value   : The object must be serialized into a byte array             : using a System.ComponentModel.TypeConverter            : and then encoded with base64 encoding.    -->    <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />    <xsd:element name="root" msdata:IsDataSet="true">        <xsd:complexType>        <xsd:choice maxOccurs="unbounded">            <xsd:element name="metadata">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" />                </xsd:sequence>                <xsd:attribute name="name" use="required" type="xsd:string" />                <xsd:attribute name="type" type="xsd:string" />                <xsd:attribute name="mimetype" type="xsd:string" />                <xsd:attribute ref="xml:space" />            </xsd:complexType>            </xsd:element>            <xsd:element name="assembly">            <xsd:complexType>                <xsd:attribute name="alias" type="xsd:string" />                <xsd:attribute name="name" type="xsd:string" />            </xsd:complexType>            </xsd:element>            <xsd:element name="data">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />                </xsd:sequence>                <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />                <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />                <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />                <xsd:attribute ref="xml:space" />            </xsd:complexType>            </xsd:element>            <xsd:element name="resheader">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />                </xsd:sequence>                <xsd:attribute name="name" type="xsd:string" use="required" />            </xsd:complexType>            </xsd:element>        </xsd:choice>        </xsd:complexType>    </xsd:element>    </xsd:schema>    <resheader name="resmimetype">    <value>text/microsoft-resx</value>    </resheader>    <resheader name="version">    <value>2.0</value>    </resheader>    <resheader name="reader">    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>    </resheader>    <resheader name="writer">    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>    </resheader>      <data name="NKS_COMMON_ANYKEY" xml:space="preserve">    <value>Press any key to continue...</value>  </data>  <data name="NKS_KERNEL_NOAPMSIMULATION" xml:space="preserve">    <value>It&apos;s now safe to turn off your computer.</value>  </data>  <data name="NKS_KERNEL_ENVERROR" xml:space="preserve">    <value>Kernel environment error:</value>  </data>  <data name="NKS_KERNEL_FATALERROR" xml:space="preserve">    <value>Nitrocid KS has detected a problem and it has been shut down.</value>  </data>  <data name="NKS_KERNEL_STARTING_DEVMESSAGE" xml:space="preserve">    <value>You&apos;re running the development version of the kernel. While you can experience upcoming features which may exist in the final release, you may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_RCMESSAGE" xml:space="preserve">    <value>You&apos;re running the release candidate version of the kernel. While you can experience the final touches, you may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_UNSUPPORTED" xml:space="preserve">    <value>We recommend against running this version of the kernel, because it is unsupported. If you have downloaded this kernel from unknown sources, this message may appear. Please download from our official downloads page.</value>  </data>  <data name="NKS_KERNEL_STARTING_ALPHAMESSAGE" xml:space="preserve">    <value>You&apos;re running the alpha version of the kernel. You may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_BETAMESSAGE" xml:space="preserve">    <value>You&apos;re running the beta version of the kernel. You may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data></root>

Our recent experiments proved that the resources method was faster than the LocaleStation method when it comes to first startup times due to Windows Defender. We have removed this library from the list of supported libraries, and that all development of LocaleStation will stop.

The specification will remain maintained, and the Aptivi Development Toolkit (ADT) will provide tools that we’ve developed internally to make dealing with those files easier than before.

We are still working on the rollout of the .resx file for all libraries, and this may take multiple library releases, depending on the severity of the situation.

#C_ #csharp #dotnet #Language #libraries #Library #Localization #news #Tech #Technology #update

LocaleStation’s Deprecation

LocaleStation was released as part of the ongoing effort back in June 2025 to give all our libraries a chance to be translatable to your native language. This kind of effort was studied under the assumption that we’d achieve simpler and faster localization. However, our expectations fell short when we had discovered the massive first startup performance impact on Windows systems.

This performance impact was especially noticeable on Windows systems where applications like Nitrocid would suffer from longer startup times in both the main application entry point and the addon loading point. This slow down is considered to be unacceptable, especially when an “unrelated” feature would cause this slow down. This is because of the Windows Defender’s Antimalware Service Executable process taking up a majority of the CPU cycles in analyzing the localization files in the first JIT compilation of all libraries and applications that depend on LocaleStation’s generated files.

As a result, we’ve decided to shut down LocaleStation as a library, and convert all the existing JSON files, with appropriate modifications, to a standard culture-specific resources file that is managed by .NET.

With Terminaux, we’ve conducted an experimental branch based on the Terminaux 8.0.0 branch that can be found in the x/exp/v8.0.x-loc-resx-poc branch. We’ve used an internal program that converts LocaleStation-compatible JSON files that you can see like below:

{    "lang": "eng",    "name": "English",    "cultures": [ "en-US", "en-GB" ],    "locs": [        {            "loc": "TEXT_HELLO_WORLD",            "text": "Hello world!"        },        {            "loc": "TEXT_HI",            "text": "Hi!"        }    ]}

…to the .resx format as in below:

<?xml version="1.0" encoding="utf-8"?><root>    <!--     Microsoft ResX Schema     Version 2.0    The primary goals of this format is to allow a simple XML format     that is mostly human readable. The generation and parsing of the     various data types are done through the TypeConverter classes     associated with the data types.    Example:    ... ado.net/XML headers & schema ...    <resheader name="resmimetype">text/microsoft-resx</resheader>    <resheader name="version">2.0</resheader>    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">        <value>[base64 mime encoded serialized .NET Framework object]</value>    </data>    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>        <comment>This is a comment</comment>    </data>    There are any number of "resheader" rows that contain simple     name/value pairs.    Each data row contains a name, and value. The row also contains a     type or mimetype. Type corresponds to a .NET class that support     text/value conversion through the TypeConverter architecture.     Classes that don't support this are serialized and stored with the     mimetype set.    The mimetype is used for serialized objects, and tells the     ResXResourceReader how to depersist the object. This is currently not     extensible. For a given mimetype the value must be set accordingly:    Note - application/x-microsoft.net.object.binary.base64 is the format     that the ResXResourceWriter will generate, however the reader can     read any of the formats listed below.    mimetype: application/x-microsoft.net.object.binary.base64    value   : The object must be serialized with             : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter            : and then encoded with base64 encoding.    mimetype: application/x-microsoft.net.object.soap.base64    value   : The object must be serialized with             : System.Runtime.Serialization.Formatters.Soap.SoapFormatter            : and then encoded with base64 encoding.    mimetype: application/x-microsoft.net.object.bytearray.base64    value   : The object must be serialized into a byte array             : using a System.ComponentModel.TypeConverter            : and then encoded with base64 encoding.    -->    <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />    <xsd:element name="root" msdata:IsDataSet="true">        <xsd:complexType>        <xsd:choice maxOccurs="unbounded">            <xsd:element name="metadata">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" />                </xsd:sequence>                <xsd:attribute name="name" use="required" type="xsd:string" />                <xsd:attribute name="type" type="xsd:string" />                <xsd:attribute name="mimetype" type="xsd:string" />                <xsd:attribute ref="xml:space" />            </xsd:complexType>            </xsd:element>            <xsd:element name="assembly">            <xsd:complexType>                <xsd:attribute name="alias" type="xsd:string" />                <xsd:attribute name="name" type="xsd:string" />            </xsd:complexType>            </xsd:element>            <xsd:element name="data">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />                </xsd:sequence>                <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />                <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />                <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />                <xsd:attribute ref="xml:space" />            </xsd:complexType>            </xsd:element>            <xsd:element name="resheader">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />                </xsd:sequence>                <xsd:attribute name="name" type="xsd:string" use="required" />            </xsd:complexType>            </xsd:element>        </xsd:choice>        </xsd:complexType>    </xsd:element>    </xsd:schema>    <resheader name="resmimetype">    <value>text/microsoft-resx</value>    </resheader>    <resheader name="version">    <value>2.0</value>    </resheader>    <resheader name="reader">    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>    </resheader>    <resheader name="writer">    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>    </resheader>      <data name="NKS_COMMON_ANYKEY" xml:space="preserve">    <value>Press any key to continue...</value>  </data>  <data name="NKS_KERNEL_NOAPMSIMULATION" xml:space="preserve">    <value>It&apos;s now safe to turn off your computer.</value>  </data>  <data name="NKS_KERNEL_ENVERROR" xml:space="preserve">    <value>Kernel environment error:</value>  </data>  <data name="NKS_KERNEL_FATALERROR" xml:space="preserve">    <value>Nitrocid KS has detected a problem and it has been shut down.</value>  </data>  <data name="NKS_KERNEL_STARTING_DEVMESSAGE" xml:space="preserve">    <value>You&apos;re running the development version of the kernel. While you can experience upcoming features which may exist in the final release, you may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_RCMESSAGE" xml:space="preserve">    <value>You&apos;re running the release candidate version of the kernel. While you can experience the final touches, you may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_UNSUPPORTED" xml:space="preserve">    <value>We recommend against running this version of the kernel, because it is unsupported. If you have downloaded this kernel from unknown sources, this message may appear. Please download from our official downloads page.</value>  </data>  <data name="NKS_KERNEL_STARTING_ALPHAMESSAGE" xml:space="preserve">    <value>You&apos;re running the alpha version of the kernel. You may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_BETAMESSAGE" xml:space="preserve">    <value>You&apos;re running the beta version of the kernel. You may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data></root>

Our recent experiments proved that the resources method was faster than the LocaleStation method when it comes to first startup times due to Windows Defender. We have removed this library from the list of supported libraries, and that all development of LocaleStation will stop.

The specification will remain maintained, and the Aptivi Development Toolkit (ADT) will provide tools that we’ve developed internally to make dealing with those files easier than before.

We are still working on the rollout of the .resx file for all libraries, and this may take multiple library releases, depending on the severity of the situation.

#C_ #csharp #dotnet #Language #libraries #Library #Localization #news #Tech #Technology #update

LocaleStation’s Deprecation

LocaleStation was released as part of the ongoing effort back in June 2025 to give all our libraries a chance to be translatable to your native language. This kind of effort was studied under the assumption that we’d achieve simpler and faster localization. However, our expectations fell short when we had discovered the massive first startup performance impact on Windows systems.

This performance impact was especially noticeable on Windows systems where applications like Nitrocid would suffer from longer startup times in both the main application entry point and the addon loading point. This slow down is considered to be unacceptable, especially when an “unrelated” feature would cause this slow down. This is because of the Windows Defender’s Antimalware Service Executable process taking up a majority of the CPU cycles in analyzing the localization files in the first JIT compilation of all libraries and applications that depend on LocaleStation’s generated files.

As a result, we’ve decided to shut down LocaleStation as a library, and convert all the existing JSON files, with appropriate modifications, to a standard culture-specific resources file that is managed by .NET.

With Terminaux, we’ve conducted an experimental branch based on the Terminaux 8.0.0 branch that can be found in the x/exp/v8.0.x-loc-resx-poc branch. We’ve used an internal program that converts LocaleStation-compatible JSON files that you can see like below:

{    "lang": "eng",    "name": "English",    "cultures": [ "en-US", "en-GB" ],    "locs": [        {            "loc": "TEXT_HELLO_WORLD",            "text": "Hello world!"        },        {            "loc": "TEXT_HI",            "text": "Hi!"        }    ]}

…to the .resx format as in below:

<?xml version="1.0" encoding="utf-8"?><root>    <!--     Microsoft ResX Schema     Version 2.0    The primary goals of this format is to allow a simple XML format     that is mostly human readable. The generation and parsing of the     various data types are done through the TypeConverter classes     associated with the data types.    Example:    ... ado.net/XML headers & schema ...    <resheader name="resmimetype">text/microsoft-resx</resheader>    <resheader name="version">2.0</resheader>    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">        <value>[base64 mime encoded serialized .NET Framework object]</value>    </data>    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>        <comment>This is a comment</comment>    </data>    There are any number of "resheader" rows that contain simple     name/value pairs.    Each data row contains a name, and value. The row also contains a     type or mimetype. Type corresponds to a .NET class that support     text/value conversion through the TypeConverter architecture.     Classes that don't support this are serialized and stored with the     mimetype set.    The mimetype is used for serialized objects, and tells the     ResXResourceReader how to depersist the object. This is currently not     extensible. For a given mimetype the value must be set accordingly:    Note - application/x-microsoft.net.object.binary.base64 is the format     that the ResXResourceWriter will generate, however the reader can     read any of the formats listed below.    mimetype: application/x-microsoft.net.object.binary.base64    value   : The object must be serialized with             : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter            : and then encoded with base64 encoding.    mimetype: application/x-microsoft.net.object.soap.base64    value   : The object must be serialized with             : System.Runtime.Serialization.Formatters.Soap.SoapFormatter            : and then encoded with base64 encoding.    mimetype: application/x-microsoft.net.object.bytearray.base64    value   : The object must be serialized into a byte array             : using a System.ComponentModel.TypeConverter            : and then encoded with base64 encoding.    -->    <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />    <xsd:element name="root" msdata:IsDataSet="true">        <xsd:complexType>        <xsd:choice maxOccurs="unbounded">            <xsd:element name="metadata">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" />                </xsd:sequence>                <xsd:attribute name="name" use="required" type="xsd:string" />                <xsd:attribute name="type" type="xsd:string" />                <xsd:attribute name="mimetype" type="xsd:string" />                <xsd:attribute ref="xml:space" />            </xsd:complexType>            </xsd:element>            <xsd:element name="assembly">            <xsd:complexType>                <xsd:attribute name="alias" type="xsd:string" />                <xsd:attribute name="name" type="xsd:string" />            </xsd:complexType>            </xsd:element>            <xsd:element name="data">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />                </xsd:sequence>                <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />                <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />                <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />                <xsd:attribute ref="xml:space" />            </xsd:complexType>            </xsd:element>            <xsd:element name="resheader">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />                </xsd:sequence>                <xsd:attribute name="name" type="xsd:string" use="required" />            </xsd:complexType>            </xsd:element>        </xsd:choice>        </xsd:complexType>    </xsd:element>    </xsd:schema>    <resheader name="resmimetype">    <value>text/microsoft-resx</value>    </resheader>    <resheader name="version">    <value>2.0</value>    </resheader>    <resheader name="reader">    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>    </resheader>    <resheader name="writer">    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>    </resheader>      <data name="NKS_COMMON_ANYKEY" xml:space="preserve">    <value>Press any key to continue...</value>  </data>  <data name="NKS_KERNEL_NOAPMSIMULATION" xml:space="preserve">    <value>It&apos;s now safe to turn off your computer.</value>  </data>  <data name="NKS_KERNEL_ENVERROR" xml:space="preserve">    <value>Kernel environment error:</value>  </data>  <data name="NKS_KERNEL_FATALERROR" xml:space="preserve">    <value>Nitrocid KS has detected a problem and it has been shut down.</value>  </data>  <data name="NKS_KERNEL_STARTING_DEVMESSAGE" xml:space="preserve">    <value>You&apos;re running the development version of the kernel. While you can experience upcoming features which may exist in the final release, you may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_RCMESSAGE" xml:space="preserve">    <value>You&apos;re running the release candidate version of the kernel. While you can experience the final touches, you may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_UNSUPPORTED" xml:space="preserve">    <value>We recommend against running this version of the kernel, because it is unsupported. If you have downloaded this kernel from unknown sources, this message may appear. Please download from our official downloads page.</value>  </data>  <data name="NKS_KERNEL_STARTING_ALPHAMESSAGE" xml:space="preserve">    <value>You&apos;re running the alpha version of the kernel. You may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_BETAMESSAGE" xml:space="preserve">    <value>You&apos;re running the beta version of the kernel. You may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data></root>

Our recent experiments proved that the resources method was faster than the LocaleStation method when it comes to first startup times due to Windows Defender. We have removed this library from the list of supported libraries, and that all development of LocaleStation will stop.

The specification will remain maintained, and the Aptivi Development Toolkit (ADT) will provide tools that we’ve developed internally to make dealing with those files easier than before.

We are still working on the rollout of the .resx file for all libraries, and this may take multiple library releases, depending on the severity of the situation.

#C_ #csharp #dotnet #Language #libraries #Library #Localization #news #Tech #Technology #update

LocaleStation’s Deprecation

LocaleStation was released as part of the ongoing effort back in June 2025 to give all our libraries a chance to be translatable to your native language. This kind of effort was studied under the assumption that we’d achieve simpler and faster localization. However, our expectations fell short when we had discovered the massive first startup performance impact on Windows systems.

This performance impact was especially noticeable on Windows systems where applications like Nitrocid would suffer from longer startup times in both the main application entry point and the addon loading point. This slow down is considered to be unacceptable, especially when an “unrelated” feature would cause this slow down. This is because of the Windows Defender’s Antimalware Service Executable process taking up a majority of the CPU cycles in analyzing the localization files in the first JIT compilation of all libraries and applications that depend on LocaleStation’s generated files.

As a result, we’ve decided to shut down LocaleStation as a library, and convert all the existing JSON files, with appropriate modifications, to a standard culture-specific resources file that is managed by .NET.

With Terminaux, we’ve conducted an experimental branch based on the Terminaux 8.0.0 branch that can be found in the x/exp/v8.0.x-loc-resx-poc branch. We’ve used an internal program that converts LocaleStation-compatible JSON files that you can see like below:

{    "lang": "eng",    "name": "English",    "cultures": [ "en-US", "en-GB" ],    "locs": [        {            "loc": "TEXT_HELLO_WORLD",            "text": "Hello world!"        },        {            "loc": "TEXT_HI",            "text": "Hi!"        }    ]}

…to the .resx format as in below:

<?xml version="1.0" encoding="utf-8"?><root>    <!--     Microsoft ResX Schema     Version 2.0    The primary goals of this format is to allow a simple XML format     that is mostly human readable. The generation and parsing of the     various data types are done through the TypeConverter classes     associated with the data types.    Example:    ... ado.net/XML headers & schema ...    <resheader name="resmimetype">text/microsoft-resx</resheader>    <resheader name="version">2.0</resheader>    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">        <value>[base64 mime encoded serialized .NET Framework object]</value>    </data>    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>        <comment>This is a comment</comment>    </data>    There are any number of "resheader" rows that contain simple     name/value pairs.    Each data row contains a name, and value. The row also contains a     type or mimetype. Type corresponds to a .NET class that support     text/value conversion through the TypeConverter architecture.     Classes that don't support this are serialized and stored with the     mimetype set.    The mimetype is used for serialized objects, and tells the     ResXResourceReader how to depersist the object. This is currently not     extensible. For a given mimetype the value must be set accordingly:    Note - application/x-microsoft.net.object.binary.base64 is the format     that the ResXResourceWriter will generate, however the reader can     read any of the formats listed below.    mimetype: application/x-microsoft.net.object.binary.base64    value   : The object must be serialized with             : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter            : and then encoded with base64 encoding.    mimetype: application/x-microsoft.net.object.soap.base64    value   : The object must be serialized with             : System.Runtime.Serialization.Formatters.Soap.SoapFormatter            : and then encoded with base64 encoding.    mimetype: application/x-microsoft.net.object.bytearray.base64    value   : The object must be serialized into a byte array             : using a System.ComponentModel.TypeConverter            : and then encoded with base64 encoding.    -->    <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />    <xsd:element name="root" msdata:IsDataSet="true">        <xsd:complexType>        <xsd:choice maxOccurs="unbounded">            <xsd:element name="metadata">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" />                </xsd:sequence>                <xsd:attribute name="name" use="required" type="xsd:string" />                <xsd:attribute name="type" type="xsd:string" />                <xsd:attribute name="mimetype" type="xsd:string" />                <xsd:attribute ref="xml:space" />            </xsd:complexType>            </xsd:element>            <xsd:element name="assembly">            <xsd:complexType>                <xsd:attribute name="alias" type="xsd:string" />                <xsd:attribute name="name" type="xsd:string" />            </xsd:complexType>            </xsd:element>            <xsd:element name="data">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />                </xsd:sequence>                <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />                <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />                <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />                <xsd:attribute ref="xml:space" />            </xsd:complexType>            </xsd:element>            <xsd:element name="resheader">            <xsd:complexType>                <xsd:sequence>                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />                </xsd:sequence>                <xsd:attribute name="name" type="xsd:string" use="required" />            </xsd:complexType>            </xsd:element>        </xsd:choice>        </xsd:complexType>    </xsd:element>    </xsd:schema>    <resheader name="resmimetype">    <value>text/microsoft-resx</value>    </resheader>    <resheader name="version">    <value>2.0</value>    </resheader>    <resheader name="reader">    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>    </resheader>    <resheader name="writer">    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>    </resheader>      <data name="NKS_COMMON_ANYKEY" xml:space="preserve">    <value>Press any key to continue...</value>  </data>  <data name="NKS_KERNEL_NOAPMSIMULATION" xml:space="preserve">    <value>It&apos;s now safe to turn off your computer.</value>  </data>  <data name="NKS_KERNEL_ENVERROR" xml:space="preserve">    <value>Kernel environment error:</value>  </data>  <data name="NKS_KERNEL_FATALERROR" xml:space="preserve">    <value>Nitrocid KS has detected a problem and it has been shut down.</value>  </data>  <data name="NKS_KERNEL_STARTING_DEVMESSAGE" xml:space="preserve">    <value>You&apos;re running the development version of the kernel. While you can experience upcoming features which may exist in the final release, you may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_RCMESSAGE" xml:space="preserve">    <value>You&apos;re running the release candidate version of the kernel. While you can experience the final touches, you may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_UNSUPPORTED" xml:space="preserve">    <value>We recommend against running this version of the kernel, because it is unsupported. If you have downloaded this kernel from unknown sources, this message may appear. Please download from our official downloads page.</value>  </data>  <data name="NKS_KERNEL_STARTING_ALPHAMESSAGE" xml:space="preserve">    <value>You&apos;re running the alpha version of the kernel. You may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data>  <data name="NKS_KERNEL_STARTING_BETAMESSAGE" xml:space="preserve">    <value>You&apos;re running the beta version of the kernel. You may run into bugs, instabilities, or even data loss. We recommend using the stable version, if possible.</value>  </data></root>

Our recent experiments proved that the resources method was faster than the LocaleStation method when it comes to first startup times due to Windows Defender. We have removed this library from the list of supported libraries, and that all development of LocaleStation will stop.

The specification will remain maintained, and the Aptivi Development Toolkit (ADT) will provide tools that we’ve developed internally to make dealing with those files easier than before.

We are still working on the rollout of the .resx file for all libraries, and this may take multiple library releases, depending on the severity of the situation.

#C_ #csharp #dotnet #Language #libraries #Library #Localization #news #Tech #Technology #update

.NET Short Term Releases get 2 years of support!

Earlier, the short term releases for each .NET version would last only 1.5 years (18 months), which means that once an LTS gets released, you’ll have to upgrade to that LTS versions before your .NET version gets deprecated. Now, it seems that Microsoft have adjusted this support length for short term releases of the modern .NET framework, starting from .NET 9.0 released November 12th of the last year.

Microsoft has added six more months to the total support length for such releases, making them end with their LTS version that came before. For example, on November 10th, 2026, both .NET 8.0 and 9.0 will reach end of life.

Here’s the chart that demonstrates the new support timeline:

This is a welcome change, as you’ll now have six extra months to upgrade to the new LTS release by the time the current STS and LTS versions are still in support. You can learn more about this change here.

#Net #Net9 #Net90 #NetCore #C_ #dotnet #news #Tech #Technology #update

.NET Short Term Releases get 2 years of support!

Earlier, the short term releases for each .NET version would last only 1.5 years (18 months), which means that once an LTS gets released, you’ll have to upgrade to that LTS versions before your .NET version gets deprecated. Now, it seems that Microsoft have adjusted this support length for short term releases of the modern .NET framework, starting from .NET 9.0 released November 12th of the last year.

Microsoft has added six more months to the total support length for such releases, making them end with their LTS version that came before. For example, on November 10th, 2026, both .NET 8.0 and 9.0 will reach end of life.

Here’s the chart that demonstrates the new support timeline:

This is a welcome change, as you’ll now have six extra months to upgrade to the new LTS release by the time the current STS and LTS versions are still in support. You can learn more about this change here.

#Net #Net9 #Net90 #NetCore #C_ #dotnet #news #Tech #Technology #update

.NET Short Term Releases get 2 years of support!

Earlier, the short term releases for each .NET version would last only 1.5 years (18 months), which means that once an LTS gets released, you’ll have to upgrade to that LTS versions before your .NET version gets deprecated. Now, it seems that Microsoft have adjusted this support length for short term releases of the modern .NET framework, starting from .NET 9.0 released November 12th of the last year.

Microsoft has added six more months to the total support length for such releases, making them end with their LTS version that came before. For example, on November 10th, 2026, both .NET 8.0 and 9.0 will reach end of life.

Here’s the chart that demonstrates the new support timeline:

This is a welcome change, as you’ll now have six extra months to upgrade to the new LTS release by the time the current STS and LTS versions are still in support. You can learn more about this change here.

#Net #Net9 #Net90 #NetCore #C_ #dotnet #news #Tech #Technology #update

.NET Short Term Releases get 2 years of support!

Earlier, the short term releases for each .NET version would last only 1.5 years (18 months), which means that once an LTS gets released, you’ll have to upgrade to that LTS versions before your .NET version gets deprecated. Now, it seems that Microsoft have adjusted this support length for short term releases of the modern .NET framework, starting from .NET 9.0 released November 12th of the last year.

Microsoft has added six more months to the total support length for such releases, making them end with their LTS version that came before. For example, on November 10th, 2026, both .NET 8.0 and 9.0 will reach end of life.

Here’s the chart that demonstrates the new support timeline:

This is a welcome change, as you’ll now have six extra months to upgrade to the new LTS release by the time the current STS and LTS versions are still in support. You can learn more about this change here.

#Net #Net9 #Net90 #NetCore #C_ #dotnet #news #Tech #Technology #update

.NET Short Term Releases get 2 years of support!

Earlier, the short term releases for each .NET version would last only 1.5 years (18 months), which means that once an LTS gets released, you’ll have to upgrade to that LTS versions before your .NET version gets deprecated. Now, it seems that Microsoft have adjusted this support length for short term releases of the modern .NET framework, starting from .NET 9.0 released November 12th of the last year.

Microsoft has added six more months to the total support length for such releases, making them end with their LTS version that came before. For example, on November 10th, 2026, both .NET 8.0 and 9.0 will reach end of life.

Here’s the chart that demonstrates the new support timeline:

This is a welcome change, as you’ll now have six extra months to upgrade to the new LTS release by the time the current STS and LTS versions are still in support. You can learn more about this change here.

#Net #Net9 #Net90 #NetCore #C_ #dotnet #news #Tech #Technology #update

Avalonia gets ready for macOS Tahoe!

Avalonia is a very popular UI framework for .NET desktop applications that run on not only computers, but also phones and tablets. Avalonia is constantly improved to bring new features while ensuring that your Avalonia applications get enhanced performance across releases. macOS Tahoe brings the Liquid Glass design, along with new features for Macintosh users.

Now, Avalonia has just released a new version in the v11.x version series, and that is version 11.3.6. The following changes were made:

• Enhancements
  • macOS – Adjust macOS Tray/Menu icons scaling by @drasticactions in Adjust macOS Tray/Menu icons scaling #19628
• Fixes
  • Windows – Fix OS timer interval calculation in Windows dispatcher by @Swarley97 in fix os timer interval calculation in windows dispatcher #19597
  • Windows – Fix maximized window being able to resize by @emmauss in Win32 – Fix maximized window being able to resize #19620
  • macOS – Fix SkiaSharp 3 Metal interop signature by @MrJul in Fix SkiaSharp3 Metal interop signature #19598
  • iOS – Backport GRContext bugfix by @maxkatz6 in Backport GRContext bugfix from 12.0 branch #19615
  • X11 – Ignore empty preeditText when no composition was active before (Ignore empty preeditText when no composition was active before #19595) by @Gillibald in Ignore empty preeditText when no composition was active before (#19595) #19621
  • Headless – Fix headless FontManager leak by @maxkatz6 in Fix headless FontManager leak #19599
  • Text – Fix TextLine.GetTextBounds zero width run by @Gillibald in TextLine.GetTextBounds zero width run fixes #19602
  • Text – Fix TextLineImpl.GetTextBounds with trailing zero width by @Gillibald in Fixes TextLineImpl.GetTextBounds with trailing zero width #19616

Out of all the above changes made to the Avalonia framework, two of them stands out for macOS support, because the macOS tray/menu icons scaling has been improved, ensuring that your applications look more awesome than before. Also, the SkiaSharp3 Metal interoperability signature has been changed, and Avalonia has been adapted to the new signature.

Both of those changes have made Avalonia ready for macOS Tahoe, as teased in a release post on Mastodon.

https://dotnet.social/@avaloniaui/115195866218682967

We are extremely grateful for their hard work at Avalonia for supporting macOS Tahoe.

To update your applications to support macOS Tahoe, update all your Avalonia NuGet packages to version 11.3.6 using either the package manager in your Visual Studio installation or the project files.

#Net #Avalonia #AvaloniaUI #C_ #csharp #dotnet #macOS #macOS26 #macOS26Tahoe #macOSTahoe #news #Programming #Tech #Technology #UI #update

Avalonia gets ready for macOS Tahoe!

Avalonia is a very popular UI framework for .NET desktop applications that run on not only computers, but also phones and tablets. Avalonia is constantly improved to bring new features while ensuring that your Avalonia applications get enhanced performance across releases. macOS Tahoe brings the Liquid Glass design, along with new features for Macintosh users.

Now, Avalonia has just released a new version in the v11.x version series, and that is version 11.3.6. The following changes were made:

• Enhancements
  • macOS – Adjust macOS Tray/Menu icons scaling by @drasticactions in Adjust macOS Tray/Menu icons scaling #19628
• Fixes
  • Windows – Fix OS timer interval calculation in Windows dispatcher by @Swarley97 in fix os timer interval calculation in windows dispatcher #19597
  • Windows – Fix maximized window being able to resize by @emmauss in Win32 – Fix maximized window being able to resize #19620
  • macOS – Fix SkiaSharp 3 Metal interop signature by @MrJul in Fix SkiaSharp3 Metal interop signature #19598
  • iOS – Backport GRContext bugfix by @maxkatz6 in Backport GRContext bugfix from 12.0 branch #19615
  • X11 – Ignore empty preeditText when no composition was active before (Ignore empty preeditText when no composition was active before #19595) by @Gillibald in Ignore empty preeditText when no composition was active before (#19595) #19621
  • Headless – Fix headless FontManager leak by @maxkatz6 in Fix headless FontManager leak #19599
  • Text – Fix TextLine.GetTextBounds zero width run by @Gillibald in TextLine.GetTextBounds zero width run fixes #19602
  • Text – Fix TextLineImpl.GetTextBounds with trailing zero width by @Gillibald in Fixes TextLineImpl.GetTextBounds with trailing zero width #19616

Out of all the above changes made to the Avalonia framework, two of them stands out for macOS support, because the macOS tray/menu icons scaling has been improved, ensuring that your applications look more awesome than before. Also, the SkiaSharp3 Metal interoperability signature has been changed, and Avalonia has been adapted to the new signature.

Both of those changes have made Avalonia ready for macOS Tahoe, as teased in a release post on Mastodon.

https://dotnet.social/@avaloniaui/115195866218682967

We are extremely grateful for their hard work at Avalonia for supporting macOS Tahoe.

To update your applications to support macOS Tahoe, update all your Avalonia NuGet packages to version 11.3.6 using either the package manager in your Visual Studio installation or the project files.

#Net #Avalonia #AvaloniaUI #C_ #csharp #dotnet #macOS #macOS26 #macOS26Tahoe #macOSTahoe #news #Programming #Tech #Technology #UI #update

Avalonia gets ready for macOS Tahoe!

Avalonia is a very popular UI framework for .NET desktop applications that run on not only computers, but also phones and tablets. Avalonia is constantly improved to bring new features while ensuring that your Avalonia applications get enhanced performance across releases. macOS Tahoe brings the Liquid Glass design, along with new features for Macintosh users.

Now, Avalonia has just released a new version in the v11.x version series, and that is version 11.3.6. The following changes were made:

• Enhancements
  • macOS – Adjust macOS Tray/Menu icons scaling by @drasticactions in Adjust macOS Tray/Menu icons scaling #19628
• Fixes
  • Windows – Fix OS timer interval calculation in Windows dispatcher by @Swarley97 in fix os timer interval calculation in windows dispatcher #19597
  • Windows – Fix maximized window being able to resize by @emmauss in Win32 – Fix maximized window being able to resize #19620
  • macOS – Fix SkiaSharp 3 Metal interop signature by @MrJul in Fix SkiaSharp3 Metal interop signature #19598
  • iOS – Backport GRContext bugfix by @maxkatz6 in Backport GRContext bugfix from 12.0 branch #19615
  • X11 – Ignore empty preeditText when no composition was active before (Ignore empty preeditText when no composition was active before #19595) by @Gillibald in Ignore empty preeditText when no composition was active before (#19595) #19621
  • Headless – Fix headless FontManager leak by @maxkatz6 in Fix headless FontManager leak #19599
  • Text – Fix TextLine.GetTextBounds zero width run by @Gillibald in TextLine.GetTextBounds zero width run fixes #19602
  • Text – Fix TextLineImpl.GetTextBounds with trailing zero width by @Gillibald in Fixes TextLineImpl.GetTextBounds with trailing zero width #19616

Out of all the above changes made to the Avalonia framework, two of them stands out for macOS support, because the macOS tray/menu icons scaling has been improved, ensuring that your applications look more awesome than before. Also, the SkiaSharp3 Metal interoperability signature has been changed, and Avalonia has been adapted to the new signature.

Both of those changes have made Avalonia ready for macOS Tahoe, as teased in a release post on Mastodon.

https://dotnet.social/@avaloniaui/115195866218682967

We are extremely grateful for their hard work at Avalonia for supporting macOS Tahoe.

To update your applications to support macOS Tahoe, update all your Avalonia NuGet packages to version 11.3.6 using either the package manager in your Visual Studio installation or the project files.

#Net #Avalonia #AvaloniaUI #C_ #csharp #dotnet #macOS #macOS26 #macOS26Tahoe #macOSTahoe #news #Programming #Tech #Technology #UI #update

Avalonia gets ready for macOS Tahoe!

Avalonia is a very popular UI framework for .NET desktop applications that run on not only computers, but also phones and tablets. Avalonia is constantly improved to bring new features while ensuring that your Avalonia applications get enhanced performance across releases. macOS Tahoe brings the Liquid Glass design, along with new features for Macintosh users.

Now, Avalonia has just released a new version in the v11.x version series, and that is version 11.3.6. The following changes were made:

• Enhancements
  • macOS – Adjust macOS Tray/Menu icons scaling by @drasticactions in Adjust macOS Tray/Menu icons scaling #19628
• Fixes
  • Windows – Fix OS timer interval calculation in Windows dispatcher by @Swarley97 in fix os timer interval calculation in windows dispatcher #19597
  • Windows – Fix maximized window being able to resize by @emmauss in Win32 – Fix maximized window being able to resize #19620
  • macOS – Fix SkiaSharp 3 Metal interop signature by @MrJul in Fix SkiaSharp3 Metal interop signature #19598
  • iOS – Backport GRContext bugfix by @maxkatz6 in Backport GRContext bugfix from 12.0 branch #19615
  • X11 – Ignore empty preeditText when no composition was active before (Ignore empty preeditText when no composition was active before #19595) by @Gillibald in Ignore empty preeditText when no composition was active before (#19595) #19621
  • Headless – Fix headless FontManager leak by @maxkatz6 in Fix headless FontManager leak #19599
  • Text – Fix TextLine.GetTextBounds zero width run by @Gillibald in TextLine.GetTextBounds zero width run fixes #19602
  • Text – Fix TextLineImpl.GetTextBounds with trailing zero width by @Gillibald in Fixes TextLineImpl.GetTextBounds with trailing zero width #19616

Out of all the above changes made to the Avalonia framework, two of them stands out for macOS support, because the macOS tray/menu icons scaling has been improved, ensuring that your applications look more awesome than before. Also, the SkiaSharp3 Metal interoperability signature has been changed, and Avalonia has been adapted to the new signature.

Both of those changes have made Avalonia ready for macOS Tahoe, as teased in a release post on Mastodon.

https://dotnet.social/@avaloniaui/115195866218682967

We are extremely grateful for their hard work at Avalonia for supporting macOS Tahoe.

To update your applications to support macOS Tahoe, update all your Avalonia NuGet packages to version 11.3.6 using either the package manager in your Visual Studio installation or the project files.

#Net #Avalonia #AvaloniaUI #C_ #csharp #dotnet #macOS #macOS26 #macOS26Tahoe #macOSTahoe #news #Programming #Tech #Technology #UI #update

Avalonia gets ready for macOS Tahoe!

Avalonia is a very popular UI framework for .NET desktop applications that run on not only computers, but also phones and tablets. Avalonia is constantly improved to bring new features while ensuring that your Avalonia applications get enhanced performance across releases. macOS Tahoe brings the Liquid Glass design, along with new features for Macintosh users.

Now, Avalonia has just released a new version in the v11.x version series, and that is version 11.3.6. The following changes were made:

• Enhancements
  • macOS – Adjust macOS Tray/Menu icons scaling by @drasticactions in Adjust macOS Tray/Menu icons scaling #19628
• Fixes
  • Windows – Fix OS timer interval calculation in Windows dispatcher by @Swarley97 in fix os timer interval calculation in windows dispatcher #19597
  • Windows – Fix maximized window being able to resize by @emmauss in Win32 – Fix maximized window being able to resize #19620
  • macOS – Fix SkiaSharp 3 Metal interop signature by @MrJul in Fix SkiaSharp3 Metal interop signature #19598
  • iOS – Backport GRContext bugfix by @maxkatz6 in Backport GRContext bugfix from 12.0 branch #19615
  • X11 – Ignore empty preeditText when no composition was active before (Ignore empty preeditText when no composition was active before #19595) by @Gillibald in Ignore empty preeditText when no composition was active before (#19595) #19621
  • Headless – Fix headless FontManager leak by @maxkatz6 in Fix headless FontManager leak #19599
  • Text – Fix TextLine.GetTextBounds zero width run by @Gillibald in TextLine.GetTextBounds zero width run fixes #19602
  • Text – Fix TextLineImpl.GetTextBounds with trailing zero width by @Gillibald in Fixes TextLineImpl.GetTextBounds with trailing zero width #19616

Out of all the above changes made to the Avalonia framework, two of them stands out for macOS support, because the macOS tray/menu icons scaling has been improved, ensuring that your applications look more awesome than before. Also, the SkiaSharp3 Metal interoperability signature has been changed, and Avalonia has been adapted to the new signature.

Both of those changes have made Avalonia ready for macOS Tahoe, as teased in a release post on Mastodon.

https://dotnet.social/@avaloniaui/115195866218682967

We are extremely grateful for their hard work at Avalonia for supporting macOS Tahoe.

To update your applications to support macOS Tahoe, update all your Avalonia NuGet packages to version 11.3.6 using either the package manager in your Visual Studio installation or the project files.

#Net #Avalonia #AvaloniaUI #C_ #csharp #dotnet #macOS #macOS26 #macOS26Tahoe #macOSTahoe #news #Programming #Tech #Technology #UI #update

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 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 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 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 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

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

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

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

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

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

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

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

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

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

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

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

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

Our NuGet total downloads reached 2M!

We have finally reached 2 million downloads across all our NuGet packages, which consist of both the current and the past libraries that have been downloaded over the lifetime of our NuGet feed existence that started on August 2019. Thanks to everyone who have tried out our packages and used them in their applications!

This is a minor milestone, but we are aiming for major ones, such as 5 million downloads across all packages. To celebrate this milestone, we’re introducing brand new versions of libraries. This is to add new features and to improve existing ones.

Nitrocid 0.1.3 is going to have a major arrangement overhaul when it comes to the API, so we’re going to mark this by increasing the API version to v4.0 from v3.1 as it’s a huge breaking change. This will make sure that the Nitrocid application acts like a “launcher” for the core Nitrocid kernel, which, in turn, depends on the base kernel library. This is vaguely similar to how v0.0.20 was developed.

Textify will be updated to improve the RTL reverse performance by getting rid of the libicu library in favor of the more efficient method after this experiment proves successful. As always, we are aiming to change how we make experiments to make sure that they don’t hinder the final production code, but, sometimes, we’d release a version that includes such experiments to gather feedback.

We are going to try reducing the distribution size of Terminaux starting from v7.0, and Beta 3 will include this improvement to ensure that we reduce the download size, especially for future Nitrocid versions. We have already updated Terminaux 6.1.x to include this improvement, and docs have been already updated to reflect this change.

Finally, we are going to introduce some subtle changes to the CI system across all projects, as well as some more build system improvements that we’ve promised, to improve build times and to increase reliability. This applies to developers only.

Enjoy!

#Net #Net6 #Net60 #NET7 #NET70 #Net8 #Net80 #Net9 #Net90 #NetCore #NetCore31 #NetFramework #NetStandard #C_ #csharp #NuGet #NuGetPackageManager #NuGetOrg #Package #PackageManager #Packages #Packaging #VBNET

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 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 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 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