Search Issue Tracker

Fixed in 1.2.5

Votes

0

Found in [Package]

2019.4

2020.3

2021.2

2021.2.10f1

2022.1

2022.2

Issue ID

1401979

Regression

No

Package path of Roslyn Analyzers is incorrect when using Visual Studio Code as an External Script Editor

Package: VS Code

-

Steps to reproduce:
1. Extract user attached archive "analyzers-package.zip"
2. Open user attached project in "a-project.zip"
3. In the Toolbar select Windows > Package Manager
4. In the Package Manager window click "+" > Add package from disk... and select "package.json" that is inside the Asset folder of extracted "analyzers-package.zip"
5. In the Toolbar select Edit > Preferences... and under External Script Editor select Visual Studio Code
6. In the Preferences window click Regenerate project files
7. Open folder in which "a-project.zip" is extracted and open "Assembly-CSharp.csproj" with a preferred text editor
8. Search for "Assets\Google.Protobuf.dll"

Expected result: path to "Google.Protobuf.dll" ends with "Assets\Google.Protobuf.dll"
Actual result: path to "Google.Protobuf.dll" ends with "Packages\com.my.sonar-analyzers\Google.Protobuf.dll"

Reproducible with: 1.2.4 (2019.4.36f1, 2020.3.30f1, 2021.2.12f1, 2022.1.0b8, 2022.2.0a5)
Not reproducible with: 1.2.5 (2019.4.37f1, 2021.2.13f1, 2021.2.17f1, 2022.1.0b9, 2022.1.0b14, 2022.2.0a6, 2022.2.0a9)

  1. Resolution Note (fix version 1.2.5):

    Fixed in: 1.2.5 (2019.4.0f1, 2020.3.0f1, 2021.2.0f1, 2022.1.0a1, 2022.2.0a1)

  2. Resolution Note:

    Fixed in: 2021.2.13f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.