Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.2.4
Issue ID
VSC-31
Regression
Yes
On Windows auto generated VS Code .csproj uses package name instead of folder name for "Compile Include" path
How to reproduce:
1. Open the attached “1382115.zip” project
2. Open Preferences window > External tools
3. Enable Embedded packages
4. Press the “Regenerate project files” button
5. Open “VX.Runtime.csproj”
Expected result: “Compile Include” line includes the actual folder path “<Compile Include="Packages\\UnityUtil\\Runtime\\Utils\\NativeUtil.cs" />”
Actual result: “Compile Include” line includes the package name instead of folder name “<Compile Include="Packages\\voxell.util\\Runtime\\Utils\\NativeUtil.cs" />”
Reproducible with: 1.2.4 (2019.4.34f1, 2020.3.26f1, 2021.2.8f1, 2022.1.0b3, 2022.2.0a1)
Not reproducible with: 1.2.3 (2019.4.34f1, 2020.3.26f1, 2021.2.8f1, 2022.1.0b3, 2022.2.0a1)
Notes:
- Not reproducible on Mac
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Asset Bundles retain their previous hash and CRC values when an object within a bundle is changed and rebuilt
- APV Reflection Probe Normalization breaks when SSGI is enabled
- Default Custom Components in project have Library counterparts
- [iOS]"The destination host has an erroneous SSL certificate" error is thrown when using UnityWebRequest to connect to the server with a self-signed certificate
- Freeze/crash on DynamicHeapAllocator::Allocate when opening a specific project
Resolution Note:
VS code package is now deprecated, this won't be fixed