stride3d / stride3d/stride

Stride can't find .Net Framework even when Visual Studio can and use it successfully

Open
#895 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-Build area-GameStudio bug good first issue priority-high work-estimate-M
Dominant language
C#
Stars
7.8k
Forks
1.2k
Avg merge
2d 17h
Merged PRs (30d)
49

Description

Release Type: Official Release

Version: 4.0.0.1-beta04-1265

Platform(s): Windows

Describe the bug
You can't test your proyects in the Stride game studio at all, you can't even try the proyects than come with the program already done, however you can compile the game in Visual Studio (2019) with no issue whatsoever.

If you choose make a new proyect with Netcore 3.1 doesn't acknowledge it and instead try try to build it with the problematic .Net Framework.

To Reproduce
Steps to reproduce the behavior:

  1. Build any proyect (even one of the examples) on game studio.

Expected behavior
Doesn't Build because can't find the associated .Net Framework

Screenshots
Non Aplicable

Log and callstacks
https://pastebin.com/VPJNh0DP

Additional context

  • Already try reinstalling everything several times, Stride, VS, Stride plugin to work with VS, the .Net Frameworks (4.6.1 and 4.7.2, both of them, Install, reinstall and also repair) and install extra Netcore versions and nothing work.

  • It maybie matter than, when installing a .Net Framework and installing a Netcore version both go to different folders in different drives, i'm just mentioning it, it may matter, it may not.

  • It's happening from some time already, i think it start when i upgrade the Stride version, that being said i already install it and reinstall it several times so maybie the problem is other thing.

  • Any question can be done to the mail asociated to this account or through discord to Obsdark#8764 please feel free to ask wherever you need to clarify the bug and hopefully fix it, i gladly answer the questions whenever i can.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked pastebin log and reproduce the failure by building an example project in Stride Game Studio on Windows. Compare that behavior with the successful Visual Studio 2019 build and the attempted .NET Core 3.1 project build; done means the examples and new projects build successfully in Game Studio.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.