Bug 15426 - console no declared
Summary: console no declared
Status: NEW
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: VB.Net Binding ()
Version: unspecified
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2013-10-16 05:39 UTC by Declan Marks
Modified: 2013-11-21 04:40 UTC (History)
2 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 for Bug 15426 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Declan Marks 2013-10-16 05:39:42 UTC
When I try to debug a console application, it fails and comes up with loads of errors. When I use 'console' it says it isn't declared, It may be inaccessible due to its protection level. This is so annoying because im learning vb.net in A level computing.
Comment 1 Mikayla Hutchinson [MSFT] 2013-10-16 13:40:08 UTC
FYI the VS.NET support in Mono / Xamarin Studio is not actively developed. I would strongly recommend using C# if possible.