W
WyomingDoug
Guest
This problem is a unique SGEN issue with .NET 4, full profile.
It initially reared it head on a client machine. We have an application, DLT, that uses COM interop to access some legacy component. Recently we had to modify the application to add support for a few new features a customer had requested. The required adding a new DLL to provide supportfr the new functionality.
The program uses XML serilization to record configuration information.
The program program works fine on the development system (of course!)
On target machine it would hand the program. Further invegtigation (yea procdump!) revealed that when the XML serialization was occuring it was crashing on receiving an exception.
The exception being thrown was "The type xxx is defined in an assembly that is not referenced. You must add a reference to assembly yyy."
Ok straight forward enough must have forgotten to refeence the new DLL which is assembly yyy.
Went and checked the references, and the proper item is referenced. Knowing the .NET can give misleading error message for types that are used in modules I checked to make sure that the main ap also referened all the DLLs referenced by the yyy assembly. They were all referenced too.
So Im left scracting my head.
Aftr a bit of monkeying around I decided to use SGEN to generate the serialization assembly for the main EXE. This now has the build failing with SGEN returning the same error message about assembly yyy.
Which is greta I can see the problem now on the devleopment machine. Unfortunately the specified module is already refereced in the main app (and so are its dependant assemblies)
Im at a loss as to what to try. Ive rebuilt from scratch refeenced the new DLLs XML serialization assembly from main the executable.
Nothing seems to resolve the issue.
Anyone have any tips?
Continue reading...
It initially reared it head on a client machine. We have an application, DLT, that uses COM interop to access some legacy component. Recently we had to modify the application to add support for a few new features a customer had requested. The required adding a new DLL to provide supportfr the new functionality.
The program uses XML serilization to record configuration information.
The program program works fine on the development system (of course!)
On target machine it would hand the program. Further invegtigation (yea procdump!) revealed that when the XML serialization was occuring it was crashing on receiving an exception.
The exception being thrown was "The type xxx is defined in an assembly that is not referenced. You must add a reference to assembly yyy."
Ok straight forward enough must have forgotten to refeence the new DLL which is assembly yyy.
Went and checked the references, and the proper item is referenced. Knowing the .NET can give misleading error message for types that are used in modules I checked to make sure that the main ap also referened all the DLLs referenced by the yyy assembly. They were all referenced too.
So Im left scracting my head.
Aftr a bit of monkeying around I decided to use SGEN to generate the serialization assembly for the main EXE. This now has the build failing with SGEN returning the same error message about assembly yyy.
Which is greta I can see the problem now on the devleopment machine. Unfortunately the specified module is already refereced in the main app (and so are its dependant assemblies)
Im at a loss as to what to try. Ive rebuilt from scratch refeenced the new DLLs XML serialization assembly from main the executable.
Nothing seems to resolve the issue.
Anyone have any tips?
Continue reading...