Hi,
I have a solution which unfortunately contains 12 projects - all of which have dependencies on each other in some shape or form.
Ever since using .NET, I've experienced nothing but the above error message. I've checked all the dependencies and cannot fathom it out. I also get warnings about the dependency not able to be copied to the run directory.
I set references to other "projects" as opposed to the "dll" as the bible says.
Whenever I add a reference, when you look in the path property it is referenced through the \obj\debug path sometimes, other times through the correct path i.e. \bin.
Sometimes when the solution loads there is no GUI on the class, just a plain VB class.
Does anyone know of any documents out there that talk plain about what actually goes on, how to set references, how to set the configuration manager and so forth? This is destroying confidence so much I'd sooner go right back to basics and start again with a clear mind?
Many thanks,
Glyn.
I have a solution which unfortunately contains 12 projects - all of which have dependencies on each other in some shape or form.
Ever since using .NET, I've experienced nothing but the above error message. I've checked all the dependencies and cannot fathom it out. I also get warnings about the dependency not able to be copied to the run directory.
I set references to other "projects" as opposed to the "dll" as the bible says.
Whenever I add a reference, when you look in the path property it is referenced through the \obj\debug path sometimes, other times through the correct path i.e. \bin.
Sometimes when the solution loads there is no GUI on the class, just a plain VB class.
Does anyone know of any documents out there that talk plain about what actually goes on, how to set references, how to set the configuration manager and so forth? This is destroying confidence so much I'd sooner go right back to basics and start again with a clear mind?
Many thanks,
Glyn.
