stride3d/stride

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

Open

#895 opened on Oct 28, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C# (6,001 stars) (886 forks)batch import
area-Buildarea-GameStudiobuggood first issuepriority-highwork-estimate-M

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

Tech stack
csharp
Domain
build system
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of .NET framework installationFamiliarity with Stride build process
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the build log at pastebin link (https://pastebin.com/VPJNh0DP). Check how Stride detects .NET Framework versions in its build system, likely in the game studio or build scripts. Compare with Visual Studio's detection. Look for any configuration files or environment variables that might cause mismatch. Consider asking maintainers about the expected .NET Framework versions required.