Use the local Plugins folder for My Extensions even if the machine has a configuration for it
In the settings of the normal LINQPad instant I run, I have set up special folder for queries, plugins, and snippets, in order to synchronize them using Dropbox.
However, I also use LINQPad on the build machine, so I have checked in a copy of LINQPad with its own local Queries folder.
If I create a local Plugins folder, and then try to use the "My Extensions" script in LINQPad, when running the build machine LINQPad instance (still on my own machine though), it still uses the global settings for picking up My Extensions.
I'd like to have a local copy of My Extensions as well, to store common code for the build scripts, things like integration with TFS, TeamCity, etc. all handy routines that I'd like to avoid having to duplicate.
Now, I can easily make such an extension and drop it into the folder. When executing on the build machine, there's no global setting, so the extensions will be used, but it makes it a hassle to edit the build scripts on my own machine.
I hope I made myself clear, otherwise let me know.
Lasse Vågsæther Karlsen
shared this idea
-
Anonymous
commented
+1 to this. Even something like if there's a Plugins folder under whereever Linqpad.exe exists, use that to load plugins/extensions rather than going and looking for a profile folder.
We've recently started using linqpad for a number of monitoring/reporting queries running on our build machine and while I got it working by futzing with the profile/settings folders on the build machine.
Would be super useful if you could support this..