https://dotnetfiddle.net/jsV9f5

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).

Any plans to support an Azure Function like interface with files area for run.csx, function.json?

Lots of C# developers out there who can't afford to have an Azure Tenant that can help collaborate on our projects.

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.

View IL feature doesn't work.

Support MyGet as a source for nuget packages, example:
// @myget: mypackage -Version 2.7.0

Simple test:

static (int, int) Foo(int i)

{

  return (i+2, 1*2);

}

Current "result" :
Predefined type 'System.ValueTuple`2' is not defined or imported

Expected:
To compile (and work of course :-)

This includes updating "4.7.2" "Compiler" to accept C# 7.x and at least linking the proper dll with ValueTuple-a for "Roslyn 2.0"

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

Mobile/Desktop versions switch button is needed on main menu.

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.

some class libraries loaded from nuget need setting assembly attributes located in assemplyInfo.cs otherwise it fire an exception, like:

[assembly: AssemblyCompany("Company xyz")]

[assembly: AssemblyCopyright("Copyright © 2018 Company xyz")]

Enable setting these attributes in assemplyInfo.cs

Add support for collapsible regions

With postsharp AOP is available for C#. I wanted to try out a sample code at postharp. I downloaded the nuget package, but it didn't work.

PostSharp extends the C# and VB languages with a notion of pattern. The result: shorter, cleaner code that’s easier to write and understand, contains fewer defects and is less expensive to maintain.

Why would you make a Nuget Header Directive available for C# but not for VB.Net?