[2018.1.0b2][netstandard2.0] Ambigous Reference

I think this is caused because netstandard has the same stuff as other already referenced assemblies.

Can the assembly references that overlap with netstandard be removed or any way to solve this?

Thanks ! (Great work getting netstandard available!)

 

Scripting Runtime Version: Experimental (.Net 4.6)
Scripting Backend: Mono
Api Compatibility Level: .Net Standard 2.0

I get this error in 'Jet Brains Rider 2017.3'

 

I was trying these settings and I get the same issue.

I thought maybe I was missing an extension for Visual Studio? I also checked the documentation but it's rather out of date regarding runtime and APIs.

Is this actually just a problem with the assembly references?

Also, does it matter if I use Nothivilians setup with with IL2CPP rather than Mono. What does this actually mean??

 

I have the same problem as @Nothilvien (in my case it happens on LINQ methods) and I already have 15.5.3 version.

It seems that it's a problem on Unity VS Tools when generating solution and projects files.

Unity compiles correctly but on Visual Studio it messes up project references and we get compilation errors regarding ambiguous references.

 

the guys from Intellij/resharper/rider are pretty fast and provided a fix here: https://github.com/JetBrains/resharper-unity/issues/329#event-1423421475 for their ide.

 

On my machine VSTU 3.6.0.1 works randomly in 2018.1b2. Sometimes it works, sometimes doesn't, and I don't understand the pattern.

Spoiler: Images

1. Here is a new project with a single Foo.cs script inside, Runtime - Net 4.6, API - Net 4.6. Initial state:


2. After opening it in Unity 2018.1b2:

VSTU works.

3. After closing Unity and deleting unnecessary files and folders:


4. After opening it in Unity 2018.1b2 again:

VSTU doesn't work.

5. And after doing the same once more:

Magically it works again!

 

I actually do use VS 2017. Mostly 15.6 Preview. Should I switch back to 2017 15.5?

 

For Rider this was fixed by setting TargetFramework version to >=4.5
Will be automatically done in Rider 2017.3.1 https://github.com/JetBrains/resharper-unity/issues/329

 

This error strikes again in 2018.1.0b6, when project references `…2018.1.0b6\Editor\Data\NetStandard`. The issue is that MSBuild always removes all hinted references to System.Core.dll and inserts the reference to System.Core.dll from the installed .Net framework.

This might be fixed once and for all by clearing 'AdditionalExplicitAssemblyReferences' property at the very end of the project file.

Code (XML):

1.   ...
2.   <PropertyGroup>
3.     <AdditionalExplicitAssemblyReferences />
4.   </PropertyGroup>
5. </Project>

http://msbuildlog.com/

 

I have this exact issue! I posted it in the 2018.1 forum, since I didn't see this thread earlier. I already reported it: Case number is 996937. It happens with VS Code / Visual Studio on all my tested machines.

I haven't had the opportunity to test agains b7 yet.