Pcls Won't Build In Xamarin Studio For Mac

Aug 31, 2017 - Upgrade PCL to. NET Standard Class library, in Visual Studio 2017. Starting a new project now, and won't be releasing until the end of the year. Microsoft MVP| Xamarin MVP| Xamarin Forms Developer| Build Flutter. Under the hood, it uses Mono (a version of the Microsoft.NET runtime), so Xamarin apps are usually written in C#. You can build Xamarin apps on Windows using Visual Studio, or Mac using Visual Studio for Mac. Even though Xamarin apps are not written in Swift (or Java), they still look and feel like real, native apps on the device.

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode. Please join us on and in the and organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future. Please create a new report on with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Ben Beckley 2017-05-26 20:41:13 UTC XVS 4.5.0.476 (1be4f0c/d15-2) As the summary says: can't hit breakpoints in a PCL project on device, however they are being hit on simulator. Reproduction Steps: 1) Create a new CrossPlatform Master Detail Forms PCL app 2) Place a breakpoint in the PCL code (In my case, BaseViewModel Line 31) 3) Allow XMA to connect, change startup project to iOS project, target a device for deployment 4) Deploy to the device 5) Do whatever action is needed to hit the breakpoint (if any) Expected: Breakpoint is hit Actual: Breakpoint is not hit env info. Brendan Zagaeski (Xamarin Team, assistant) 2017-06-01 02:11:17 UTC ## Possible temporary workaround: switch the portable class library project(s) to output 'portable' PDB files rather than 'full' PDB files 1. Open the portable class library.csproj file in a text editor. For example, right-click the project in the Solution Explorer and select Unload Project, and then right-click it again and select 'Edit.' Under the PropertyGroup for the 'Debug AnyCPU' configuration, change the DebugType to: portable 3. Save the change and reload the project.

Build, deploy, and start debugging the iOS app project again. This workaround was successful in my particular test environment using the scenario described in, but there might be other scenarios where the workaround will not be effective.

Brendan Zagaeski (Xamarin Team, assistant) 2017-06-02 03:55:00 UTC it now does not work on android Thanks for the note about that result. It seems that this is due to left-over.mdb debug symbol files. Long story short, if you manually delete the 'bin' and 'obj' folders for each of the projects that you have switched to `portable`, uninstall the app from the test device, and then clean and rebuild the solution, that should hopefully allow the `portable` mode to work with Android too. Once you have performed those clean-up steps once, you should in theory not need to perform them again unless you switch the DebugType again. (See for a bit more background information about the issue with stale.mdb files.). Brendan Zagaeski (Xamarin Team, assistant) 2017-06-08 02:25:41 UTC ## Additional workaround step for projects that use `async partial` methods For users trying the workaround, if any of your library projects contain `async partial` methods, you will hit a bug in the Roslyn C# compiler that causes 'csc.exe' exited with code -532462766' 1. To work around this error, you can install pre-release version 2.3.0-beta1 or higher of the 'Microsoft.Net.Compilers' NuGet package into all of your projects to use the latest Roslyn C# compiler (that includes the fix).

Brendan Zagaeski (Xamarin Team, assistant) 2017-06-08 02:28:05 UTC ## Note to the Xamarin team At the end of the steps in, the.mdb file for the PCL is present as expected in the 'mtouch-cache/Link' directory, but it is missing from the 'mtouch-cache/PreBuild' directory and the final.app bundle. This matches up exactly with the latest information on.

The problem seems to be caused by recent changes to the `LinkAssemblies` method in the `mtouch` tool on the Mac. Based on these results, I will mark this bug as a duplicate of. Once a candidate fix is available for, it would be good to double-check that the fix is also effective for this. This bug has been marked as a duplicate of. Brendan Zagaeski (Xamarin Team, assistant) 2017-06-14 19:57:22 UTC this workaround is ineffective in that case.

We need a solution. Note that this is issue is still being investigated as a critical issue in by the engineering team. The possible temporary workaround provided earlier in this bug was documented in case it might help some users.

It should not be interpreted to mean that the bug has a lower urgency. MyApp.dll can't be found To make a guess, this might be due to an incompatibility of Fody with the portable debugging type in some scenarios. In case you haven't checked it yet, the diagnostic build output might contain additional information about why the MyApp.dll is not building successfully for your scenario. There's a chance some of that information would allow you to make another small adjustment that would allow the build process to work successfully while using the portable debugging type.

Set 'Tools Options Projects and Solutions Build and Run MSBuild project build output verbosity' to Diagnostic. The next time you build the project the diagnostic build output will now be visible in the Output window. Eric 2017-07-03 18:00:49 UTC I get the following exception in my.NET Standard library (Target: 1.4.NET Standard). When the breakpoint is hit. In the MainActivity of the Droid project I hit the breakpoint and can step through.

Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. System.ArgumentException: Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. Brendan Zagaeski (Xamarin Team, assistant) 2017-07-03 19:00:37 UTC I get the following exception.

When the breakpoint is hit. This bug is about the specific symptom 'Unable to hit PCL breakpoints'. Receiving an exception when hitting a breakpoint is a different symptom from being unable to hit a breakpoint and would need to be investigated in its own bug report. Particularly if you still see that issue with the latest Xamarin preview or Visual Studio 2017 Preview versions, please submit a new bug report for the issue, ideally including a small self-contained test case that replicates the issue and as many other details as possible about the scenario (see also 1 for additional recommendations). Thanks in advance!

Brendan Zagaeski (Xamarin Team, assistant) 2017-07-04 01:15:43 UTC ## Verification status for the behavior described in: verified fixed by the latest Xamarin.iOS '15.3 release' Beta channel preview for the remote Mac GOOD: Xamarin.iOS 10.12.0.12 (494fcbc) BAD: Xamarin.iOS 10.12.0.5 (104e7b4) (In keeping with my usual verification procedure, I retested briefly on the 'bad' version first to ensure I was still able to replicate the issue on an older version.) ## GOOD Results The debugger did pause on the breakpoint at BaseViewModel.cs, line 31. ## BAD Results The debugger did not pause on the breakpoint in BaseViewModel.cs, line 31. ## Additional testing environment info ### Windows Microsoft Visual Studio Enterprise 2015 Version 14.0.25431.01 Update 3 Microsoft.NET Framework Version 4.6.01586 XamarinVS 4.6.0.240 (60c3d0e) Windows 10 version 1607 (OS Build 14393.0) US English locale, US Eastern time zone ### Mac Mono MDK 5.2.0.196 (2017-04/478c04a) Xcode 8.3, Build version 8E162 macOS 10.12.5 US English locale, US Eastern time zone ### Devices iPad Mini 2, iOS 8.0.