mention fsproj files as an example of other dotnet reference files #44031
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
add mention to the fact that cross language project reference can work within valid .NET project files, for example F#
dotnet-policy-service
bot
added
the
community-contribution
gewarren
reviewed
Dec 19, 2024
gewarren
approved these changes
Dec 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
in .NET ecosystem other supported project formats exist, for example
.vbprojand.fsprojand users are many times confused or not aware of this capability, so it should be made clear is perfectly legit to have solutions with multiple languages. One possible usecase is having test solution in one language, for example .fsproj, referencing an implementation solution in another language, for example .csproj, some languages might have benefits in specific areas or it might be an easier way / lower-friction to introduce a new language to a team, just have it in a small assembly, be it tests or a small module.Summary
Add a mention to the fact that cross language project reference can work within valid .NET project files, for example F#
Fixes #Issue_Number (if available)
Internal previews