Bug 761 - Ctrl+Shift+Enter shortcut adds invisible character
Summary: Ctrl+Shift+Enter shortcut adds invisible character
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 2.6
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2011-09-12 13:06 UTC by Stas Kalashnikov
Modified: 2011-09-13 02:55 UTC (History)
1 user (show)

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

Compilation error (21.24 KB, image/png)
2011-09-12 13:06 UTC, Stas Kalashnikov

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:

Description Stas Kalashnikov 2011-09-12 13:06:44 UTC
Created attachment 327 [details]
Compilation error

Create a new cs file, paste the following code and place a cursor after semicolon. Then press Ctrl+Shift+Enter and F8 to build. You'll get a compilation error (see attached screenshot). There is invisible semicolon after closing curly bracket of Main method.

class App
    static void Main()
        Console.WriteLine("Hello, World!");
Comment 1 Mike Krüger 2011-09-13 02:55:03 UTC

That was very, very old code - it's not really working. It has inserted the semicolon between the delimiter chars.

I've updated it using the newer text editor structures.
(But looking at what it should be doing I don't think that his works - but at least it doesn't produce errors like that anymore)