-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion - msbuild and .net 6 #3
Comments
I've been thinking about doing that for some time now but was trying to keep compliant with the existing build methodology. I'm nearly done with the port of the VSIX Graph Engine Add-in to VS 2022. Getting rid of the CMake is going to take a bit of work as the C++ code is dependent on it; also need to make sure the Linux and macOS build work as well. I will take a serious look at making this change in two weeks; I'm busy with getting a beta build ready to release. I do get a clean build now with this build configuration with what is checked in now; I will try on a clean machine there this evening to see what is broken now. |
I've updated, fixed the current build pipeline, and added support for Azure CI/CD. It might be a while before I get to the pure MSBuild method. |
New build works for .NET 7 and Azure CI/CD |
Cool. I will try. Thanks. |
A huge update is coming! Many new capabilities with new sophisticated samples demonstrate advanced and hidden features of the Graph Engine. |
that sounds very interesting :) |
I've not pushed the .NET 7 updates just yet. |
Maybe it would make sense just to get rid of legacy stuff and cmake and move to msbuild and .net 6 (which would work on both windows and linux). That would improve maintainability quite a bit, as on every new VS version and framework version - there are issues to be fixed.
The text was updated successfully, but these errors were encountered: