Migration to 4.0

迁移到 4.0

Migration to 4.0

本页适用于从 3.x 升级到 AuroraScript.JIT 4.0.0 的宿主和工具链。

This page applies to hosts and tooling moving from 3.x to AuroraScript.JIT 4.0.0.

更新包与工具

Updating Packages and Tools

将 NuGet 包和全局 MCP 工具更新到 4.0.0，然后重新构建宿主项目和脚本。

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

README 只保留项目介绍、安装和最小示例。语言教程、完整 API、基准、MCP、Language Server、Visual Studio 和排障资料已迁移到本 Wiki。项目内 documents/ 仍是随包提供给工具和 MCP 的机器可读语言资料。

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. 重新还原并构建宿主项目。
2. 运行现有脚本测试，重点检查模块解析、宿主全局、CLR 注册和热更新流程。
3. 如使用自定义 Resolver，确认相对路径仍以导入者来源为基准。
4. 如使用 Persistence、VSIX 或调试，验证目标 .NET/Visual Studio 环境满足要求。
5. 对热点规则运行 benchmark，避免将历史机器上的绝对耗时当作新版本结论。

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

升级前后请以本 Wiki 的对象页面、发布包的 schema 和测试结果为准。对任何依赖未在 API 参考中列出的运行时实现类型的代码，应先用目标版本重新验证；这些类型不构成长期兼容承诺。

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.