Linqpad6 no longer has "Do not shadow assembly references" option

bkaperick
bkaperick
in General

Hello,

In Linqpad 5, under Edit>Preferences>Advanced there was an option to disable the default shadow/temp folder behavior and use the assemblies directly, though it seems this is no longer available in Linqpad 6. So my AppDomain.CurrentDomain.BaseDirectory is a temporary folder like C:\Users\\AppData\Local\Temp\LINQPad6_kbxkhhme\shadow-2.

I tried to get around this by customizing environment variables within my script, like
Environment.SetEnvironmentVariable("LINQPAD_LOCALAPPDATA", [path to my assemblies]);
Environment.SetEnvironmentVariable("LINQPAD_TEMP", [path to my assemblies]);

within the script, but it did not seem to change the behavior at all. Maybe there is a different way I should be setting environment variables?

Is there a reason that it's no longer possible to disable "shadow assembly references"?

Thank you for your time.

· Share on Facebook

Comments

  • JoeAlbahari
    JoeAlbahari

    What are you trying to accomplish by disabling shadowing?

    · Share on Facebook
  • bkaperick
    bkaperick

    Within a C# solution, I use the assembly location in order to find the build folder in order to load config files. But when executing the code from linqpad, the assembly location is now LINQPAD_TEMP. So I guess I need either to find a way to move my config files to the LINQPAD_TEMP folder along with the assemblies, or to customize the LINQPAD_TEMP folder location.

    Does that make sense?

    · Share on Facebook
  • JoeAlbahari
    JoeAlbahari

    Have you tried referencing your config files, too? LINQPad 6 will copy over anything that you reference, including non-assembly files.

    · Share on Facebook

Categories