Warning
This is a preliminary and work-in-progress version of the official document.
Warning
We recommend taking a full backup of your project(s), including your existing Eyeshot 2024 NuGet packages.
Single project update
To migrate a single Eyeshot 2024-based project to Eyeshot 2025, follow the steps below:
- Ensure that your existing Eyeshot 2024 Visual Studio project compiles and run
- Close any text editor with your source code loaded
- Open the solution containing the given project in VS
- Right click on the project you want to upgrade in the Solution Explorer panel
- Select Eyeshot 2025>Upgrade... and perform the upgrade operations
- Try to compile your converted project
- In case of failure:
- Search for the "TODO devDept" text in your entire Visual Studio solution
- Check the Project Converter log file for errors
- Check the Breaking Changes in Eyeshot 2025 article
Multiple project updates
To migrate many Eyeshot 2024-based projects in batch to Eyeshot 2025, follow the steps below:
- Ensure that your existing Eyeshot 2024 Visual Studio project compiles and run
- Close all Visual Studio instances
- Close any text editor with your source code loaded
- Run the Eyeshot 2025 Project Converter tool
- Try to compile your converted project
- In case of failure:
- Search for the "TODO devDept" text in your entire Visual Studio solution
- Check the Project Converter log file for errors
- Check the Breaking Changes in Eyeshot 2025 article
Notes
With Eyeshot 2025 tools, the migration will remove old Eyeshot 2024 NuGet packages installation, in order to try and install the new Eyeshot 2025 NuGet packages; with SDK-style projects this operation is less error prone than with legacy style projects: update your project to a SDK-style project or manually add NuGet packages after the conversion if needed.
If you get the following error after the conversion of the project:
please install the NuGet package via the VS extension menu or manually install it as shown in this article or manually edit the project file to use the proper version of the NuGet packages you have installed locally.
In case of migration from older versions, you may want to check this article.
Comments
Please sign in to leave a comment.