Migration to 4.0

Migration to 4.0

Upgrade AuroraScript.JIT hosts and tooling from 3.x to 4.0.0 and validate compatibility.

Applies to 4.0.0.

Home · Getting Started

On this page

• Updating Packages and Tools
• Documentation Entry Changes
• Upgrade Validation
• Finding Change Details
• Next steps

Updating Packages and Tools

Update the NuGet package and global MCP tool to 4.0.0, then rebuild the host project and scripts.

dotnet add package AuroraScript.JIT --version 4.0.0
dotnet tool update --global AuroraScript.Mcp --version 4.0.0

Documentation Entry Changes

The README now retains only project introduction, installation, and a minimal example. Tutorials, complete APIs, benchmarks, MCP, Language Server, Visual Studio, and troubleshooting material live in this Wiki. The in-repository documents/ folder remains the packaged machine-readable language material for tooling and MCP.

Upgrade Validation

1. Restore and rebuild the host project.
2. Run existing script tests, especially module resolution, host globals, CLR registration, and hot-patch flows.
3. If using a custom resolver, confirm relative paths are still based on the importing source.
4. If using Persistence, the VSIX, or debugging, verify the target .NET/Visual Studio environment meets the requirements.
5. Benchmark hot rules; do not treat historical absolute timings from another machine as a conclusion for the new version.

Finding Change Details

Before and after upgrading, use this Wiki's object pages, the package schemas, and test results as the source of truth. Revalidate any code that depends on runtime implementation types not listed in the API reference; those types are not a long-term compatibility promise.

Next steps

• Getting Started to verify a minimal 4.0 host.
• Troubleshooting and Security for upgrade failures.