Hi!
When I try to load a .NET v1.1 assembly dll in VS2005 I get an error message
"MyAssembly.dll" is not a Microsoft .NET module.
Are all v1.1 .NET framework assemblies inaccessible from VS.NET 2005
Is there a way to get a more detailed error description about
why the load fails
Thanks!
Atmapuri
Loading .NET v1.1 assembly in VS2005
Hot Topic
- Manipulating Excel spreadsheet with ASP.net
- BinaryReader.ReadBytes()
- adding application path in dill import c#
- Named Pipes in C#
- Discard changes made to datatable columns of a Dataset?
- Parent-Child Table Updation Problem
- Passing a ascii byte array as System.String to a COM BSTR param
- Problem with AutoNumber key column
- WMI methods
- Please Help!!
.NET Development
- TCPIP Messages Bunching Up! Any help appreciated.
- Type.GetType(string typeName) not working for my classes
- Change DOCTYPE without loading XML in C++
- how to use \r,\n in the xml
- Problem with Thread and COM object
- Print file using Microsoft Office Document Image Writer
- MultiThreading Question
- Static object instantiated multiple times
- Import from excel file
- XmlNode in Generated Typed Class
Loading .NET v1.1 assembly in VS2005
Tim Roddick
Actually, compiled libraries do seem to work. The error message was due to a part
of the code that was included in the assembly. After adding source files
one by one, I found the culprit. I also used PEVerify to check for anything
that the new framework does not like.
Regardless, It seems rather unprobable that libraries compiled
against v1.1 .NET framework will work as-is. You will need to have the source
and do some tweaking even if there is no framework incompatibility.
If nothing else, PEVerify would be failing almost certainly. So, you can ensure
that an assembly compiled against v1.1 will work in VS2005 also,
but cant expect that it will work instantly. Therefore, if you have bought
third party libraries, you will need an update in 99% of cases.
Regards!
Atmapuri
firebalrog
So, this means that all v1.1 assemblies will have to be recompiled, and packages and software bought for VS 2003.NET will need to recieve an upgrade
(sounds pretty expensive to me
I have VS.2003 and v1.1 framework on the same computer. I noticed
that there are some portability issues mentioned by the docs. Do they
refer to source code only And binaries compiled against v1.1 framework
absolutely can not be used with applications developed in VS2005
Thanks!
Atmapuri.
Ian Sugar
05 is not backwards compatible with the 1.1 framework....you will have to upgrade the assembly to open in 05
Ronald_D_Craig
If somebody out there from MS nows any diff....speak-up