Skip to content
← LINQPad Feature Suggestions

I suggest you ...

LINQPad Feature Suggestions

Categories

(thinking…)

Add "Export To Visual Studio" to generate a solution and project based on the LINQPad script

LINQPad is awesome for quick scripts, but sometimes they grow to the point that you just have to promote them to a full-blown Visual Studio project. It would be awesome to have a feature to be able to do a "Save As Solution", which would generate a Visual Studio compatible Solution and Project, and move your code into a new class as well as providing a generated DataContext.

50 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Steve W. shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Guillaume Collic commented  ·   ·  Report

    In my company, LinqPad is used by few developers (mostly me) for the simple reason it can't be shared with our colleagues working on Mac.
    Making it easier to export a personal LinqPad script to a format that can be shared as a csproj usable by colleagues even on Mac would be better than nothing.
    MVP: basic export, without any transformation (`Dump` won't compile, etc.).
    Nice to have: converting `Dump` to basic ToString console write (without any of the LinqPad magic).

  • Anonymous commented  ·   ·  Report

    Additionally, let the user select if they want a full solution or a project (or even only a file with all "using" and other stuff) so that the result can be added to an existing solution or project.

  • Nick Portelli commented  ·   ·  Report

    I was just going to submit the same idea. Or even just a class.