Bug 2184 - vs.net, package failed output not visible in output window first time
Summary: vs.net, package failed output not visible in output window first time
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: 3.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Radek Doulik
URL:
Depends on:
Blocks:
 
Reported: 2011-11-23 15:19 UTC by Roman Kalantari
Modified: 2016-12-22 16:54 UTC (History)
6 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 NOT_REPRODUCIBLE

Description Roman Kalantari 2011-11-23 15:19:01 UTC
Whenever I get a packaging error and it says see the output (build) window for more details, the output window is blank the first time.

Steps:

1. put somethign invalid in androidmanifest.xml
2. attempt to package, error says to look in output window.
3. output window is blank.
4. run packaging again, same error but this time output window has results.
Comment 1 Parmendra Kumar 2015-01-16 12:42:25 UTC
@Roman I have checked this issue but I am not able to reproduce this issue at my end.
Could you please recheck this issue on latest build and let we know if you getting same behavior?
Comment 2 Jose Gallardo 2016-12-22 16:54:16 UTC
Marking the bug as resolved - not_reproducible.
Please feel free to reopen if you can reproduce it with current bits.
Thanks