Query isolation by process - run query as 32/64 bit
Regarding new query isolation by process in LINQPad beta:
When query is now run in separate process, it should be easy to start queries in 32/64 bit mode, regardless of how LINQPad alone is running.
Is it possible to define bitness of query?
If not, would it be possible to add such option?
It could be defined in F4 Query Properties.
I see those advantages:
1) Easier way for user to run query with different bitness.
2) Bitness config can be part of saved query .linq file
3) No need to distribute x64 version of LINQPad executable
What do you think?
When query is now run in separate process, it should be easy to start queries in 32/64 bit mode, regardless of how LINQPad alone is running.
Is it possible to define bitness of query?
If not, would it be possible to add such option?
It could be defined in F4 Query Properties.
I see those advantages:
1) Easier way for user to run query with different bitness.
2) Bitness config can be part of saved query .linq file
3) No need to distribute x64 version of LINQPad executable
What do you think?
Comments
First, LINQPad would need to use process isolation not just for query execution, but for all the other activities that involve loading user assemblies, such as reflecting types, creating driver domains, getting schema information, etc.
Second, it would cause trouble for the upcoming debugger in that a 32-bit host process cannot debug a 64-bit process and vice-versa. The workaround is writing a daemon executable that acts as an intermediary, communicating with the host via Remoting or similar. However this adds another unwelcome layer of complexity, as well as making it (even) harder to debug the debugger.
Thanks for explanation.