Search:   Namespaces Discussions .NET v1.1 Feedback

Apps no longer work with Framework 1.0 SP3 Messages   Related Types This message was discovered on microsoft.public.dotnet.framework. Responses highlighted in red are from those people who are likely to be able to contribute good, authoratitive information to this discussion. They include Microsoft employees, MVP's and others who IMHO contribute well to these kinds of discussions. Post a new message to this list... Bert Hyman Our administrators did an unannounced deployment of dotNet Framework 1.0 SP3 to all our Win2K machines last week and now the product we're developing no longer works, nor does the dotNet Framework Configuration tool. The machines runnning dotNet Framework 1.1 appear to be OK. When the app is executed, it produces this exception: "Request for the permission of type System.DelegateSerializationHolder failed." Trying to run the Configuration tool merely produces an error dialog "MMC cannot open the selected file" This is ->serious. -- Bert Hyman | St. Paul, MN | Click here to reveal e-mail address Reply to this message...        Bert Hyman Click here to reveal e-mail address (Bert Hyman) wrote in news:Click here to reveal e-mail address: [Original message clipped] A little more info... The new corrupt mscorcfg.msc file on my machine is an XML file that starts out <?xml version="1.0"?> <MMC_ConsoleFile ConsoleVersion="2.0" ProgramMode="Author"> <ConsoleFileID>{92BF0122-2B3D-42DC-BB73-9102F9EF13E0} </ConsoleFileID> Does this mean anything to anybody? -- Bert Hyman | St. Paul, MN | Click here to reveal e-mail address Reply to this message...        Peter Huang (VIP) Hi Bert, It seems that there is something corrupted, you may try to install the .net framework 1.1(in the repair installation mode) to see if that works for you. 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. Reply to this message...        Bert Hyman Click here to reveal e-mail address ("Peter Huang") wrote in news:wKxk#Click here to reveal e-mail address: [Original message clipped] Installing dotNet Framework 1.1 is ->not an option. We need to build and test our application on many OS levels and both 1.0 and 1.1 Framework levels. All of our Win2K systems with Framework 1.0 are completely out of business right now. I downloaded the Framework 1.0 SP3 package from MSDN yesterday and re-installed it but had exactly the same result. -- Bert Hyman | St. Paul, MN | Click here to reveal e-mail address Reply to this message...        Bert Hyman Click here to reveal e-mail address (Bert Hyman) wrote in news:Click here to reveal e-mail address: [Original message clipped] Following up on my own post, I believe I've found a fix to our app's immediate problem. When creating our BinaryServerFormatterSinkProvider, I set the typeFilterLevel property to "Full". We already did this when running under Framework 1.1, and apparently, this property was retrofitted to Framework 1.0 by the SP3 update. I guess if the update had gone through our normal qualification process instead of being forced on us by our administrators, we'd have known about this. Still, the fact that the "mscorcfg.msc" file was corrupted on all systems that received the update is ->very troubling. And, who knows what other incompatibilities have been introduced by this "fix" that we haven't run into yet. Short of re-installing the Framework from scratch, there doesn't appear to be any way to back out SP3; is that correct? -- Bert Hyman | St. Paul, MN | Click here to reveal e-mail address Reply to this message...        Bert Hyman Click here to reveal e-mail address (Bert Hyman) wrote in news:Click here to reveal e-mail address: [Original message clipped] Well, maybe not. Looking at the long laundry list of changes in SP3, which one of these would have told us of the changes to the properties of our BinaryServerFormatterSinkProvider? Further, how can we determine at runtime if our application is running on a system with SP3 installed, since the "typeFilterLevel" property didn't exist before? Is this what DLL Hell is like? -- Bert Hyman | St. Paul, MN | Click here to reveal e-mail address Reply to this message...     System.Runtime.Remoting.Channels.BinaryServerFormatterSinkProvider Ad MBR BootFX Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd. Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com