1
I only have one .NET module left that I maintain in the app store. The framework version actually loaded just fine in 2025,
but I went ahead and used the conversion tool and ported it to Core.
I never tried to step into to it with the debugger though. I remember that .NET would load specific debugger depending on the .config settings.. so it may run, just not debug
I’m going to rewrite it in C++, I didn’t take the news of Microsoft depreciating framework well
Maybe that’s a Framework DLL that doesn’t like Core?
If it’s not already installed, Microsoft .NET Framework 4.8, will also be installed with AutoCAD 2025 including Specialized Toolsets. Microsoft .NET Framework 4.8 also requires a Windows version that’s currently supported by Microsoft.
If you are targeting AutoCAD 2025 or AutoCAD 2025-based programs, you should use:
Microsoft Visual Studio 2022 version 17.8.0
Microsoft .NET 8.0
Note: Applications compiled with Microsoft Visual Studio 2019 version 16.0 or later should load into AutoCAD 2025 or AutoCAD 2025-based programs without any problems.
"Unable to load DLL 'mscorwks.dll' or one of its dependencies: The specified module could not be found. (0x8007007E)"