-
Notifications
You must be signed in to change notification settings - Fork 228
Update to supported dotnet #1196
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
Draft
GrahamTheCoder
wants to merge
41
commits into
master
Choose a base branch
from
update-to-supported-dotnet
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changed the target framework in ConsoleApp4.vbproj from netcoreapp3.1 to net10.0 to upgrade the project to a newer .NET version.
…t since they will likely screw up for name clashes anyway
…ately runnable file I made to test the approach
…for this upgrade is installed on the machine and if not, help to get it installed'
Converted CSharpConsoleApp.csproj from the legacy .NET Framework project format to the modern SDK-style format. Updated the target framework to net10.0, removed redundant property groups and references, and simplified the ProjectReference element. This streamlines the project file and aligns it with current .NET best practices.
Eliminated references to microsoft.visualbasic, System.Data.DataSetExtensions, and Microsoft.CSharp from the CSharpConsoleApp.csproj file, streamlining project dependencies. No other changes were made.
less important to have winforms in frontend since it only really works with multiple files
…t enforces having precisely one match
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will remove direct attempts to support running dot net framework apps. It may still partially work in some cases, but using an older version of the converter would be wisest. It also removes the web app's api and cuts it down to a host of static files with the function always providing the api.
Why
It's very hard to find a balance between old and new, particularly around dot net framework and msbuild versions.
Instead, we'll target the latest LTS version of dot net and use old builds to satisfy people who turn up with ancient projects that need converting, or advise them to upgrade to the latest dot net first.
Solution
Still need to look into a couple of test failures but wanted to check if this works on CI system.