Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.28f1
2022.3.5f1
2023.1.4f1
2023.2.0a23
Issue ID
UUM-43901
Regression
No
Remove svcutil.exe because it's not officially supported
How to reproduce:
1. Navigate to the Unity version through file explorer "D:\Unity\[Unity version]\Data\MonoBleedingEdge\lib\mono\4.5”
2. Search for the svcutil.exe file
Expected result: svcutil.exe file doesn't exist
Actual result: svcutil.exe file exists
Reproducible with: 2021.3.28f1, 2022.3.5f1, 2023.1.4f1, 2023.2.0a23
Reproducible on: Windows 10 Pro
Note: Unity doesn't officially support this tool and after a conversation with developers it's been decided this tool should be removed so it wouldn't cause any more confusion.
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
svcutil.exe that is in the Unity install is a managed executable that needs to be run with the Mono version that is also part of Unity install.
Data\MonoBleedingEdge\bin\mono.exe Data\MonoBleedingEdge\lib\mono\4.5\svcutil.exe
Launching svcutil.exe directly will use the .Net Framework that is installed and is not comparable.