.NET Fiddle Ideas

  1. allow us to view compiled razor, and collapse code for readability

    allow us to

    1) View the compiled razor
    2) allow code folding of codetags and collapse/expand code for readability

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support ScriptCS

    ScriptCS has a syntax for loading assemblies and works better as a single file. I don't know if you plan on allowing .NET Fiddles (?...is that the plural of the thing you make in .NET Fiddle?) to load other assemblies, but I think it would be really cool to be able to do that.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support For Akka.NET

    Currently, dotNetFiddle throws when trying to use Akka.NET.
    There is an error message saying that some methods in JSON.NET are missing.
    We would love to have the ability to run live Akka samples from our docs site.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add same Keyboard Editor shortcuts as Visual Studio

    We need the same quick keyboard shortcuts as visual studio...
    CTRL+D - Duplicate line
    CTRL+K+C - Comment out line
    CTRL+K+U - Uncomment line
    ALT+ENTER - Automatically add or suggest missing namespace reference and add usings to the class (like resharper)

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Enable Vim key bindings.

    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.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Expression Bodied Properties

    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

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Keep Nuget Packages

    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

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support null check operators

    Allow the compilation of null check operators i.e. DataSet?.Tables.Count. Currently the "?" screws up everything and a compilation error is received:

    Code:
    System.Data.DataSet ds = null;

        if (ds?.Tables.Count == 0 || ds?.Tables[0]?.Rows.Count == 0)
    
    {
    Console.WriteLine("True");
    }
    else
    {
    Console.WriteLine("False");
    }

    Errors:
    Compilation error (line 8, col 10): Invalid expression term '.'
    Compilation error (line 8, col 11): Syntax error, ':' expected
    Compilation error (line 8, col 35): Invalid expression term '.'
    Compilation error (line 8, col 36): Syntax error, ':' expected
    Compilation error (line 8, col 46): Invalid expression term '.'
    Compilation error (line 8, col 47): Syntax error,…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow console output and the code to viewed in separate tabs

    In CodePen, you can show the HTML, CSS, and JS on one half of the iframe and the result on the other half, as well as open and close them by clicking on tabs located at the top of the iframe. It would be awesome if we could have the code be on one tab, and the console output on the other tab

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. work on projects as a whole and being able to download them after

    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

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Update NuGet

    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!

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow inclusion of other exiting fiddles

    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

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Be able to include import a Github repository

    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

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Flush the Console Buffer after run

    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.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Blazor project type

    Now that Blazor server-side has been released and client-side in preview (due to be released with .Net 5 in November), you should think about supporting the project type on .Net Fiddle

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. On .NET Core, you cannot do Console.ReadLine() as it doesn't work on that platform for some reason

    On .NET Core, you cannot do Console.ReadLine() as it doesn't work on that platform for some reason

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Automatically save the fiddle

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

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Allow user input features such as "Console.ReadKey()" etc

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

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

.NET Fiddle Ideas

Categories

Feedback and Knowledge Base