D
darrel
What does that MEAN?
I'm working on a VS project with another person. We keep our DLLs and files
in sync with each other. Last week I hit a snag where i kept getting the
'could not load type' error with one of my usercontrols. The other person
can take my exact same files, compile it into his copy, and it works fine.
So, I deleted everything I had, reimported all of his files, and things were
working again on my localhost.
However, I can not change any of the VB code of the one particular
usercontrol and have VS.net compile it. It seems to ignore my changes and
goes on using the DLL I got from the other person. If I delete said DLL in
hopes of forcing a rebuild, I'm back to getting the 'Could not load type'
error again.
AAAAAARRRRRRRRRRRRRRRRRRRRRRRRGGGGGGGGGGGGGGHHHHHHHHHHHHHHHHHHHHHH!
Any idea? I've looked online and found that this seems to be a really genric
error and to just keep trying rebuilding/resetting things until it works.
I'm getting nowhere with this.
-Darrel
I'm working on a VS project with another person. We keep our DLLs and files
in sync with each other. Last week I hit a snag where i kept getting the
'could not load type' error with one of my usercontrols. The other person
can take my exact same files, compile it into his copy, and it works fine.
So, I deleted everything I had, reimported all of his files, and things were
working again on my localhost.
However, I can not change any of the VB code of the one particular
usercontrol and have VS.net compile it. It seems to ignore my changes and
goes on using the DLL I got from the other person. If I delete said DLL in
hopes of forcing a rebuild, I'm back to getting the 'Could not load type'
error again.
AAAAAARRRRRRRRRRRRRRRRRRRRRRRRGGGGGGGGGGGGGGHHHHHHHHHHHHHHHHHHHHHH!
Any idea? I've looked online and found that this seems to be a really genric
error and to just keep trying rebuilding/resetting things until it works.
I'm getting nowhere with this.
-Darrel