System.objectmodel Warning Xamarin Does Not Run On Android

We are running the 'Welcome to Xamarin` example on Visual Studio Enterprise, using the latest Xamarin, in a Windows 8.1 environment. We are managing to build and run on both Window

Solution 1:

Right click on your Android project's references and manually add the reference: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.ObjectModel.dll. And technically that's a warning, not an error.

Solution 2:

I simply removed the reference entirely since none of my code actually used it.

Solution 3:

In the Package manager console type: (Select the Android project)

update-package -reinstall

Is slower but is the correct method and always works

Solution 4:

Exercise 1 from GitHub https://github.com/XamarinUniversity/XAM135/ when opening has the same problem.

Based on the above solutions I resolved by performing the following steps:

1. Update the Nuget Package

2. Save, close and abire the solution

3. Click on the Portable (shared) project-> Referencias-> Donet in the copy properties of the path = "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETPortable\v4.5\Profile\Profile111"

4. Open Windows Explorer and paste the path = "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETPortable\v4.5\Profile\Profile111", here is the System.ObjectModel.dll file

5. Click on the Droid Project -> Referencias and REMOVE System.ObjectModel

6. Right click on References and Add references

7. Click the Browse button and open the path = "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETPortable\v4.5\Profile\Profile111"

8. Select System.ObjectModel.dll, and then click Add and OK

9. The reference was added successfully! Save, compile the project.

Here is a similiar solution

Solution 5:

Try moving it to desktop, then add it as ref in solution. worked for me, visual studio had access to all the other ref but for some reason dident have access to that specific ref. So i moved it, and i think it gave visual studio access. simply try to move it where access wont be a problem.