You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since visualscripting using CodeDom class and it was conflict with nuget codedom that being dependencies of some package
Library\PackageCache\com.unity.visualscripting@1.9.4\Editor\VisualScripting.Core\Platforms\MethodInfoStubWriter.cs(13,37): error CS0433: The type 'CodeStatement' 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'
But I think anything using CodeDom will cause this error (such as Google.Api.Auth)
Currently now I can uninstall visualscripting I don't used. But it's not ideal if I need to work with project that require visualscripting
Should we remove the dependencies of System.CodeDom and similar library that incorporated into unity from nuget registry, or should we try to force visualscripting to use nuget. Or are there any other sensible fix?
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.
If you think this issue should stay open, please remove the Stale label or comment on the issue.
Since visualscripting using CodeDom class and it was conflict with nuget codedom that being dependencies of some package
The package that can cause this error is
But I think anything using CodeDom will cause this error (such as Google.Api.Auth)
Currently now I can uninstall visualscripting I don't used. But it's not ideal if I need to work with project that require visualscripting
Should we remove the dependencies of
System.CodeDom
and similar library that incorporated into unity from nuget registry, or should we try to force visualscripting to use nuget. Or are there any other sensible fix?The text was updated successfully, but these errors were encountered: