JoeAlbahari said:wazzamatazz - Can you try deleting the installed package and trying again?
wazzamatazz - Can you try deleting the installed package and trying again?
90% of our 200+ linq pad scripts are used with 3rd party sdks that are not dotnet core compatible. One of the biggest features we were looking forward to was the #load support. Is there any possibility that we will be able to get similar functionality for full framework scripts? An alternative solution that would work just as well for us would be to have a linq file specify its own extension file rather than using the extension file of the user.
We love linq pad and just purched an enterprise upgrade. I was sad to see that it didn't work for the big project we were hoping to simplify with v6.
As of now, I don't see anything on the products roadmaps in regards to dotnet core sadly.
On my other note above, would it be too much work to allow queries to specify their own extensions file location or have something similar to extensions in v5? The extension file has worked well for us, but swapping out extensions or portable executable locations has been a bit of a pain.
Since queries won't work without the exact extensions as someone else on the team, I believe it would feel more natural. I can move this into another topic if you would like.