Bug 11716 - Build outputs dll file even when it fails
Summary: Build outputs dll file even when it fails
Status: VERIFIED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.8.x
Hardware: PC Mac OS
: High major
Target Milestone: 7.0 (C8)
Assignee: dean.ellis
URL:
Depends on:
Blocks:
 
Reported: 2013-04-10 16:00 UTC by Mikayla Hutchinson [MSFT]
Modified: 2016-06-06 17:10 UTC (History)
6 users (show)

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


Attachments
Build log (21.90 KB, text/plain)
2013-04-10 16:00 UTC, Mikayla Hutchinson [MSFT]
Details


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 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.

Related Links:
Status:
VERIFIED FIXED

Description Mikayla Hutchinson [MSFT] 2013-04-10 16:00:27 UTC
Created attachment 3796 [details]
Build log

If the build fails because the assemblies are too large, it still outputs the dll to the output directory. This causes Xamarin Studio to think it's up to date and not build it again. The build process can be seen in the attached log. Note that DeployOutputFiles happens before the scan phase.
Comment 3 dean.ellis 2016-06-06 15:11:05 UTC
@Mikayla is this still an issue? Given the size restrictions have been removed I think we can close this issue.
Comment 4 Mikayla Hutchinson [MSFT] 2016-06-06 15:31:43 UTC
Yes, makes sense to me.
Comment 5 Naqeeb 2016-06-06 17:10:06 UTC
As per comment 3 and comment 4, closing this issue.