Search Issue Tracker
Fixed
Fixed in 2.0.18
Votes
0
Found in [Package]
2.0.8
Issue ID
VS-33
Regression
Yes
DLL which is disabled on the current platform is being referenced due to its path being first in the compiled assembly
Steps to reproduce:
1. Open the project attached by the user
2. Open AssetList.cs (Assets/Plugins/Weaver/Asset Lists/AssetList.cs)
Expected results: No errors are produced since the assembly used in Editor is the one specified to use in Editor
Actual results: Errors due to using assembly for runtime
Reproducible with: Visual Studio Editor 2.0.8, 2.0.9, 2.0.11 (2019.4.28f1, 2020.3.13f1, 2021.1.14f1, 2021.2.0b3)
Not reproducible with: Visual Studio Editor 1.0.2, 1.0.11 (2019.4.28f1), 2018.4.36f1
Workaround:
- Open Weaver.csproj from the projects directory in notepad or any other text editor. Search for "Weaver.Lite.dll". Once you find the ItemGroup with paths to Weaver plugin components, exchange the Runtime and Editor dll paths (so the Editor dll path would be first).
Notes:
- Runtime assembly is marked to be excluded in Editor, another assembly with the same name is marked to be used only in Editor
- In 2018.4 the ItemGroup mentioned in the workaround is not in the Weaver.csproj file, so likely that's the reason is not reproducible
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Add comment