Bug 14565 - Normal iOS project takes very long to build and start debugging
Summary: Normal iOS project takes very long to build and start debugging
Status: RESOLVED UPSTREAM
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Debugger ()
Version: 1.3.x
Hardware: PC Windows
: Normal normal
Target Milestone: 1.12 (Merge)
Assignee: Dominique Louis
URL:
Depends on:
Blocks:
 
Reported: 2013-09-09 13:14 UTC by Andy
Modified: 2016-05-10 17:04 UTC (History)
9 users (show)

Tags:
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:
Status:
RESOLVED UPSTREAM

Description Andy 2013-09-09 13:14:41 UTC
A project that takes around 15 seconds to build on the Mac, sometimes it "just" takes around 2 minutes from VS, sometimes it just hangs indefinitely, until I run the same project from the Mac. At that time, after a while it unfreezes and starts a new instance.

This has been going on for a long time, with all versions and actually on two different PC/Mac setups.

Makes VS integration useless
Comment 1 Andy 2013-09-09 13:18:46 UTC
When it hangs indefinitely:
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
this is what DEBUG says:

Getting device...
Starting debug on:iPhone 6.1
Remote building...
Microsoft (R) Build Engine version 4.0.30319.17929
[Microsoft .NET Framework, version 4.0.30319.18052]
Copyright (C) Microsoft Corporation. All rights reserved.

Build started 09/09/2013 19:15:11.
Project "\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj" on node 1 (_RemoteBuild target(s)).
_ResolveAssemblies:
  ResolveAssemblies Task
    ReferenceAssembliesDirectory: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\
    I18nAssemblies: 
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\monotouch.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\mscorlib.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\mscorlib.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\monotouch.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Core.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Xml.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Data.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Web.Services.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Json.dll
    [Output] ResolvedAssemblies:
      \\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.exe
      \\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.exe.mdb
      \\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.pdb
      \\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\TapkuLibrary.dll
_GenerateBundleContentDir:
  Preparing application bundle
  Copying file from "\\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.exe" to "\\ANDREAS-MAC\Projects\iosDO\iosDO\obj\iPhoneSimulator\Debug\build_package\assemblies\iosDO.exe".
  Copying file from "\\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.exe.mdb" to "\\ANDREAS-MAC\Projects\iosDO\iosDO\obj\iPhoneSimulator\Debug\build_package\assemblies\iosDO.exe.mdb".
_BuildNativeApplication:
  Saying hello to the remote server at http://192.168.153.129:49446/
  Fetching manifest...
  Updating information about the remote server
  Uploading changes...
  Synchronizing with the remote server
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
And Mac Server Log says:

[2013-09-09 19:15:31.0] Handling with command: [Info: CommmandUrl=Info] (24)
[2013-09-09 19:15:31.0] Attempting to acquire command execution lock, timeout set to 00:10:00
[2013-09-09 19:15:31.0] Starting /Developer/MonoTouch/usr/bin/mtouch -sdkroot "/Applications/Xcode.app/Contents/Developer" --listdev
[2013-09-09 19:15:31.9] Starting /Developer/MonoTouch/usr/bin/mtouch --version
[2013-09-09 19:15:32.2] stdout: mtouch 6.4.4.12 (62e07d5)
[2013-09-09 19:15:32.4] 
[2013-09-09 19:15:32.4] Starting /Developer/MonoTouch/usr/bin/mtouch -sdkroot "/Applications/Xcode.app/Contents/Developer" --entitlements
[2013-09-09 19:15:32.8] stdout: 874078a37ec2af58eaaad4896492547e7af946dc MonoTouch Business 2014-03-19T14:51:41
[2013-09-09 19:15:33.0] 
[2013-09-09 19:15:33.0] Command [Info: CommmandUrl=Info] finished (24)
[2013-09-09 19:15:33.0] Starting /Developer/MonoTouch/usr/bin/mtouch -sdkroot "/Applications/Xcode.app/Contents/Developer" --entitlements
[2013-09-09 19:15:33.9] stdout: 874078a37ec2af58eaaad4896492547e7af946dc MonoTouch Business 2014-03-19T14:51:41
[2013-09-09 19:15:34.1] 
[2013-09-09 19:15:34.1] Handling with command: [FileManifest: CommmandUrl=FileManifest] (24)
[2013-09-09 19:15:34.1] Attempting to acquire command execution lock, timeout set to 00:10:00
[2013-09-09 19:15:35.5] Command [FileManifest: CommmandUrl=FileManifest] finished (24)

_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________

it's been there for about 4 minutes now

Network connection is ok, I constantly check
Comment 2 Andy 2013-09-09 13:22:14 UTC
This is new: 

Error	2	MT2001:Could not link assemblies. Reason: Argument is out of range. [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
		0	0	

it happened after around 5 minutes

Debug log:

Getting device...
Starting debug on:iPhone 6.1
Remote building...
Microsoft (R) Build Engine version 4.0.30319.17929
[Microsoft .NET Framework, version 4.0.30319.18052]
Copyright (C) Microsoft Corporation. All rights reserved.

Build started 09/09/2013 19:15:11.
Project "\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj" on node 1 (_RemoteBuild target(s)).
_ResolveAssemblies:
  ResolveAssemblies Task
    ReferenceAssembliesDirectory: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\
    I18nAssemblies: 
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\monotouch.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\mscorlib.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\mscorlib.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\monotouch.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Core.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Xml.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Data.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Web.Services.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Json.dll
    [Output] ResolvedAssemblies:
      \\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.exe
      \\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.exe.mdb
      \\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.pdb
      \\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\TapkuLibrary.dll
_GenerateBundleContentDir:
  Preparing application bundle
  Copying file from "\\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.exe" to "\\ANDREAS-MAC\Projects\iosDO\iosDO\obj\iPhoneSimulator\Debug\build_package\assemblies\iosDO.exe".
  Copying file from "\\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.exe.mdb" to "\\ANDREAS-MAC\Projects\iosDO\iosDO\obj\iPhoneSimulator\Debug\build_package\assemblies\iosDO.exe.mdb".
_BuildNativeApplication:
  Saying hello to the remote server at http://192.168.153.129:49446/
  Fetching manifest...
  Updating information about the remote server
  Uploading changes...
  Synchronizing with the remote server
  Building...
  Building application on the remote server
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Remote build step failed. [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Response status: Error [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : error MT2001: Could not link assemblies. Reason: Argument is out of range. [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error :  [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error :  [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Remote build step failed. [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
Done Building Project "\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj" (_RemoteBuild target(s)) -- FAILED.

Build FAILED.

"\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj" (_RemoteBuild target) (1) ->
(_BuildNativeApplication target) -> 
  C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Remote build step failed. [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Response status: Error [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : error MT2001: Could not link assemblies. Reason: Argument is out of range. [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error :  [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error :  [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
  C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Remote build step failed. [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]

    0 Warning(s)
    2 Error(s)

Time Elapsed 00:04:23.08


Microsoft (R) Build Engine version 4.0.30319.17929
[Microsoft .NET Framework, version 4.0.30319.18052]
Copyright (C) Microsoft Corporation. All rights reserved.

Build started 09/09/2013 19:15:11.
Project "\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj" on node 1 (_RemoteBuild target(s)).
_ResolveAssemblies:
  ResolveAssemblies Task
    ReferenceAssembliesDirectory: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\
    I18nAssemblies: 
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\monotouch.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\mscorlib.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\mscorlib.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\monotouch.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Core.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Xml.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Data.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Web.Services.dll
  Skipping profile assembly: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoTouch\v4.0\System.Json.dll
    [Output] ResolvedAssemblies:
      \\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.exe
      \\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.exe.mdb
      \\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.pdb
      \\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\TapkuLibrary.dll
_GenerateBundleContentDir:
  Preparing application bundle
  Copying file from "\\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.exe" to "\\ANDREAS-MAC\Projects\iosDO\iosDO\obj\iPhoneSimulator\Debug\build_package\assemblies\iosDO.exe".
  Copying file from "\\ANDREAS-MAC\Projects\iosDO\iosDO\bin\iPhoneSimulator\Debug\iosDO.exe.mdb" to "\\ANDREAS-MAC\Projects\iosDO\iosDO\obj\iPhoneSimulator\Debug\build_package\assemblies\iosDO.exe.mdb".
_BuildNativeApplication:
  Saying hello to the remote server at http://192.168.153.129:49446/
  Fetching manifest...
  Updating information about the remote server
  Uploading changes...
  Synchronizing with the remote server
  Building...
  Building application on the remote server
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Remote build step failed. [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Response status: Error [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : error MT2001: Could not link assemblies. Reason: Argument is out of range. [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error :  [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error :  [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Remote build step failed. [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
Done Building Project "\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj" (_RemoteBuild target(s)) -- FAILED.

Build FAILED.

"\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj" (_RemoteBuild target) (1) ->
(_BuildNativeApplication target) -> 
  C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Remote build step failed. [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Response status: Error [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : error MT2001: Could not link assemblies. Reason: Argument is out of range. [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error :  [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error :  [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]
  C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Remote build step failed. [\\ANDREAS-MAC\Projects\iosDO\iosDO\iosDO.csproj]

    0 Warning(s)
    2 Error(s)

Time Elapsed 00:04:23.08
Comment 3 Andy 2013-09-09 13:22:53 UTC
Last part of mac server log:

[2013-09-09 19:19:30.7] Copying '/Users/Andy/Library/Caches/Xamarin/mtbs/builds/iosDO/0bb96013-5c98-4ac5-89a0-26754f388da2/bundle/iosDO.app/Images/Logo_icon_58.png' to '/Users/Andy/Library/Caches/Xamarin/mtbs/builds/iosDO/0bb96013-5c98-4ac5-89a0-26754f388da2/output/Debug/iPhoneSimulator/iosDO.app/Logo_icon_58.png'
[2013-09-09 19:19:30.7] 	Running tool: TrialCheckChanges
[2013-09-09 19:19:30.7] Starting /Developer/MonoTouch/usr/bin/mtouch -sdkroot "/Applications/Xcode.app/Contents/Developer" --entitlements
[2013-09-09 19:19:31.2] stdout: 874078a37ec2af58eaaad4896492547e7af946dc MonoTouch Business 2014-03-19T14:51:41
[2013-09-09 19:19:31.4] 
[2013-09-09 19:19:31.4] 	Running tool: Mtouch
[2013-09-09 19:19:31.4] Starting /Developer/MonoTouch/usr/bin/mtouch -v -sdkroot "/Applications/Xcode.app/Contents/Developer" --cache "/Users/Andy/Library/Caches/Xamarin/mtbs/builds/iosDO/0bb96013-5c98-4ac5-89a0-26754f388da2/output/temp/mtouch-cache" --nomanifest --nosign -sim "/Users/Andy/Library/Caches/Xamarin/mtbs/builds/iosDO/0bb96013-5c98-4ac5-89a0-26754f388da2/output/Debug/iPhoneSimulator/iosDO.app" -r "/Users/Andy/Library/Caches/Xamarin/mtbs/builds/iosDO/0bb96013-5c98-4ac5-89a0-26754f388da2/assemblies/MBProgressHUD.dll" -r "/Users/Andy/Library/Caches/Xamarin/mtbs/builds/iosDO/0bb96013-5c98-4ac5-89a0-26754f388da2/assemblies/TapkuLibrary.dll" -debug -linksdkonly -sdk "6.1" -targetver "5.0" --gsharedvt=false --abi=i386 "/Users/Andy/Library/Caches/Xamarin/mtbs/builds/iosDO/0bb96013-5c98-4ac5-89a0-26754f388da2/assemblies/iosDO.exe"
[2013-09-09 19:19:34.3] stderr: error MT2001: Could not link assemblies. Reason: Argument is out of range.
[2013-09-09 19:19:34.5] 
[2013-09-09 19:19:34.5] stdout: Xamarin.iOS 6.4.4 Business Edition using framework: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator6.1.sdk
[2013-09-09 19:19:34.5] Linking SDK only for assembly /Users/Andy/Library/Caches/Xamarin/mtbs/builds/iosDO/0bb96013-5c98-4ac5-89a0-26754f388da2/assemblies/iosDO.exe into /Users/Andy/Library/Caches/Xamarin/mtbs/builds/iosDO/0bb96013-5c98-4ac5-89a0-26754f388da2/output/temp/mtouch-cache/PreBuild
[2013-09-09 19:19:34.5] 
[2013-09-09 19:19:34.5] Error: Tool MonoTouch.Tools.Tools.Mtouch failed to run
[2013-09-09 19:19:34.5] Command [Build: CommmandUrl=Build] finished (33)
Comment 4 Andy 2013-09-11 10:42:01 UTC
Even worse... 8 minutes !!!!

  Preparing application bundle
_BuildNativeApplication:
  Saying hello to the remote server at http://10.0.0.17:49224/
  Fetching manifest...
  Updating information about the remote server
  Uploading changes...
  Synchronizing with the remote server
  Building...
  Building application on the remote server
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Remote build step failed. [\\10.0.0.17\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Response status: Error [\\10.0.0.17\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : error MT2001: Could not link assemblies. Reason: Argument is out of range. [\\10.0.0.17\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error :  [\\10.0.0.17\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error :  [\\10.0.0.17\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Remote build step failed. [\\10.0.0.17\Projects\iosDO\iosDO\iosDO.csproj]
Done Building Project "\\10.0.0.17\Projects\iosDO\iosDO\iosDO.csproj" (_RemoteBuild target(s)) -- FAILED.

Build FAILED.

"\\10.0.0.17\Projects\iosDO\iosDO\iosDO.csproj" (_RemoteBuild target) (1) ->
(_BuildNativeApplication target) -> 
  C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Remote build step failed. [\\10.0.0.17\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Response status: Error [\\10.0.0.17\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : error MT2001: Could not link assemblies. Reason: Argument is out of range. [\\10.0.0.17\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error :  [\\10.0.0.17\Projects\iosDO\iosDO\iosDO.csproj]
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error :  [\\10.0.0.17\Projects\iosDO\iosDO\iosDO.csproj]
  C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(156,3): error : Remote build step failed. [\\10.0.0.17\Projects\iosDO\iosDO\iosDO.csproj]

    0 Warning(s)
    2 Error(s)

Time Elapsed 00:08:10.13
Comment 5 Andy 2013-09-11 10:48:35 UTC
Seems to me, at least recently, it locks at this for a very long while:
[2013-09-11 16:43:44.7] Handling with command: [FileManifest: CommmandUrl=FileManifest] (12)
[2013-09-11 16:43:44.7] Attempting to acquire command execution lock, timeout set to 00:10:00
[2013-09-11 16:43:44.7] Command [FileManifest: CommmandUrl=FileManifest] finished (12)


Full log (still 'working', has been there for 5 minutes, no signs of life):

[2013-09-11 16:43:41.9] Handling with command: [Info: CommmandUrl=Info] (10)
[2013-09-11 16:43:41.9] Attempting to acquire command execution lock, timeout set to 00:10:00
[2013-09-11 16:43:41.9] Starting /Developer/MonoTouch/usr/bin/mtouch -sdkroot "/Applications/Xcode.app/Contents/Developer" --listdev
[2013-09-11 16:43:42.9] Starting /Developer/MonoTouch/usr/bin/mtouch --version
[2013-09-11 16:43:43.1] stdout: mtouch 6.4.5.0 (1336a36)
[2013-09-11 16:43:43.3] 
[2013-09-11 16:43:43.3] Starting /Developer/MonoTouch/usr/bin/mtouch -sdkroot "/Applications/Xcode.app/Contents/Developer" --entitlements
[2013-09-11 16:43:43.8] stdout: 6bb53c61ee5a15ebb24fcf1480d22cb4054c9cc7 MonoTouch Business 2014-03-19T14:51:41
[2013-09-11 16:43:44.0] 
[2013-09-11 16:43:44.0] Command [Info: CommmandUrl=Info] finished (10)
[2013-09-11 16:43:44.0] Starting /Developer/MonoTouch/usr/bin/mtouch -sdkroot "/Applications/Xcode.app/Contents/Developer" --entitlements
[2013-09-11 16:43:44.5] stdout: 6bb53c61ee5a15ebb24fcf1480d22cb4054c9cc7 MonoTouch Business 2014-03-19T14:51:41
[2013-09-11 16:43:44.7] 
[2013-09-11 16:43:44.7] Handling with command: [FileManifest: CommmandUrl=FileManifest] (12)
[2013-09-11 16:43:44.7] Attempting to acquire command execution lock, timeout set to 00:10:00
[2013-09-11 16:43:44.7] Command [FileManifest: CommmandUrl=FileManifest] finished (12)
Comment 6 Andy 2013-09-11 10:55:19 UTC
Oh wow, this time it started successfully only after 8 minutes, 7 of which were spent at that point in the previous comment.

I tried with

PC A -> MacMini
PC B -> MacMini
PC B -> Mac

on two different networks

and with 4 different projects.

Same result, so I'm fairly sure there is something wrong with Xamarin integration in VS.

This makes VS integration obviously useless, any tips ?
Comment 7 Andy 2013-09-16 13:48:28 UTC
Today - as it seems this bug isn't getting any attention - I tried everything that crossed my mind, losing a few hours - but with a hint of progress.

I tried to bypass the router and use a simple switch. Please note: I previously tested every possible way with 3 different routers, on LAN and on WiFi, and also with a OSX VMWare Virtual Machine - all these changes produced more or less zero change. 

This solution instead seems to get a bit of help: instead of a pretty reliable 10 minutes wait after the Manifest line:

[2013-09-16 19:41:06.8] Handling with command: [FileManifest: CommmandUrl=FileManifest] (10)
[2013-09-16 19:41:06.8] Attempting to acquire command execution lock, timeout set to 00:10:00
[2013-09-16 19:41:07.4] Command [FileManifest: CommmandUrl=FileManifest] finished (10)

and before:

[2013-09-16 19:42:48.6] Starting /Developer/MonoTouch/usr/bin/mtouch -sdkroot "/Applications/Xcode.app/Contents/Developer" --entitlements

I get around a 3 minutes wait. Even better, it seems semi-random, at times it goes for 1 or 2 minutes with Hello World projects (as in the example)
This is still way too much (very simple project) but who knows, if anybody will have the goodwill to look into it, it might be of help ?

I would really like to get some insight from you guys, I'm pretty much using half of my coding time to understand how to dodge Xamarin Studio bugs...
Comment 8 Andy 2013-09-16 14:50:32 UTC
Update:

regrettably this is useless too: a simple Hello World project will take around 1 minute, a small project 2-3 minutes (and we're still in semi-acceptable times) but a semi-normal project will take up to 5-10 minutes.
So there is a small benefit, but only for small projects.

Meanwhile, I'm starting to hear the echo of my voice in here. Are you all still on holiday ?
Comment 9 Dominique Louis 2013-09-16 19:13:55 UTC
Hi Andy,
  thanks for you feedback. Could you please attach a sample project that is showing this delayed build? 

Thanks.
Comment 10 Andy 2013-09-16 19:55:49 UTC
A default empty project already incurs in a pause between 10 seconds and 2 minutes. This after removing the router. 

My "real" projects are for production environment and can't attach them. If I find the time I can try a fake semi complex project and attach it

Meanwhile I keep getting an alert that docs and sdk are out of sync.
Comment 11 Andy 2013-09-17 09:03:34 UTC
I'll build a sample semi-complex project and submit it. In the meantime I noticed this while opening any project on VS:
_________________________________________
Mono.VisualStudio.Extension.Utilities Warning: 0 : Failed to retrieve current project.
System.Runtime.InteropServices.COMException (0x80004005): Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))
   at EnvDTE._DTE.get_ActiveSolutionProjects()
   at Mono.VisualStudio.Extension.Utilities.GetCurrentProject(DTE dte)
Mono.VisualStudio.Extension.Utilities Warning: 0 : Failed to retrieve current project.
System.Runtime.InteropServices.COMException (0x80004005): Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))
   at EnvDTE._DTE.get_ActiveSolutionProjects()
   at Mono.VisualStudio.Extension.Utilities.GetCurrentProject(DTE dte)
Mono.VisualStudio.Extension.Utilities Warning: 0 : Failed to retrieve current project.
System.Runtime.InteropServices.COMException (0x80004005): Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))
   at EnvDTE._DTE.get_ActiveSolutionProjects()
   at Mono.VisualStudio.Extension.Utilities.GetCurrentProject(DTE dte)
Mono.VisualStudio.Extension.Utilities Warning: 0 : Failed to retrieve current project.
System.Runtime.InteropServices.COMException (0x80004005): Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))
   at EnvDTE._DTE.get_ActiveSolutionProjects()
   at Mono.VisualStudio.Extension.Utilities.GetCurrentProject(DTE dte)
Mono.VisualStudio.Extension.Utilities Warning: 0 : Failed to retrieve current project.
System.Runtime.InteropServices.COMException (0x80004005): Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))
   at EnvDTE._DTE.get_ActiveSolutionProjects()
   at Mono.VisualStudio.Extension.Utilities.GetCurrentProject(DTE dte)
Mono.VisualStudio.Extension.Utilities Warning: 0 : Failed to retrieve current project.
System.Runtime.InteropServices.COMException (0x80004005): Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))
   at EnvDTE._DTE.get_ActiveSolutionProjects()
   at Mono.VisualStudio.Extension.Utilities.GetCurrentProject(DTE dte)
________________________________________

And by the way, docs don't seem to be able to sync. I permanently get this:

[2013-09-17 15:00:48.1] Handling with command: [StatusSdk: CommmandUrl=StatusSdk] (9)
[2013-09-17 15:00:48.1] Attempting to acquire command execution lock, timeout set to 00:10:00
[2013-09-17 15:01:05.4] monotouch.xml
[2013-09-17 15:01:05.4] OpenTK.xml
[2013-09-17 15:01:05.4] MonoTouch.Dialog-1.xml
[2013-09-17 15:01:05.6] MonoTouch.NUnitLite.xml
[2013-09-17 15:01:05.6] NamespaceSummaries.xml
[2013-09-17 15:01:09.0] Using https://developer.apple.com/rss/com.apple.adc.documentation.AppleiPhone6.1.atom
[2013-09-17 15:01:13.4] API Docs installed version: 42.18.0.0
[2013-09-17 15:01:13.4] API Docs official version: 44.30.0.0
[2013-09-17 15:01:13.4] Apple Docs need to be updated.
[2013-09-17 15:01:13.4] Command [StatusSdk: CommmandUrl=StatusSdk] finished (9)
[2013-09-17 15:01:16.6] Handling with command: [UpdateDoc: CommmandUrl=UpdateDoc] (9)
[2013-09-17 15:01:16.6] Attempting to acquire command execution lock, timeout set to 00:10:00
[2013-09-17 15:01:16.6] Launched process
[2013-09-17 15:01:16.6] Command [UpdateDoc: CommmandUrl=UpdateDoc] finished (9)
[2013-09-17 15:01:18.9] Downloading Apple docs from http://devimages.apple.com/docsets/20130128/com.apple.adc.documentation.AppleiOS6.1.iOSLibrary.xar to /tmp/com.apple.adc.documentation.AppleiOS6.1.iOSLibrary.xar
[2013-09-17 15:01:19.1]   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
[2013-09-17 15:01:19.1]                                  Dload  Upload   Total   Spent    Left  Speed
[2013-09-17 15:01:19.1] 
[2013-09-17 15:01:19.8]   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
____________________

and agree to sync after the messagebox, but next time it says the same.
Comment 12 Andy 2013-09-17 09:53:55 UTC
The more I play with it, more bugs I find. 

Now after trying for an hour to build a semi-complex project I understood that you should _never_ modify project properties, nor icons/splashscreens, from VS. 
It completely messes up the project file. 

Sorry, no more time to play with it at the moment, have to work on other stuff. When I find some time I'll put together a sample project.
Comment 13 Dominique Louis 2013-09-17 12:26:59 UTC
Our next alpha release should address issues with SDK and Docs sync.

Without a test project that throws the "GetCurrentProject" COMException, it may be quite hard to track down.
Comment 14 Andy 2013-09-17 13:28:52 UTC
Hi,

I copied the project and I'm starting to remove stuff. 
I might be onto something. The more files there are the more time - potentially - it takes to pass from 

[2013-09-17 19:15:58.1] Current MonoTouch license is valid
[2013-09-17 19:15:58.1] Handling with command: [FileManifest: CommmandUrl=FileManifest] (10)
[2013-09-17 19:15:58.1] Attempting to acquire command execution lock, timeout set to 00:10:00
[2013-09-17 19:15:58.1] Command [FileManifest: CommmandUrl=FileManifest] finished (10)

to the next line

[2013-09-17 19:17:23.0] Starting /Developer/MonoTouch/usr/bin/mtouch -sdkroot "/Applications/Xcode.app/Contents/Developer" --entitlements
 
It seems a bit random, but the number of files, especially resources, influences a lot the time it pauses there.
Comment 15 Andy 2013-09-17 14:06:16 UTC
Read below the second line for the end result of the test. 

(after half afternoon...)
______________ First Test: removing stuff (took me 1h)
...it apparently doesn't matter that much. 

Right now, with a test project derived from the original one, I consistently got 1 minute 20 seconds pause three times in a row, then it got slightly better the last four times at 50 seconds...
Yesterday it was 10 minutes, removing the router helped a bit and times went under the 5 minutes... but it is too random and inconsistent.

I'll attach the sample project. (NOT!)
I kept removing stuff from a very big project, but it won't change, at this time the project is totally empty. It takes between 50 and 80 seconds at that pause.

(20 seconds later, grrrrrr) 
______________ Second Test: manually deleting obj/bin (took me 20 seconds, grrrrr)

At last I found out something ! Cleaning the project, then closing it, then removing everything under obj and bin made it very fast !

The problem is that often time when you do that, the info.plist and relative project resources (icons/splashscreen) gets corrupted.

___________________ Conclusion

But this is not feasible, nor reliable. You should really fix VS integration. At this point it's basically Alpha stage.

So, I guess I won't even attach the project, it's a default empty project...
Comment 16 Andy 2013-09-17 14:06:56 UTC
By the way: 

PLEASE Don't mark this thing as fixed, just because I found a very convoluted and unreliable way to make it work !!!
Comment 17 Andy 2013-09-17 14:14:36 UTC
In fact this is what gives now after a full clean:

Error	1	MT0007:The root assembly '/Users/Andy/Library/Caches/Xamarin/mtbs/builds/iosDO/0bb96013-5c98-4ac5-89a0-26754f388da2/assemblies/iosDO.exe' does not exist [\\10.0.0.10\Projects\iosDO\iosDO\iosDO.csproj]
		0	0	

Giving up !
Comment 22 Andy 2013-11-29 12:28:36 UTC
Hi,

Using 1.8 and latest beta as well, this issue seems mostly fixed, thanks.

However there is still a 20 seconds overhead compared to running the same project for debug on Xamarin Studio directly from the Mac. This happens even when not altering the project (not rebuilding it) and just launching the project for debugging...so I think it's a bit strange.

Not sure if it's part of the same problem, but it does make debugging a bit of a chore on VS. Do you think it's a bug, it can be fixed, etc ?

I'll mark it reopened so maybe you can see it (not sure how it works)

PS: no, I'm not in Xamarin, just trying to use your tools with a decent code editor...but I spend as much time here filing bugs that it's almost like I'm working with you guys :)
Comment 23 Andy 2014-01-04 14:27:57 UTC
Today I tried (in desperation) to install VS 2013 and see if things are better.

Nope, actually they're worse ! One out of two times I got:

Build server control connection failed
Mono.IOS.VisualStudio.MonoTouchPackage Error: 0 : Server 10.0.0.10 hung up connection. Unable to read data from the transport connection: A blocking operation was interrupted by a call to WSACancelBlockingCall. (System.IO.IOException)
[2014-01-04 19:26:40.0] INFO:Found Xcode, version 5.0.2 (3335.32).
[2014-01-04 19:26:40.6] INFO:Found Xamarin.iOS, version 7.0.4.209.

Sometimes VS stuck in a loop. Sometimes I had to kill it...
Comment 24 Andy 2014-01-04 14:32:32 UTC
Scratch that: it just won't work. With some projects it just goes:

Build server control connection failed
Mono.IOS.VisualStudio.MonoTouchPackage Error: 0 : Server 10.0.0.10 hung up connection. Unable to read data from the transport connection: A blocking operation was interrupted by a call to WSACancelBlockingCall. (System.IO.IOException)
[2014-01-04 19:26:40.0] INFO:Found Xcode, version 5.0.2 (3335.32).
[2014-01-04 19:26:40.6] INFO:Found Xamarin.iOS, version 7.0.4.209.
Mono.IOS.VisualStudio.MonoTouchPackage Warning: 0 : Build server returned an Warning.
Mono.IOS.VisualStudio.MonoTouchPackage Warning: 0 : Negotiating server information for pairing process.
[2014-01-04 19:27:10.7] monotouch.xml
[2014-01-04 19:27:10.7] OpenTK.xml
[2014-01-04 19:27:10.7] MonoTouch.Dialog-1.xml
[2014-01-04 19:27:11.1] MonoTouch.NUnitLite.xml
[2014-01-04 19:27:11.1] NamespaceSummaries.xml


and stays there.

Great, can't use VS 2013...
Comment 25 Andy 2014-01-05 14:07:57 UTC
Can I get at least a hint on how to go forward ? Can you please point me to any resource (or write it here) about pros and cons of having the solution on the PC hard disk, vs the Mac hard disk when using VS ? 

This way I might try to work around these and probably other bugs...
Comment 26 Marek Habersack 2014-01-07 07:03:08 UTC
Andy,

I believe I hinted to the possible cause in one of your other bug reports - you seem to keep the project on a network share. For that reason the data travels in 4-5 times bigger a volume around your network than it is necessary. The build process must effectively fetch all the source files to the windows machine to build them (that includes all the assets - graphics, sound, whatever else). If you keep your project in git repository then VS (if you have git installed in it) will _also_ fetch the whole git index. Then, after the build VS needs to write the files (thus upload them) to the shared location - dll, exe, pdb, mdb files all need to be uploaded. After that the remote build process needs to zip up the changed files - it _again_ causes the need to this time download all the built files to windows machine and create the zip archive which, built in memory on windows side, needs to be uploaded to the share (it uses the obj/ directory as its working area). When all of it is done, the zip needs to be uploaded to the build server which _again_ causes VS to fetch the archive from the share and upload it to the build server. To summarize, this is the traffic that takes place:

 [share](sources, resources, assets, etc) => [windows] build
 [windows] managed build => [share](dll, mdb, pdb, exe, .sdf, .suo, obj/ temporary contents 
              (including .cache, .resources, generated sources from designer))
 [share](dll, mdb, pdb, exe, external resources) => [windows] zip
 [windows](zip) => [share]
 [share](zip) => [windows] for remote build on build host
 [windows] (zip) => [build host]
 
So if your code is, say, 100mb with everything needed for build and then you're looking at 500-600mb of traffic just to perform the build. If your project lived on your local windows disk the traffic would be less than 100mb (i.e. the zipped-up result of build on the first upload to the build host, less after that since only differences are zipped up and sent)

So please, for testing, move your project to Windows and test again - hopefully it will be faster.
Comment 27 Andy 2014-01-07 07:12:04 UTC
Alright thanks a lot for (finally) explaining the process in detail. This however is what I (we) knew at present, how it was publicly stated: build happens on the Mac. So it made sense keeping the files on the Mac, right ?

Secondly, by inspecting the log, one doesn't get the impression times are slowed down by data transmission, but rather by locking/waiting procedures, or some kind of race.

Lastly, again, thanks for the explanation, but why isn't this info more public ? Anyway, at present the problem is that since the VS plugin is incomplete, one has to build now and then on the Mac, which results in long waits anyway.
Comment 28 Andy 2014-01-07 07:19:08 UTC
Specifically, from VS:

- no xcassets
- no deploy to device or no provisioning at times
- no choosing iphone 4" VS 3.5"
Can't remember the rest now
Comment 29 Marek Habersack 2014-01-07 07:57:23 UTC
(In reply to comment #27)
> Alright thanks a lot for (finally) explaining the process in detail. This
> however is what I (we) knew at present, how it was publicly stated: build
> happens on the Mac. So it made sense keeping the files on the Mac, right ?
Not quite, I'm afraid. Yes, the build takes place on mac _physically_ but as far as VS is concerned this is always a remote machine - so whenever you mount it, all the data has to travel back and forth, no way around it. And you must also consider that VS/msbuild might be opening and reading (thus transferring between the share and the local machine) files multiple times, for various reasons. If you account for any possible congestion on the network you will realize that such transfers can be slow (especially on WiFi if you use the link for .e.g. multimedia playback or backups etc). Also take into account the time to access the disk on both ends (yes, there's in-kernel caching involved) - all of those factors together contribute to longer build times in such environment as yours.
 
> Secondly, by inspecting the log, one doesn't get the impression times are
> slowed down by data transmission, but rather by locking/waiting procedures, or
> some kind of race.
Yes, that might be the impression, indeed, but the bulk of time is spent shuffling data. The build itself may take a longer time because of AOT and linking, but it will rarely outweigh the network traffic timewise for large payloads.

> 
> Lastly, again, thanks for the explanation, but why isn't this info more public
> ? Anyway, at present the problem is that since the VS plugin is incomplete, 
one
> has to build now and then on the Mac, which results in long waits anyway.
Most people using Xamarin for VS work on the local machine so nobody has ran into this so far. The fact that the build is remote and involves transferring data is commonly known and explicit. The fact that network shares involve network traffic is beyond the scope of Xamarin tools and is also commonly understood. Those are the reasons, I suppose, why it was never explicitly stated in Xamarin documentation. But, perhaps, we should include a word on two on this.
Comment 30 Andy 2014-01-07 08:14:08 UTC
Ok, Marek, thanks again for the explanation. I don't understand why, but apparently you're the only person who actually solves my bugs/situations.

Just to be clear what happens on the other side of the fence (customers):

We don't really know very well what works and what doesn't. At times like this, we don't know HOW it works, especially regarding the VS plugin, which went though a year of extremely buggy changes. So, I'm sorry to say, we usually don't have a clue on how to use your tools, for example the VS tool, which for the most part of the year, wouldn't basically even install properly. Hence the insecurity on our part on how to use it, i.e. we try anything to make it work !

For this and other issues, hearing 'most people do something...', feels like you have tested only a limited use-case scenario, leaving to users (me apparently !) the chore of find bugs. I dedicated the better part of my work time in the last months trying to work around bugs in XS an VS.iOS, filing bug reports, doing test cases, etc . 
I worked particularly hard on this bug (and I don't work for you, like someone else suggested). It would have saved me A LOT of time if somebody took their time to explain this before now (or docs, for once). 

Again, thanks.

Side note: both computers have SSD, both are recent i5 and both are wired to the same router. So the hardware part of the lag is minimized as possible.
Comment 31 Marek Habersack 2014-01-07 08:45:38 UTC
Regarding testing. Do believe that we test the software on as wide an array of machines as possible, but consider the elements:

- 6 versions of windows (XP, Win7, Win8, Win8 - both 32 and 64 bit, counted as 
  separate versions)
- localized windows (which DOES introduce OS-level differences in Windows)
- 3 versions of visual studio
- 3 versions of OS X
- a myriad of possible 3rd party extensions that can be installed in any 
  combination in any version of VS
- 3rd party software on Windows which can affect the way other software works
  (especially networked) - firewalls, AV, filtering proxies

If you consider the number of combinations of the above then you'll see that it's a nearly NP-complete problem :)

Stay assured that we really test the software but also keep in mind that people will keep finding bugs no matter how much time we spend testing the software, that is the nature of software development.

With that, let me state that we're in a process of making the software more robust and hopefully in not so distant future there will be much less bugs from release to release.
Comment 32 Andy 2014-01-07 09:25:47 UTC
NP-Complete...maybe ! But then I feel I'm the one trying to crack it :) I filed.what...50 bugs ? I'll concede some are not real bugs, but rather glitches (and again, let me underscore that the trust in VS plugin is a bit shaky) ... 

So while I see your point, and I know perfectly well bugs are everywhere, I feel the VS release was rushed. Believe me, I started a myriad of times to port back everything to obj-c only to find I don't have the time now...

I want to love your tools, as well as using them (and paying then :) ). But it's very hard presently !

Anyway, thanks