I have experienced serious build and deploy issues using using https://www.nuget.org/packages/NuSpec.ReferenceGenerator/2.0.0-beta-bld14 package in the following project: https://github.com/XLabs/Xamarin-Forms-Labs
Build process extremely slows down for the iOS build on Mac using Xamarin Studio 6. It seems that MSBuild and GetCopyToOutputDirectoryItems tasks are the slow ones. Android build on Windows using XS 6 is not affected. VS2015 build is not affected either, but debugging from VS is - it stands couple of minutes on "Start debugging Android application..." before debugger finally attaches. You can download Xamarin-Forms-Labs and try this out - set build verbosity to diagnostic.
Even experienced Xamarin Studio crash when referenced XLabs projects referencing NuSpec.ReferenceGenerator from other solution. Unfortunately I cannot publish this solution.
I have filed bug reports to Xamarin's bugzilla before finally recognized NuSpec.ReferenceGenerator is the cause of these symptoms.
As a workaround I removed NuSpec.ReferenceGenerator reference from all projects in my fork.
I have experienced serious build and deploy issues using using https://www.nuget.org/packages/NuSpec.ReferenceGenerator/2.0.0-beta-bld14 package in the following project: https://github.com/XLabs/Xamarin-Forms-Labs Build process extremely slows down for the iOS build on Mac using Xamarin Studio 6. It seems that MSBuild and GetCopyToOutputDirectoryItems tasks are the slow ones. Android build on Windows using XS 6 is not affected. VS2015 build is not affected either, but debugging from VS is - it stands couple of minutes on "Start debugging Android application..." before debugger finally attaches. You can download Xamarin-Forms-Labs and try this out - set build verbosity to diagnostic. Even experienced Xamarin Studio crash when referenced XLabs projects referencing NuSpec.ReferenceGenerator from other solution. Unfortunately I cannot publish this solution. I have filed bug reports to Xamarin's bugzilla before finally recognized NuSpec.ReferenceGenerator is the cause of these symptoms. As a workaround I removed NuSpec.ReferenceGenerator reference from all projects in my fork.