# 6.13.0 08 Apr 2026 *** ### Upgraded to .NET 10 Linx 6 now runs on .NET 10, bringing improved performance, reduced memory usage, and access to the latest runtime features. All plugins targeting .NET 10 are fully supported. *** ### Replaced JSON.NET with System.Text.Json for Type Import The Type Import feature now uses System.Text.Json instead of Newtonsoft's JSON.NET for parsing JSON schemas. This improves consistency with the rest of the platform and removes the dependency on the third-party JSON library for this feature. *** ### Fixed Designer crash when renaming a folder Renaming a folder in the Designer caused the application to crash in a very specific configuration. Folders can now be renamed without issue. *** ### Fixed context menus not opening with keyboard shortcuts Context menus for items in the Solution Explorer and Test Explorer could not be opened using keyboard shortcuts. Keyboard-triggered context menus now work correctly. *** ### Fixed Test Explorer showing Duration for tests that have not run The Test Explorer displayed a "Duration" label in the outcome panel for tests that had not been executed yet. The duration text is now only shown after a test has completed. *** ### Fixed installer deleting files during update Updating from Linx Designer or Server 6.10.1 or earlier could result in files being deleted during the installation process. The installer now correctly preserves existing files during updates. *** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.linx.software/releasenotes/linx-platforms/6.13.0.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.