Settings and activity
13 results found
-
1 voteMatt shared this idea ·
-
0 votesMatt shared this idea ·
-
1 voteMatt supported this idea ·Matt shared this idea ·
-
0 votes
An error occurred while saving the comment Matt shared this idea · -
248 votes
An error occurred while saving the comment Matt commented@Joe - a good idea, but it is a lot of work to transfer all connections, queries etc manually to the portable folders and xml files. Hence it would be nice to have a menu option such as "File -> Create portable LinqPad" which asks you about a target folder, and then does all the copying and creating XML files.
(For the readers of this forum, here are the details: http://www.linqpad.net/PortableDeployment.aspx)
-
1 voteMatt shared this idea ·
-
1,132 votes
An error occurred while saving the comment Matt commentedThere is already a workaround available for this, read more at Stackoverflow:
http://stackoverflow.com/a/38199055/1016343 -
1,685 votes
An error occurred while saving the comment Matt commentedWhy not add support for the C:\Windows\Microsoft.NET\Framework64\v4.0.30319\csc.exe commandline compiler? Should not be too difficult to include a converter which generates *.cs files ... if some restrictions apply, like ommitting the .Dump() and use the Console.WriteLine() instead, it seems to be achievable. Something like a "Generate console app from LinqPad project". Like Martin already mentioned ... but the issue is that a LinqPad file handles the references differently, so something like an "export to console app" would be great.
-
31 votes
An error occurred while saving the comment Matt commentedSimply open Windows Explorer, type
%AppData%\LinqPad
into the path combobox and it will take you to the settings directory.ConnectionsV2.xml and RoamingUserOptions.xml can be edited with a text editor like
Notepad++, and since XML is an open standard it is easy to read and maintain.Copy the files to the target PC, note that the account name can be different, since
%AppData%\LinqPad
resolves to
C:\Users\[accountName]\AppData\Roaming\LINQPad\Matt supported this idea · -
7 votesMatt supported this idea ·
An error occurred while saving the comment Matt commentedCopying table content from one database to another in LinqPad would close the gap between SQL Management Studio and LinqPad and allow to simplify staging data while developing.
Matt shared this idea · -
84 votes
An error occurred while saving the comment Matt commented63 votes - but it is still unclear what a "linqshell" actually is ... could someone summarize this please and be more specific?
-
5 votesMatt supported this idea ·
-
7 votes
NOTE: The "Ctrl+Shift+M" dialog mentioned is the same as the one coming up in Management Studio when you right-click on a stored procedure and select "Execute..." from the context menu.