Inexplicable errors on forms.
-
I've got a rather odd problem which I can't fix, and can't find any information about on the Microsoft sites, so maybe some saged person here can help. In summary, I am referencing a home grown .DLL in my project. The .DLL is relatively simple, it just accesses some legacy BTree files. However with the reference in place, loading up one of the existing forms in the project the form doesn't load - in it's place is a screen saying:
An error occurred while loading the document. Fix the error, and then try loading the document again. The error message follows: File or assembly name EPoSAccessLayer.dll, or one of it's dependencies, was not found.I have confirmed that all dependencies are found, and in a brand new project the .DLL does not cause these problems. In the existing project where this reference is causing the form problems, the application will compile and execute without errors. I just can't edit the forms. My current workaround is to remove the reference, and then the forms load up and are OK for editing. So the question is, has anyone else experienced this problem, and if so, do you know the solution for it. Thanks. Martin. -
I've got a rather odd problem which I can't fix, and can't find any information about on the Microsoft sites, so maybe some saged person here can help. In summary, I am referencing a home grown .DLL in my project. The .DLL is relatively simple, it just accesses some legacy BTree files. However with the reference in place, loading up one of the existing forms in the project the form doesn't load - in it's place is a screen saying:
An error occurred while loading the document. Fix the error, and then try loading the document again. The error message follows: File or assembly name EPoSAccessLayer.dll, or one of it's dependencies, was not found.I have confirmed that all dependencies are found, and in a brand new project the .DLL does not cause these problems. In the existing project where this reference is causing the form problems, the application will compile and execute without errors. I just can't edit the forms. My current workaround is to remove the reference, and then the forms load up and are OK for editing. So the question is, has anyone else experienced this problem, and if so, do you know the solution for it. Thanks. Martin.Sometimes I found those error too, What I did.. just try saving the form.. restart the IDE and reopen again. Mostly it's work.. Sorry I can't help you with other solution :) "Courage choose who will follow, Fate choose who will lead" - Lord Gunner, Septerra Core "Press any key to continue, where's the ANY key ?" - Homer Simpsons Drinking gives me amazing powers of insight. I can solve all the worlds problems when drunk, but can never remember the solutions in the morning. - Michael P Butler to Paul Watson on 12/08/03
-
I've got a rather odd problem which I can't fix, and can't find any information about on the Microsoft sites, so maybe some saged person here can help. In summary, I am referencing a home grown .DLL in my project. The .DLL is relatively simple, it just accesses some legacy BTree files. However with the reference in place, loading up one of the existing forms in the project the form doesn't load - in it's place is a screen saying:
An error occurred while loading the document. Fix the error, and then try loading the document again. The error message follows: File or assembly name EPoSAccessLayer.dll, or one of it's dependencies, was not found.I have confirmed that all dependencies are found, and in a brand new project the .DLL does not cause these problems. In the existing project where this reference is causing the form problems, the application will compile and execute without errors. I just can't edit the forms. My current workaround is to remove the reference, and then the forms load up and are OK for editing. So the question is, has anyone else experienced this problem, and if so, do you know the solution for it. Thanks. Martin.If the assembly EPoSAccessLayer.dll is from a project in your solution, I recommend you add a Project reference to your project that depends on it (same as adding a .NET or COM reference, only click on the Project tab). This keeps both Debug, Release, or any other build configurations in sync when building. It also makes sure that any changes to the EPoSAccessLayer project force a recompilation of it before compiling your project with a dependency on it. If you're using automatic versioning, this problem seems common and using a project reference should help.
-----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----
-
I've got a rather odd problem which I can't fix, and can't find any information about on the Microsoft sites, so maybe some saged person here can help. In summary, I am referencing a home grown .DLL in my project. The .DLL is relatively simple, it just accesses some legacy BTree files. However with the reference in place, loading up one of the existing forms in the project the form doesn't load - in it's place is a screen saying:
An error occurred while loading the document. Fix the error, and then try loading the document again. The error message follows: File or assembly name EPoSAccessLayer.dll, or one of it's dependencies, was not found.I have confirmed that all dependencies are found, and in a brand new project the .DLL does not cause these problems. In the existing project where this reference is causing the form problems, the application will compile and execute without errors. I just can't edit the forms. My current workaround is to remove the reference, and then the forms load up and are OK for editing. So the question is, has anyone else experienced this problem, and if so, do you know the solution for it. Thanks. Martin.This problem occurs also when you are using inherited forms. Forms inherited from forms in your own project usually don't cause much trouble. But I have never been able to inherit a form from another (library) project... the program worked just fine - like yours - but the designer wouldn't work... A bug in VS.NET ... Anybody knowing how to fix this inheriting problem?? greetz ;-) *Niels Penneman*
Software/Dev Site
Personal Site
-
If the assembly EPoSAccessLayer.dll is from a project in your solution, I recommend you add a Project reference to your project that depends on it (same as adding a .NET or COM reference, only click on the Project tab). This keeps both Debug, Release, or any other build configurations in sync when building. It also makes sure that any changes to the EPoSAccessLayer project force a recompilation of it before compiling your project with a dependency on it. If you're using automatic versioning, this problem seems common and using a project reference should help.
-----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----
I wasn't orginally using a project reference, just a normal binary reference. But that does seem to have fixed it. Thanks.