Quantcast
Channel: Xamarin.Forms — Xamarin Community Forums
Viewing all articles
Browse latest Browse all 75885

VS2015 + PCL + Xamarin Updates -> lots of errors, XS working fine

$
0
0

Hi all,

I've just updated my environment to work with the latest IOS 9 and xcode 7. This is not going as easy as I hoped..

First of all, I updated all at the same time (Xamarin Studio, Xcode and Visual Studio). But than I found this article, saying that xcode 7 is not yet supported in the stable channel, so I switched to beta in Xamarin Studio and Visual Studio.

Now I'm able to build and deploy a new project from Xcode and XS to my iPhone. Than I switched to Visual Studio and here I'm facing some problems..

When I create a new Shared Xamarin.Forms project I can immediately build it and deploy to my iPhone without any problems. But when I simply try to build my existing app with the new SDK for IOS 9, I get a lot of errors, saying I'm missing assembly references, which I didn't need before

like:
The type 'Object' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.

These missing references can be fixed by adding them, but it feels like there is something wrong with my environment. Any ideas? Besides that, I'm also having trouble getting PCLs to work in Visual Studio. When I try to build any PCL (via new projects or existing projects), I get the following error:

There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "C:\Windows\Microsoft.NET\Framework\v4.0.30319\\mscorlib.dll", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.

Is there anyone who faces the samen problem(s)? Or any ideas on where to begin? I'm not sure if reinstalling Xamarin Studio / Visual Studio will fix this problem..


Viewing all articles
Browse latest Browse all 75885

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>