Assets compiler produce errors if nuget cache directory was changed
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
Version: 4.0.1.1401
Platform(s): Windows
Describe the bug
Changed Nuget project-level cache directory causes assets compiler error.
To Reproduce
Steps to reproduce the behavior:
- Create new Stride project from template
- Change Nuget cache directory by overriding MSBUildProjectExtensionsPath variable in Directory.Build.props.
- Error has been occurred during build process.
Expected behavior
I want to build Stride project with changed Nuget cache directory.
Additional context
See example project: WrongNugetHandlingExample.zip
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 build from the linked WrongNugetHandlingExample.zip, using a Stride project created from the template and the MSBuildProjectExtensionsPath override in Directory.Build.props. Start with the assets compiler error and trace how the changed NuGet project-level cache directory is handled during the build. Done means the project builds successfully with the overridden cache directory.
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
- 30/100