Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 or GitHub 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.
I'm not really sure what's going on here. For whatever reason Xamarin Studio takes every chance it gets rebuild our solution which is time consuming.
If I open XS and not have any tabs/source/resources/etc open and hit deploy it will deploy. If I wait a short (minutes) period of time and hit stop and then play(icon) again it rebuilds the solution.
Silly Question #1: Is Dropbox involved? It's possible that if you're on Dropbox, or "something" is otherwise updating your file timestamps, you'll need to rebuild because "suddenly" things are out of date.
Silly Question #2: Does the same happen if you use `xbuild /t:Install Project.csproj` from the command-line. Which is to say, is this a build-system issue or a Xamarin Studio issue?
Silly Question #3? Build logs? :-)
ok, lets see if I can come up with some answers :)
1) Nope, no dropbox. Just a plain old directory on a run of the mill macos file system :)
2) using xbuild on the console is about the same
3) Logs sent :)
From the logs:
> Target CoreCompile needs to be built as input file '/Users/sshaw/code/xactware/git/mobile/Xactimate/Android/SharedCodeProjectFiles/bin/Debug/Core.Data.Enums.dll' is newer than output file 'obj/Debug/Core.Data.dll'
Rephrased: search the diagnostic build output for the phrase "newer than". Every such instance will result in rebuilding something, causing a cascade of rebuilds as everything gets updated. (There were 88 matches in the provided build output.)
If nothing has changed, there should be NO instances of "newer than" in the diagnostic build output.