Quantcast
Channel: Recent Threads — Xamarin Community Forums
Viewing all articles
Browse latest Browse all 204402

Xamarin new PCLs (W8+WP8+.Net45+Xamarin.iOS+Xamarin.Droid) plus new Microsoft BCL terribly broken!

$
0
0

Hi,

I've got a pretty tough problem...

My current Setup uses a PCL with Windows 8.1, Windows Phone 8, Android and iOS Projects. As soon as the new PCLs were launched I updated my setup to use the official approach by the xamarin team. The problem - the new BCLs of Microsoft released to support exactly those PCLs terribly destroyed my setup again.

That are my problems at the moment:

When using a PCL without Xamarin.iOS and Xamarin.Droid everything works just fine for Windows 8.1 and Windows Phone 8 (well I cannot reference this PCL directly in VS for iOS and Android...).

When using Profile 78 (Xamarin.iOS + Xamarin.Droid + W8 + WP8 + .Net45) without BCL.Async all projects compile BUT the designer does not work in Visual studio (in Blend it does)! It tells me about an invalid markup - with every single XAML marked as invalid. That drove me really crazy. I uninstalled VS2012, reinstalled VS2013, built up a clean project with all existing files, deleted the ShadowCache, tried to Debug via second VS instance, logged with powershell and even reinstalled my Windows 8 because I just thought that it had to work....

When using Profile 158 (= Profile 78 + SL5) without BCL.Async it does not compile (missing threading-ns)

When using Profile 78 WITH BCL.Async there is an ugly conflict with the existing threading-ns -> does not work

When using Profile 158 WITH BCL.Async it compiles BUT complains about an invalid markup in the VS designer again.

In addition to that the new BCLs are really hard to handle. It works if you install and uninstall every single BCL package (espacially .Build) via NuGet Commandline and delete the .configs and edit the .csproj manually...

That leads me to the descision to go for the originial PCL without xamarin support until W8.1 and WP8.1 are finished - then switch to Profile 158+BCL.Async to write iOS and Android. Is that really the way to go for at the moment?

Does anyone have a fix or another setup that works for him with the new PCLs + the new BCLs (13.11) (Espacially BCL.Async and BCL.Http) ?? As I reinstalled really everything and also switched back to 100% working TFS versions severeal days ago I think the new BCLs are the obvious lowest common denominators. Am I wrong with this?

I would be happy to hear from you guys.

Best regards, André


Viewing all articles
Browse latest Browse all 204402

Trending Articles



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