Feature: Add Support for F# and VB Project Types #1821
Merged
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.
PR Details
This PR adds support for additional project types:
.fsproj
and.vbproj
, enabling F# and Visual Basic coding in Stride's code-only approach. Further work may be required to integrate F# and Visual Basic into the Stride Game Studio, which I will leave to more experienced contributors.Description
This PR serves as a follow-up to the incomplete #1078. I've implemented the changes necessary for a "code-only" approach, as I'm currently not familiar with Stride Game Studio.
To accommodate these changes, I've introduced a
SupportedProgrammingLanguage
record and aSupportedProgrammingLanguages
class. I opted for these names asSupportedLanguage
is already used within the codebase for a different purpose.I'm open to feedback on the naming conventions and the overall implementation. The core change involves extending the existing logic to account for
.fsproj
and.vbproj
in addition to.csproj
.Related Issue
#1078
Typical error when using other project types
Motivation and Context
Allowing to use other .NET languages as they should be working.
Types of changes
Checklist