NetFrameworkv1 WMI Provider?

I was pleased to discover you can use WMI to configure your machine.config and web.config files. This appealed to me as someone has been burnt changing their machine.config file in the past. That is until I found out it doesn’t work on the 1.1 framework. According to this posting they’re phasing out the WMI provider. Does anyone know if it is being replaced with anything? What is the current best practice for programmatically changing your machine.config?

From: Andy Cheung [MSFT] (hangc@online.microsoft.com)
Subject: Re: new namespace for v1.1?

 
View this article only
Newsgroups: microsoft.public.win32.programmer.wmi
Date: 2003-07-16 14:17:54 PST
This namespace and the WMI Configuration Provider are removed starting from
.NET Framework v1.1 Redist as part of our effort to phase out this provider
for various reasons. If you have .NET Framework v1.0 installed side-by-side,
you can still connect to root\NetFramework namespace using System.Management
in .NET Framework v1.1. However, you can only use the root\NETFrameworkv1
namespace to access configuration information specific to .NET Framework
v1.0.

-- 
Andy Cheung
Microsoft WMI Test Engineer
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Published Friday, October 10, 2003 12:24 PM by Jamie Cansdale

Comments

# re: NetFrameworkv1 WMI Provider?

According to comments by Scott Guthrie on the .NET Rocks show, Whidbey includes a new configuration API for modifying config files.

Bummer that they took out the config provider in 1.1 though. I hadn't heard that. They should have waited until they had an alternative before removing that functionality.

Friday, October 10, 2003 10:29 AM by Kevin Dente

# re: NetFrameworkv1 WMI Provider?

I was the one posting the original request. I was amazed by <a href="http://www.newtelligence.com/">newtelligence</a> use of it to configure their webservice extensions, only to notice it didn't work anymore when I moved to Everett. :(
<br/>
I agree they should have had a replacement before removing it altogether.

Friday, October 10, 2003 11:11 AM by Daniel Cazzulino

Leave a Comment

(required) 
(required) 
(optional)
(required)