Problems with assemblies
-
Ok, here's the deal - I have two assemblies in a project along with a tester application. The tester application is dependant on (and references) both assemblies, but neither of the assemblies reference each other. I have set up the dependancies and references for the tester app in VS.NET (including setting the references to the assemblies to copy the referenced assemblies local). When i launch the tester application, i get a IO SystemException saying that one of the dll's or its dependancies can't be found, yet if i open explorer and look in the bin\debug folder, i can see both of the assembly dll's along with the tester executable. Any help? This is very frustrating. Thanks!
-
Ok, here's the deal - I have two assemblies in a project along with a tester application. The tester application is dependant on (and references) both assemblies, but neither of the assemblies reference each other. I have set up the dependancies and references for the tester app in VS.NET (including setting the references to the assemblies to copy the referenced assemblies local). When i launch the tester application, i get a IO SystemException saying that one of the dll's or its dependancies can't be found, yet if i open explorer and look in the bin\debug folder, i can see both of the assembly dll's along with the tester executable. Any help? This is very frustrating. Thanks!
the_grip wrote: When i launch the tester application, i get a IO SystemException saying that one of the dll's or its dependancies can't be found, yet if i open explorer and look in the bin\debug folder, i can see both of the assembly dll's along with the tester executable. One or both of the assemblies probably has a dependancy on another assembly that is not in the progrm directory or the GAC. Who is this miscrosoft, and what devilish plans have they for us?
-
the_grip wrote: When i launch the tester application, i get a IO SystemException saying that one of the dll's or its dependancies can't be found, yet if i open explorer and look in the bin\debug folder, i can see both of the assembly dll's along with the tester executable. One or both of the assemblies probably has a dependancy on another assembly that is not in the progrm directory or the GAC. Who is this miscrosoft, and what devilish plans have they for us?
That's what i initially thought, however, they only reference the base assemblies (System, etc.). There are no custom references defined that these are dependant on. Surely I don't have to copy these dlls... that should be in the environment path... or do i need to set these to copy local? i should note that i had this problem once before... i had to strong name my assemblies and add them to the GAC before it would work. This was a few weeks ago, and i dumped that solution. Every time i rebuilt the assemblies i would have to reregister them in the GAC. Surely there is a better solution (i can't imagine having to do this just to test assemblies)?
-
That's what i initially thought, however, they only reference the base assemblies (System, etc.). There are no custom references defined that these are dependant on. Surely I don't have to copy these dlls... that should be in the environment path... or do i need to set these to copy local? i should note that i had this problem once before... i had to strong name my assemblies and add them to the GAC before it would work. This was a few weeks ago, and i dumped that solution. Every time i rebuilt the assemblies i would have to reregister them in the GAC. Surely there is a better solution (i can't imagine having to do this just to test assemblies)?
-
Weird. I would suggest using Reflector .NET , it will popup a dialog for the needed assemblies when laoding an assembly. http://www.aisto.com/roeder/dotnet[^] Who is this miscrosoft, and what devilish plans have they for us?
Thx leppie... i downloaded all those proggies off that page... good stuff. i DID manage to finally find my problem. i was referencing the debug dll's for the assemblies (wrong), co i changed it to reference the assembly projects (right). i could have used the release dll's i guess, but this way solved my problem. Oh well - there's another hour or two down the tubes on stupid troubleshooting errors :) Thanks again for the help.
-
Thx leppie... i downloaded all those proggies off that page... good stuff. i DID manage to finally find my problem. i was referencing the debug dll's for the assemblies (wrong), co i changed it to reference the assembly projects (right). i could have used the release dll's i guess, but this way solved my problem. Oh well - there's another hour or two down the tubes on stupid troubleshooting errors :) Thanks again for the help.
the_grip wrote: Oh well - there's another hour or two down the tubes on stupid troubleshooting errors I had a problem the other day, that each time i was compiling an assembly it was adding a reference to a then removed reference , eventually 20000 builds later it leaved me alone. ;) Who is this miscrosoft, and what devilish plans have they for us?