Framework 1.0 SP3 clobbers "mscofcfg.msc"

[Bert Hyman]

The installation of Framework 1.0 SP3 destroys the "Microsoft .Net
Configuration" utility, mscorcfg.msc, normally accessed via "Start->
Programs->Administrative Tools".

I discovered this problem while tracking down the "typeFilterLevel"
problem with our application.

I downloaded fresh copies of the Framework 1.0, SP1, SP2 and SP3 from
the MS Web site this morning.

I uninstalled Framework 1.0 completeley, then installed each piece,
rebooting and checking our application and mscorcfg.msc at each step.

After SP2, our application was still OK and mscorcfg.msc was unchanged
from the initial installation, dated 11/21/2001@1:13PM, 53,248 bytes.

After installing SP3, our app was broken and the "mscorcfg.msc" file
had been replaced by an XML text file, dated 2/12/2004@2:57PM, 41,692
bytes.

 

[Bert Hyman]

(e-mail address removed) ("Peter Huang") wrote in

I have made a test on two test machines and can not reproduce the
problem. After applied the sp3, the mscorcfg.msc file is an xml
file.(I attched the file, you may try to see if that works for you)

I'm afraid I don't understand what you're talking about.

The fact that mscorcfg.msc becomes an XML file after applying the SP3
update IS THE PROBLEM I'M DESCRIBING.

A .msc file is not supposed to be an XML file.

MMC doesn't read XML files.

Selecting "Microsoft .NET Framework Configuration" from the
"Administrative Tools" menu produces an error dialog which says "MMC
cannot open the selected file".

 

[Guest]

I have exactly the same problem when i try to acess it via
Start->Administrative tools. You can however use
mmc->Add SnapIn->.Net Framework Configuration .... to access the
..Net configuration settings. I even removed the mscorcfg.msc file and
the method described above still works. I do'nt know what the new xml
file is used for.

 

[Peter Huang]

Hi Bert,

I am sorry that if I make any confusion. Based on my knowledge, the xml
format of msc file is of the new feature of MMC 2.0.

MMC 2.0 allows several snap-ins to be added to a single console to create a
custom tool. Earlier versions of MMC used a proprietary file format for
tools created using MMC (with the .msc file name extension). This did not
allow the contents to be easily inspected or modified directly. In
contrast, MMC 2.0 uses an XML console file format, although console files
created using earlier versions of MMC will continue to work. Because XML is
text-based, these console files can be added to a source control system,
allowing you to maintain full-revision history.
http://msdn.microsoft.com/msdnmag/issues/01/03/mmc20/default.aspx

Also I mean after I applied SP3, the mscorcfg.msc do become an xml file and
I can still open the file by double click the mscorcfg.msc file.

If you still have any concern please feel free to let me know.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Iain Paton]

I am sorry that if I make any confusion. Based on my knowledge, the xml
format of msc file is of the new feature of MMC 2.0.

To quote from:
http://www.microsoft.com/windows2000/technologies/management/mmc/

"You can download MMC 1.2 in five languages. Windows 2000 includes MMC 1.2, but you can download MMC to Microsoft Windows NT® 4.0, Windows 98, Windows 98 SE, and Windows Millennium Edition (Windows Me) operating systems. (MMC 2.0 is not available for Windows 2000)."

So as the version of mscorcfg.msc supplied with SP3 is an XML file and therefore requires MMC 2.0 and MMC 2.0 is not available on Windoes 2000 (and aparrently anything earlier) then SP3 by definition breaks the framework for any OS prior to XP.
This sort of thing is almost as bad as randomly removing something like the System.Windows.Forms namespace from the framework.. breaks lots of things..

It's worth noting that the MS04-028 fix for framework 1.1 (i.e. 1.1 SP1) does not change it's mscorcfg.msc to an XML file in the same way that 1.0 SP3 does.

So, do you know where we can either download a version of MMC 2.0 for Windows 2000 and earlier, or when a non-broken version of SP3 for Framework 1.0 will be available ?

Rgds,
Iain

 

[Patrick Philippot]

After installing SP3, our app was broken and the "mscorcfg.msc" file
had been replaced by an XML text file, dated 2/12/2004@2:57PM, 41,692
bytes.

Hi,

Strangely enough, I have had a different experience.

After installing SP3, mscorcfg.msc was still in binary format. However,
after double-clicking it and making a few changes, the MMC asked whether
I wanted to save in the new 2.0 format. I clicked Yes and the file then
became an XML document.

I did the same with mscorcfg.msc in version 1.1 (which is still in
binary format) but in that case, I had no opportunity to save the msc
file when exiting the MMC. So it remained in binary format.

Did you say consistency ?

 

[Patrick Philippot]

I did the same with mscorcfg.msc in version 1.1 (which is still in
binary format) but in that case, I had no opportunity to save the msc
file when exiting the MMC. So it remained in binary format.

Of course, I could change this by creating a new empty console and
adding the Framework 1.0 configuration snap-in to it. This time I could
save the msc file as XML.

 

[Bert Hyman]

In

Hi Bert,

I am sorry that if I make any confusion. Based on my knowledge, the xml
format of msc file is of the new feature of MMC 2.0.

That's all very interesting, but so far as I know, MMC 2 was never
supplied for Windows 2000, which is the OS I'm concerned about.

Do you mean to say that you folks have already dropped support for dotNet
Framework on Windows 2000?

I'd like to hear more about that.

 

[Peter Huang]

Hi Bert,

I have reported the problem to our product group, and I will update you
with new information ASAP.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Will Buffington [MS 414076]]

Hello all,

My name is Will Buffington with Microsoft Developer Support. I wanted to
let everyone know that this issue is currently being investigated by the
development team as a possible bug. I'll let everyone know when I have more
information.

Will Buffington
Microsoft Developer Support

 

[Guest]

I'm dealing with the same problem here and I'm quite sure de file You've
attached is the solution. The problem is I'm not getting access to the file.

I would be really thankfull if someone could send it directly to my mailbox:
(e-mail address removed)
or,
does exist an article in the knowledge base where I can download de correct
file?

thanks.
Clodoaldo