• Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

clamping .NET framework 3+ .. please HELP!!

argoran

Still gathering requirements...
Thanks received
1
Hi,

After microsoft ( in their infinite wisdom ) shipped .NET framework 2.0 - for all subsequent releases they stopped shipping them with their own version of the configuration wizard ( mscorcfg.msc ) instead from their documentation you've got to use v2.0's mscorcfg.msc.

my question here is - using that wizard it will always show .NET Framework 2.0 - so how the heck am I supposed to know whether I'm configuring v2.0 or 3.0 or 3.5??

any help would be appreciated....
 
Last edited: 13:22
Hi,

After microsoft ( in their infinite wisdom ) shipped .NET framework 2.0 - for all subsequent releases they stopped shipping them with their own version of the configuration wizard ( mscorcfg.msc ) instead from their documentation you've got to use v2.0's mscorcfg.msc.

my question here is - using that wizard it will always show .NET Framework 2.0 - so how the heck am I supposed to know whether I'm configuring v2.0 or 3.0 or 3.5??

any help would be appreciated....


.NET 3.0 and 3.5 is built on 2.0 (it is 2.0 core plus extras). Therefore you are either configuring 2.0 or 1.1 only and by configuring 2.0 you are configuring 3.0 and 3.5 by the same token.
 
.NET 3.0 and 3.5 is built on 2.0 (it is 2.0 core plus extras). Therefore you are either configuring 2.0 or 1.1 only and by configuring 2.0 you are configuring 3.0 and 3.5 by the same token.

but how could that be ? I did read most of the microsoft whitepapers regarding that they don't say that explicitly however they do say that the core of 2.0 is the same for 3.0 - but when it goes to securing the policies they mention that you use the same mscorcfg.msc ( http://msdn.microsoft.com/en-us/library/2bc0cxhc.aspx ) - so you assume that you have to seperately configure each version otherwise why mention it at all since 3.5 on deployment would deploy 2.0 & 3.0 anyway???

Also what about the new techs that are with 3.0/3.5 like WF WPF etc surely these would have to be clamped as well?
 

Advertisers

Back
Top