Kevin,

>I guess that since rebuilding the DLL means the build number for the DLL gets incremented...and the winform no longer 'recognizes' it.>

This is why you have broken references. The version number must match. You most likely have the AssemblyVersionAttribute class in the AssemblyInfo file set to "1.0.*". Everytime you recompile, the version is changing. In your WinForm applications, you now need to recompile using the new version.

When you recompile, a new version is copied to your application since you chose to Copy Local.

>This is a basic question about DLLs, references, etc.
>
>Let's say I have a basic WinForm, and an 'external' DLL [say, a basic MOVER container dialog]. I create the MOVER and compile it as a separate project/DLL. The Winform has a reference to it.
>
>If I go and make a change to the MOVER DLL and compile/rebuild the DLL, it seems [at least the way I've set up my project] that I have to go recompile the Winform as well. This doesn't make much sense...but it may be because I've set the reference incorrectly.
>
>[I don't know if this is relevant, but in my reference, I have the property COPY LOCAL set to TRUE]. If I set that to FALSE, it doesn't work at all.
>
>I have the same general question if the external DLL is a business logic library that has no UI presence. It seems that everytime I make a change to the DLL, I need to rebuild my Winform project, or else I have a 'broken reference'. I guess that since rebuilding the DLL means the build number for the DLL gets incremented...and the winform no longer 'recognizes' it.
>
>Again, I may be doing a bunch of things wrong...can someone steer me in the right path?
>
>Thanks,
>Kevin