views:

43

answers:

2

I've read the whole thread about running PowerShell under .NET 4.0, including the warnings about what happens when using the registry keys to make the scripts run under that framework.

So far, I only get the desired result with the registry keys. Is anyone aware of a way to make this work without changing the registry keys? When I checked PowerGUI's discussion boards, even they pointed to the stackoverflow thread. Has anyone come up with something better since April 2010?

+1  A: 

RE "something better" - short of PowerGUI being recompiled to target .NET 4.0 - no. Out of curiousity, what .NET 4.0 feature are you trying to access in .NET 4?

Keith Hill
Oh, bignum support would be quite nice to have natively. Some Project Euler tasks are awkward to do otherwise.
Joey
@Keith Hill We have some custom cmdlets we're using for UI automation that are compiled under .NET 4.
Scott A. Lawrence
A: 

I'm not a dev but maybe you create a config file for powergui. Check this page:

http://poshcode.org/1971

Shay Levy
@Shay The config file only applies for PowerShell ISE. I've already made that configuration file change.
Scott A. Lawrence