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
Hi there!
Is the Project Converter tool for 2025 currently supposed to work? I tried using it on our fairly big solution using 2024 nightly build 629 and it seems to me that the tool gets stuck at whichever first .csproj file it is supposed to update. CPU usage below 0.5%, memory consumption remains constant, so it seems it's just stuck.
If I restart the tool and uncheck the project it was stuck on, it's getting stuck on the next one.
Anything I can try?
Best regards
Matthias Rolf
Hello Matthias,
I tested the Project Converter 2025 with the Eyeshot 2024 sample projects, and it worked as expected without any issues.
If you are experiencing problems specifically with your project, I recommend opening a ticket with our support team so we can investigate further.
Thank you.
Hi Marcello,
I let the Project Converter run just to give it a try. What I mistook as "stuck" was the converter just taking forever to handle every csproj file. For our solution, it took around 4 hours to complete. According to the log file, all selected projects were successfully converted.
However, none of the Eyeshot dependencies were changed correctly. On top of that, the converter also added comment line like "Curve offset methods don't need the tolerance parameter anymore" seemingly above every single line that contains the word "Offset" in some way. Same goes for the comment line "IShader.Create() method has been removed" and probably others I missed, resulting in a log file of just shy of 5000 lines, making it pretty much useless.
I think there is definitely room for improvement in the converter tool.
Best regards
Hi Matthias,
Thanks for your feedback and for sharing your experience with the Project Converter.
Could you confirm if your project is a legacy project? If so, as stated on the Project Converter’s initial screen, dependencies are not automatically updated by the tool and must be manually adjusted after the conversion.
Regarding the added comments, the Project Converter operates based on a find-and-replace mechanism and does not have full contextual awareness of the project’s structure. I understand that some comments may appear repetitive, but unfortunately, we cannot anticipate the size or complexity of our customers' projects in advance.
To reduce the number of comments, you have two options:
We are always open to suggestions for improving the tool. If you have any specific recommendations, feel free to open a support ticket, and we’ll be happy to consider them.
Best regards,
Marcello
Hello Matthias,
I have been upgrading my solution from eyeshot 22 to eyeshot 24 but i'm getting an error at this below while runtime
devDept.Eyeshot.Control.BackgroundSettings backgroundSettings1 = new devDept.Eyeshot.Control.BackgroundSettings(devDept.Graphics.backgroundStyleType.Solid, System.Drawing.Color.DeepSkyBlue, System.Drawing.Color.DodgerBlue, System.Drawing.Color.WhiteSmoke, 0.75D, null, devDept.Eyeshot.colorThemeType.Auto, 0.33D);
And below is the screenshot of the error im getting
1.
2.
Please let me know if i'm missing any key step of upgradation.
Hi Vaibhav,
I'm sorry, but I don't work for devDept. Also, this article here is about migrating from Eyeshot 2024 to 2025. But from what I can tell in your screenshots, you seem to be missing some referenced assemblies in your output folder.
For any further assistance, please contact devDept.
Best regards
Please sign in to leave a comment.