build - Building a project changes another project's bin folder in a Visual Studio Solution -

i've dozens of web applications , lots of class libraries in solution. when build web application, let's "a", web application project, let's "b", affected compiling. "a" , "b" not referenced directly, uses same class libraries. if build or rebuild "a", created assemblies build goes "b"'s bin folder, too. so, everytime build "a", i'm waiting startup of "b". far know, there isn't hardlink/symlink between these bin folders of projects.

also, i'm using common output path class libraries, not web applications.

is bug or default behavior? how can prevent behavior?

is bug or default behavior? how can prevent behavior?

this default behavior. add project reference visual studio web project, following added web project's bin folder:

• a copy of assembly created added project.
• copies of dependent assemblies, xml document files, license files, resource files, , on.

so once add library project web, assembly added project automatically add web project`s bin folder.

if want prevent behavior, can pack class libraries nuget package, add package web project , b. can refer this document more info nuget create package.