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