Skirmish with .NET Framework versions 2.0, 3.0, 3.5 following update to SP1

[Doug]

System: Conventional PC with 4GB RAM, no swap file, Vista Home Premium with
all updates including SP1.

I am trying to run FxVisor32.msi (Vista Shortcut Overlay Remover from
http://www.cnet.com/) which installed normally but when run reports:
Unhandled exception error has occurred in your application. If you click
Continue, the application will ignore this error and attempt to continue. If
you click Quit, the application will close immediately.

The detailed report is appended. It will be seen that .NET\Framework\v2.0 is
involved. When I skip the message the program runs but a similar warning
(not shown here) is repeated with nothing achieved.

This incident follows a skirmish fought on my system between .NET Framework
3.5 and .NET Framework 3.0 following the installation of Nero 9.0.9.4 and
Nuance OmniPage 17 during which I ended up with both .NET 3.5 and 3.0
installed, as neither package would install with 3.5 alone..

I am wondering whether I now also need to install .NET Framework 2.0.
Ideally I suppose I am seeking a .NET environment that will cope with
everything that is thrown at it. Is it OK to have multiple versions of .NET
installed concurrently?

Perhaps I should just backup and then edit the icon overlay? Where would
that be? (I have icon editor IcoFX 1.6.4).

Doug


======== Appendix Starts =========
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Configuration.ConfigurationErrorsException: Configuration system
failed to initialize ---> System.Configuration.ConfigurationErrorsException:
Unrecognized configuration section system.serviceModel.
(C:\Windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config line
146)
at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean
ignoreLocal)
at
System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors
schemaErrors)
at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
at System.Configuration.ClientConfigurationSystem.EnsureInit(String
configKey)
--- End of inner exception stack trace ---
at System.Configuration.ClientConfigurationSystem.EnsureInit(String
configKey)
at
System.Configuration.ClientConfigurationSystem.PrepareClientConfigSystem(String
sectionName)
at
System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.RefreshConfig(String
sectionName)
at System.Configuration.ConfigurationManager.RefreshSection(String
sectionName)
at System.Configuration.ClientSettingsStore.ReadSettings(String
sectionName, Boolean isUserScoped)
at
System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext
context, SettingsPropertyCollection properties)
at
System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider
provider)
at System.Configuration.SettingsBase.GetPropertyValueByName(String
propertyName)
at System.Configuration.SettingsBase.get_Item(String propertyName)
at System.Configuration.ApplicationSettingsBase.GetPropertyValue(String
propertyName)
at System.Configuration.ApplicationSettingsBase.get_Item(String
propertyName)
at VistaArrowGone.Properties.Settings.get_Arrow()
at VistaArrowGone.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase:
file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
FxVisor
Assembly Version: 2.0.0.0
Win32 Version: 2.0.0.0
CodeBase:
file:///C:/Program%20Files/Frameworkx/Vista%20Shortcut%20Manager/FxVisor.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
========= Appendix Ends ==========



__________ Information from ESET Smart Security, version of virus signature database 4166 (20090618) __________

The message was checked by ESET Smart Security.

http://www.eset.com

 

[DL]

Run MS Update, install any Net framework offered, yes you need multiple
versions as an app may be version specific
No swap file?

 

[William Yanaire, ESQ]

no swap file due to 4GB this guy thought it's OK, but I dont think. I
think he needs a swap file

You are 100% right. You don't think.

IDIOT

 

[Mike]

< but I dont think.

We know, dammit! We know!

 

[JEWboy]

no swap file due to 4GB this guy thought it's OK, but I dont think. I think
he needs a swap file

 

[Doug]

Thanks, DL, for explaining that it is normal to run multiple versions of
..NET.

No swap file? - I only mentioned it in case it might affect the .NET issue.

Off topic, when I took my box in to the manufacturer to have an extra 2GB
fitted to make 4GB, I was surprised when I got it home to find the
technician had removed the swap file. After trying it with a fixed swap file
of around 9GB and reading up about it, I decided that opinion was evenly
divided and that he was probably right. The space is welcome, the disc
thrashing reduced, everything seems faster, and PerfectDisk has less
defragging to do.

Doug

Run MS Update, install any Net framework offered, yes you need multiple
versions as an app may be version specific
No swap file?

__________ Information from ESET Smart Security, version of virus signature database 4168 (20090618) __________

The message was checked by ESET Smart Security.

http://www.eset.com

 

[Ken Blake, MVP]

Off topic, when I took my box in to the manufacturer to have an extra 2GB
fitted to make 4GB, I was surprised when I got it home to find the
technician had removed the swap file. After trying it with a fixed swap file
of around 9GB and reading up about it, I decided that opinion was evenly
divided and that he was probably right.

He was not right.

The space is welcome, the disc
thrashing reduced, everything seems faster, and PerfectDisk has less
defragging to do.

There's no reason to have a fixed size. There's no advantage to not
having a page file, and often a disadvantage.

1. If you don't have a page file, you can't use all the RAM you have.
That's because Windows preallocates virtual memory in anticipation of
a possible need for it, even though that allocated virtual memory may
never be used. Without a page file, that allocation has to be made in
real memory, thus tying up that memory and preventing it from being
used for any purpose.

2. There is never a benefit in not having a page file. If it isn't
needed, it won't be used. Don't confuse allocated memory with used
memory.

 

[Doug]

He was not right.


There's no reason to have a fixed size. There's no advantage to not
having a page file, and often a disadvantage.

1. If you don't have a page file, you can't use all the RAM you have.
That's because Windows preallocates virtual memory in anticipation of
a possible need for it, even though that allocated virtual memory may
never be used. Without a page file, that allocation has to be made in
real memory, thus tying up that memory and preventing it from being
used for any purpose.

2. There is never a benefit in not having a page file. If it isn't
needed, it won't be used. Don't confuse allocated memory with used
memory.

Thanks, Ken, I shall certainly give this further attention.
Doug


__________ Information from ESET Smart Security, version of virus signature database 4169 (20090619) __________

The message was checked by ESET Smart Security.

http://www.eset.com

 

[Ken Blake, MVP]

Thanks, Ken, I shall certainly give this further attention.

You're welcome. Glad to help.