Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.9.2
Issue ID
UVSB-2541
Regression
No
“error CS0433: The type 'CodeBinaryOperatorType' exists in both 'System.CodeDom and 'System" compilation errors are thrown when opening a specific project
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Observe the Console Window
Expected results: There are no compilation errors
Actual result: 9 “error CS0433: The type 'CodeBinaryOperatorType' exists in both 'System.CodeDom, Version=7.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' and 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'“ compilation errors are visible
Reproducible with: 2022.3.23f1, 2023.2.17f1, 6000.0.0b14
Could not test with: 2021.3.37f1 (Multiple “Multiple precompiled assemblies with the same name Grpc.Net.Client.dll included on the current platform” compilation errors)
Reproducible on: MacOS Sonoma 14.3.1 (Intel), Windows 11 (user’s)
Not reproducible on: No other environment tested
Notes:
- Clearing the Library folder does not remove the errors
- Does not reproduce on a blank project with the same Visual Scripting package version
- Removing the “Assets/Packages/System.Codedom.7.0.0” folder prevents these errors
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
- Foldout arrow indent is misaligned in the Inspector when used in Custom Type
- [Android] The Player screen turns black when playing a video under certain conditions
- Search window icons at the bottom are cut off when Search window is resized vertically
- "Try something else?" text label is cut off when searching for a long text in the Search window
- Rendering Debugger window sections do not have a minimum width set when resizing with the slider in the middle of the window
Resolution Note:
This issue is being caused by a second version of the System.CodeDom assembly being installed by NuGetForUnity that causes compilation errors in Visual Scripting.
You can get around this issue by
* Exiting Safe Mode
* Open the NuGet For Unity window
* Open the "Installed" tab
* Expand "Implicitely installed packages"
* Search for "System.CodeDom"
* click "Uninstall"
Visual Scripting should now compile as expected