We encourage you to head over to Microsoft Q&A for .NET for posting new questions and get involved today.
Debug error after switching to VS2017
USMember ✭✭
I recently downloaded and installed Visual Studio 2017 and upon attempting to debug my Xamarin.Android project (which still compiles and runs in VS2015) I get the following error:
I have made sure that all my included packages have been updated to the latest stable versions
(I am using some extra like: ZXing.Net.Mobile, NewtonSoft.Json, sqlite.net and Android.Support.v4/v7)
I have also tried another test app that I have (much smaller and doesn't use most of the components that the other uses) and that works fine even without updating the packages.
Is there some code tweaks that I need to do or some settings that I need to change because of the extra passages that are in use or am I having some other problem here?
Any help and suggest would be very appreciated, thank you.
Posts
This is a know bug and fixed in upcoming build. Brendan suggested a workaround here https://bugzilla.xamarin.com/show_bug.cgi?id=56787#c15
Please give it a try, and let us know if it helps
The steps in Bug 56787, Comment 15 are a bit outdated. The latest version of the Xamarin Tools for Visual Studio 2015 doesn't include the Mono.Posix file, so if you're up-to-date in Visual Studio 2015, you won't have that file in the location mentioned in Comment 15. I would recommend instead following the steps from the Release Blog post (that is also mentioned by a few users toward the bottom of that bug report):
https://releases.xamarin.com/common-issues-in-the-xamarin-15-2-2-release-being-tracked-by-the-xamarin-team/
(Or if you prefer, you can try installing a side-by-side instance of Visual Studio 2017 Preview version 15.3.0, which includes the fix for Bug 56787.)
@BrendanZagaeski
Thank you for your reply, I updated Xamarin on VS2015 and my project no longer was compatible with VS2015 so I had to get it working for VS2017. Downloading the file and including it in the extensions folder worked just fine and it is now up and running on my device just like usual.