For years, Ranorex Studio has been built on .NET Framework. Although Microsoft continues to support the framework as a Windows component, it is no longer the foundation for .NET development. That has created a growing mismatch for enterprise QA teams working with current .NET tools, libraries, and development standards.

Ranorex Studio 13.0.0 resolves that mismatch by migrating to .NET 10, Microsoft’s current Long-Term Support release. The IDE, test runner, plugins, UI controls, and built-in tools now run on the platform. More than a compatibility update, this release rebuilds the technical foundation of Ranorex Studio for the applications, engineering environments, and capabilities ahead.

Why this matters

For enterprise QA teams, the .NET 10 edition removes Ranorex Studio’s longstanding dependency on .NET Framework. It aligns the platform with Microsoft’s modern development platform, reduces friction during technical and procurement reviews, and resolves known issues traced to limitations in the previous architecture.

This is also a future-ready platform, not a maintenance release. .NET 10 is supported by Microsoft through November 2028, so you get a stable, modern runtime to build on. Upcoming Ranorex capabilities, including new AI tooling, integrations, and expanded framework support, will expand on what this release delivers.

What Ranorex Studio 13.0.0 unlocks for your team

Moving Ranorex Studio to .NET 10 does more than update its underlying architecture. It improves the product’s performance today while removing technical constraints that could otherwise limit its continued development.

• Faster test execution. Improvements to JIT compilation and garbage collection in .NET 10 reduce runtime overhead and help test suites execute more efficiently.
• Faster startup and project loading. Ranorex Studio opens faster and loads projects more quickly, reducing the time between launching the product and beginning work.
• Access to modern NuGet package feeds. Ranorex Studio now supports the NuGet v3 protocol so you can use compatible package feeds hosted on GitLab, Azure Artifacts, and other platforms that require v3.
• Better use of hardware. Improved resource utilization helps Ranorex Studio make greater use of current multicore systems, including high-core-count machines often used in CI environments.
• Alignment with enterprise standards. Moving away from the maintenance-focused .NET Framework means a developed platform that is easier to support during architectural, security, and procurement reviews.
• A foundation for innovation. Future Ranorex capabilities can now be developed without being constrained by the legacy architecture.

What the migration means for existing projects

Ranorex Studio 13.0.0 is available in two editions: a .NET 10 edition (beta) and a .NET Framework 4.8 edition. Both offer the same automation capabilities and support the same technologies. The .NET 10 edition is the path forward, while the .NET Framework 4.8 edition is available for teams with specific compatibility requirements.

Existing automation projects do not need to migrate immediately. Current test suites and recording modules remain supported, while teams with custom code can retain their .NET Framework 4.8 target or move to .NET 10 when ready.

• In the .NET 10 edition, Ranorex Studio’s IDE, test runner, plugins, UI controls, and built-in tools run natively on .NET 10.
• The Ranorex API supports both .NET Framework 4.8 and .NET 10, allowing custom automation projects and API integrations to remain on their current target or migrate when ready.
• Ranorex DLLs targeting .NET 10 are included with the release, alongside companion .NET Framework 4.8 DLLs for projects that continue to use the older framework.

What to check before upgrading

Most existing test suites should carry over without significant changes. Teams using custom code, third-party dependencies, or API integrations should review the following before upgrading:

• Custom code: Review C# or VB.NET modules for APIs available only in .NET Framework before moving projects to .NET 10.
• Third-party dependencies: Check that libraries, packages, and extensions support your chosen target. In the .NET 10 edition, previously bundled packages such as Newtonsoft.Json and NLog must be added directly to your project if your custom code depends on them.
• Build environments: Check whether build scripts and CI runners need the .NET 10 runtime or updated Ranorex components.
• API integrations: Confirm whether custom automation frameworks and integrations will remain on .NET Framework 4.8 or move to .NET 10.
• SQL Server data sources: The .NET 10 edition uses a SQL client that enables encryption by default. Review connection settings and certificate requirements in the migration guide before upgrading.
• SQL Server Compact data sources: The SQL CE connector is unavailable in the .NET 10 edition. Teams that depend on it should retain the .NET Framework 4.8 edition or migrate to a supported data source before switching.

Ranorex Studio 13.0.0 was tested in real-world enterprise environments through a beta program ahead of release. For detailed compatibility requirements and upgrade instructions, consult the migration guide.

Get started

Ranorex Studio 13.0.0 is available now. Current users can upgrade through their normal update channel, and new users can try it for free.

Before upgrading, read the full migration guide for system requirements, compatibility guidance, and step-by-step instructions. Since the .NET 10 edition is a beta, we’d love to hear how it works in your environment. If you have questions, feedback, or run into an issue, contact the Ranorex support team for help planning or completing your migration.

FAQs

Do I need to update my existing test suites?

Most teams will not need to make changes. Existing test suites, recording modules, and code modules are expected to continue running as is, since the migration happens at the product level, not in your project files.

What if my custom code or API integration depends on .NET Framework?

You’re covered either way. The Ranorex API supports both .NET Framework 4.8+ and .NET 10+, and companion 4.8 DLLs ship alongside the .NET 10 build for projects that need to stay on the older runtime.

Will this change how my tests run in CI/CD?

No changes are required, other than ensuring your runners have the appropriate .NET version for the target you choose.

What happens to my object repository and RanoreXPath expressions?

They carry over unchanged. Object recognition, the Ranorex Repository, and your locator strategy are not affected by the runtime migration.

Is this a subscription-only update?

No. Both subscription and perpetual license holders receive this migration as part of the update.

How was this validated before release?

This release went through an enterprise beta program to validate the migration in real-world environments before it shipped broadly.

Who can I contact if I run into issues?

Reach out to our support team. They can walk your team through the migration and troubleshoot any compatibility questions.