Protecting projects from accidental rebuilds

[las]

....Working with VS .Net 2003...

I have a solution that includes several projects: A core application,
several plug-in driver DLL's and a class library.

I want to make sure the Class Library project never gets rebuilt
accidentally. Aside from moving it out to its own Solution, is there
any way to lock it down to prevent a rebuild?

Or perhaps, is there a way to make .Net less sensitive to rebuilds of
the class library?

Background:
The class library contains an Interface that is Implemented by the
plug-in driver DLL's so that they are decoupled from the core
application -- this allows me to rebuild and redistribute any single
component (the core application or a driver DLL) without having to
rebuild and redistribute all components.

Of course, if I change the Interface that all the drivers Implement, I
must rebuild and redistribute everything. Fair enough.

Unfortunately, there seem to be too many ways for this class library to
be rebuilt when it does not need to be. I can remove dependencies to
prevent VS from automatically rebuilding the library when rebuilding
another component, but I wonder if there are other automatic mechanisms
I don't know about, and of course it is always possible to a developer
to slip and click Build Solution instead of Build Project, causing a
real mess to clean up.

Is the safest fix just to move the class library to its own VS
Solution?

Thanks for any ideas!

Lee