Bug 5629 - Cut and Copy do not work in files with random extensions
Summary: Cut and Copy do not work in files with random extensions
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 3.0.x
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2012-06-13 07:06 UTC by Max
Modified: 2012-06-13 07:28 UTC (History)
1 user (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 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:
RESOLVED FIXED

Description Max 2012-06-13 07:06:49 UTC
I am trying to build a Nancy project with Razor files (.cshtml)

Cut and Copy do not work in those files. Tried adding a file with random extension of .hghghg and got the same thing. Is there a work around? I saw in a previous bug  (4855) some talk about Mime types.

Max
Comment 1 Max 2012-06-13 07:11:12 UTC
txt files also do not work
Comment 2 Mike Krüger 2012-06-13 07:12:10 UTC
Fixed in master (should work in 3.0.2 as well).
Comment 3 Max 2012-06-13 07:14:03 UTC
I'm running 3.0.2 with the issue
Comment 4 Max 2012-06-13 07:28:16 UTC
Installed Beta 3.0.3.1 and it appears to be fixed. Thanks :)