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

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.

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.

As far my experience goes using dotnetfiddle.net, the "Tidy Up" functionality only remove unnecessary lines reducing code readability

Was just trying to run through the c# tutorial and realised the fiddler doesn't allow you to run code with Console.Read etc. Would be a nifty feature :)

It would come in handy to be able to click either the .NET Fiddle title in the top left corner, or a New Fiddle button to start over. Now, you have to refresh the page or go back to http://dotnetfiddle.net to create a new fiddle.

On top of each fiddle, it says "by <author's user name>". The author's username should be a link to take the user to all his/her fiddles.

Allow the usage of debugging such as stepping into a function, out of a function, run, memory mapping, local variables and the whole nine yards. It is vital if you don't want users to write constantly Console.WriteLine() statements.

Kindly, add debugging!

It would be nice to have a user page that lists the Fiddles that we have created. A main page of sorts.

Curley braces autocompletion would be so nice
and shortcut like cw + tab to write Console.WriteLine()

It would be cool to mark some words as `code` and others as *emphasized*.