Skip to content

Conversation

@GrahamTheCoder
Copy link
Member

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.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants