I had a look at DnsShell. I like the idea but I’m concerned by the fact that it is compiled to target version 4 of the .NET Framework and therefore CLR v4. The standard PowerShell engine is built to work with CLR v2 only and while there are tricks to get it to be able to load .NET 4 assemblies, this isn’t ideal if you want to use the DnsShell module across several machines in several environments.
It appears the DnsShell source compiles fine if the project properties are changed to target .NET 3.5 so this should probably be done until either DnsShell is dependent on a .NET 4 feature or PowerShell officially supports .NET 4.
Posted by Jason Stangroome on 17.05.10 at 11:00 am
Hi,
I had a look at DnsShell. I like the idea but I’m concerned by the fact that it is compiled to target version 4 of the .NET Framework and therefore CLR v4. The standard PowerShell engine is built to work with CLR v2 only and while there are tricks to get it to be able to load .NET 4 assemblies, this isn’t ideal if you want to use the DnsShell module across several machines in several environments.
It appears the DnsShell source compiles fine if the project properties are changed to target .NET 3.5 so this should probably be done until either DnsShell is dependent on a .NET 4 feature or PowerShell officially supports .NET 4.
Regards,
Jason