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