Please enable vim key bindings. VsVim is one of the most downloaded Visual Studio extension, which is an indication of Vim key binding's popularity among .net devs.

The following paste is an example of code that compiles in visual studio that does not appear to be supported by dotnetfiddle: https://dotnetfiddle.net/224Hvk

I was just making a quick draft to make sure I understood the way this kind of assignment behaved to find it wouldn't compile on dotnetfiddle

When you add a nuget reference save it in the fiddle so when you open the fiddle again, either on the same machine or a different one, the packages are still there and you don't have to search for them again

Allow you to work on whole projects instead of a single at a time. Having the tree listed on the side allowing you to jump from page to page and looking more like a whole project. Also being able to download your project when it's completed

When trying to install System.Xml.XPath from NuGet (any version listed in the menu), installation is not allowed and this message is included at the end of the description of the package: "When using NuGet 3.x this package requires at least version 3.4". I think that updating NuGet is an important and urgent step for the functionality of this site. Gracias!

For example: I define a class Person in a fiddle named PersonClass.
Then I base a new fiddle PersonUseExample on existing fiddle PersonClass, so I don't need to declare the class again, just démonstrate how I can use it.

The idea is probably easier to implementis but similar to the exiting request: https://dotnetfiddle.uservoice.com/forums/228764--net-fiddle-ideas/suggestions/6056568-allow-multiple-files-for-console-projects

This would really help to make samples of bugs / issues in a repository. One could import all the files of a repository, then write a "Test" that fails and the owner of the repository could then check out why it fails easily.

See for example me manually uploading the files in a competitors product:
https://repl.it/@devedse/ErrorWhenLoadingJpgWithExif

I'm creating some samples for a project, and when using Console.WriteLine inside Tasks, the messages usually won't appear in the log window.

I'm currently required to add a "Thread.Sleep(1000)" or "Task.Delay(1000)" to allow the console buffer to appear.

It would be much better for everyone if this was handled by .NET Fiddle by default.

Please add this, at least as an option. Otherwise we can lose work. Thank you!

Hi it would be extremely useful if we had the Elvis operator.

I would like to be able to create projects that contain multiple files so that I can create tutorials to teach student.
The MVC project type for example allows for multiple files. but they are all together on screen and I can't close one down to focus on say the controller.

VS Code uses Theia https://www.theia-ide.org/index.html - Perhaps you could also use this in your UI?

Such as 'Def.1.1.1', which I successfully referenced but could not use.

The error is:

Compilation error (line 13, col 21): The name 'Def' does not exist in the current context.

The site shows that the package is "on disk", but '/usr/nugetCache/def' does not contain 1.1.1.

Is there a problem?

Change the text color with Console.ForegroundColor

That the code can be used:
Console.ForegroundColor = ConsoleColor.DarkBlue;

Console.Write ("Hello");

Console.ForegroundColor = ConsoleColor.DarkRed;

Console.WriteLine ("World");

It would be nice to see form submits pass through a controller method to another view. Currently I'm just throwing an exception to see passed values (https://dotnetfiddle.net/jZQKsM).

Allow for a teacher/student structure whereby a teacher can have access to students' files and create tutorials on .NET Academy visible to only students.

Some of my code uses System.Windows.Forms.BindingContext (i.e. non UI code) and I want to reference it dotnetfiddle.net

Unfortunately I can't write using System.Windows.Forms; as I get the error Compilation error (line 2, col 22): The type or namespace name 'Forms' does not exist in the namespace 'System.Windows' (are you missing an assembly reference?)