You might be able to author a VS extension that creates a .linq file for the block of code that is selected in VS? You might be able to also grab the references and namespaces from the related file and add them to the .linq file as well? Then, you might be able to open your nifty new .linq file and execute it?
I was able to add LINQPad to the 'External Tools' list in VS and pass it the $(ItemPath) argument. This launches the entire file in LINQPad but isn't ideal.
You might be able to author a VS extension that creates a .linq file for the block of code that is selected in VS? You might be able to also grab the references and namespaces from the related file and add them to the .linq file as well? Then, you might be able to open your nifty new .linq file and execute it?
I was able to add LINQPad to the 'External Tools' list in VS and pass it the $(ItemPath) argument. This launches the entire file in LINQPad but isn't ideal.