FSharp projects are removed from the solution when building from the engine
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Release Type: Official Release/GitHub (please choose appropriate option)
Version: 4.2
Platform(s): Windows
Describe the bug
Running build from the editor is removing my fsharp projects from the .net solution.
To Reproduce
Steps to reproduce the behavior:
- Create a new stride project.
- Add an fsharp project to the solution in visual studio
- Run build from the game editor.
- Return to visual studio. The fsharp project is unloaded.
Expected behavior
Leave fsharp and vb.net projects alone.
Screenshots
If applicable, add screenshots to help explain your problem (use GitHub drag & drop)
Log and callstacks
If any, please attach here any log or callstack (preferably in a .txt file using GitHub drag and drop)
Additional context
I'm not expecting extensive fsharp support anytime soon, but fsharp is a part of .net and I don't see why stride should be outright hostile to using it in the codebase.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by adding an F# project to a Stride solution in Visual Studio, then running a build from the game editor. Compare the solution before and after the build; done means the F# and VB.NET projects remain loaded and unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp, visualbasic
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100