On a new system I loaded Microsoft .NET Framework 2.0, now some of my applications need Microsoft .NET Framework 1.1. Of which I can not load, even after unloading 2.0. Using XP Pro SP2. Any Suggestions
.Net 2.0 loaded 1.1 needed
Hot Topic
- ADO.net and Excel
- stack overflow and memory corrupt when use DsBrowseContainer
- how to open excel file (on server), write some value to it and save it in ASP.Net
- get data from access and save it into a new excel file using vb 2005
- Strange Memory Leak...
- Problem | Oracle 9i Release + With Vb.Net 2005
- How to veto suspend and shutdown request using C#?
- String.Compare with Unicode characters
- deploy and manifest file?
- ResourcePool problem
.NET Development
- SOAP Attachments - c# and java
- ActiveX controls in server objects - Is this possible?
- Delegate Keep alive
- C# Lookup Local & Network Servers (Oracle & MySQL)
- How to access COM+ remotely using .NET Remoting?
- Strange behavior when making remote call
- Create Message Queue
- StreamWriter, limited File Size?
- Is there anyway to force web services to deserialize request message without checking soap namespace?
- UDP example code not working
.Net 2.0 loaded 1.1 needed
maest
Ordinarily a .NET application will try to run by the same framework version as it was compiled for (provided no overrides exist) and it is strange that installing the 2.0 Framework caused your 1.1 apps to try to run in 2.0 and stop working.
Have you tried reinstalling/repairing the 1.1 Framework
Also worth noting is that when you have multiple versions of the framework installed and you absolutely want to have control over the framework that your app runs in (provided it is installed) you can modify the apps config file with an XML block like this:
<configuration>
<startup>
<supportedRuntime version="v1.1.4322" />
</startup>
</configuration>
Above we are telling the system that when our app loads, we want it to be run by the 1.1 Framework.
Barry Kwok
You must have at least one component that references the 1.1 BCL.
You can find out by running ildasm, opening your assembly(s), and examining the 'MANIFEST' section of the output.
Sean