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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
VS code package is now deprecated, this won't be fixed