Bug 41247 - Visual Studio Extremely Slow on WinRT TargetSelected And Connected to iOS Simulator
Summary: Visual Studio Extremely Slow on WinRT TargetSelected And Connected to iOS Sim...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-05-23 08:35 UTC by ebubekirakgul
Modified: 2016-06-01 13:22 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono 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 Developer Community 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.

Related Links:

Description ebubekirakgul 2016-05-23 08:35:12 UTC
Steps to reproduce:
	- Create a Xamarin.Forms project
	- Connect iOS build host
	- Set WinRT project as Startup Project (Still connected to iOS build host)
	- Create a class on WinRT project(i.e. custom renderer) and implement something

	- Visual Studio being extremely slow, like waiting 3 seconds when pressing any key on keyboard.
	- This behaviour not observed when disconnected on iOS build Host.
Comment 1 Joaquin Jares 2016-06-01 13:22:43 UTC
This has been fixed in C7. Are you able to try alpha and check if you see the same? There was an issue with simulators loading at the wrong time that made this happen. This may be a different issue; I want to confirm it's the same.