Using the machine.config with .Net 3.5 RSS

• • Reply
  

  xtRmCheeZe

  Member

  61 Points

  29 Posts

  Using the machine.config with .Net 3.5

  Jan 07, 2008 05:16 PM|LINK

   Hi All,

  We're in the process of upgrading our servers from 2.0 to 3.5 on some Windows 2003 servers and I'm having trouble finding the answer to this question:

  There doesn't seem to be a machine.config in the /win/Microsoft.net/Framework/v3.5 directory after installation. Does the 3.5 framework use the machine.config from the 2.0 framework? 

  We have a couple environments setup with load balancing so I need to make sure I setup the machine keys correctly.

  Thanks for your help!
   

  ASP.NET Configuration windows 2003 server configuration configuration of ASP.net AsP Net 2.0 .Net 2.0 ASP.net 3.5 iis 6 asp .net .net 3.5 install .NET 3.5 machine.config load balancing

  "Behold, the power of CheeZe"
  • Edited by xtRmCheeZe on Jan 07, 2008 06:25 PM
• • Reply
  

  Careed

  All-Star

  18774 Points

  3637 Posts

  Re: Using the machine.config with .Net 3.5

  Jan 07, 2008 06:51 PM|LINK

  .NET 3.5 is only a layer on top of 2.0.  You can still required to maintain 2.0 to ensure that 3.5 also runs.  So, the Framework directory for 3.5 only contains files that are needed for the new version.  Anything that is unchanged is still accessed through 2.0.

  So, I guess the answer to your question is that you need to maintain the machine.config under 2.0.  Thus, if it's already been configured to work with 2.0, then it should be ready for 3.5.

  Christopher Reed, MCT, MCPD, MCTS, Microsoft Specialist, MTA
  "The oxen are slow, but the earth is patient."
  • Marked as answer by xtRmCheeZe on Jan 07, 2008 07:07 PM
• • Reply
  

  xtRmCheeZe

  Member

  61 Points

  29 Posts

  Re: Using the machine.config with .Net 3.5

  Jan 07, 2008 07:11 PM|LINK

  Thanks Careed!

  After doing a little more search on the open web, I found some replies in Scott Gu's blog that explained how .Net 3.5 uses the same CLR as version 2.0 and how the configuration files used are determined by the CLR version, not the framework version.

  Here's what he said:

  <div class="commentssubhead"> Wednesday, August 01, 2007 2:09 AM by ScottGu </div>

  Hi Mike,

  >>>>>> I don't get it, the settings would be in the global configuration for .NET 3.5. How is that a problem for AJAX 1.0 applications, they are running on .NET 2.0 or 3.0 right? So then they wouldn't see the new configuration...

  The configuration files for applications are versioned using the CLR version, and not the framework library versions.  .NET 3.5 uses the same CLR version as .NET 2.0 - and so share the same root web.config file.  That is why putting the configuration settings there would cause conflicts.

  Hope this helps,

  Scott

  
   

  "Behold, the power of CheeZe"