visual studio - Assembly lands in bin with Build Action: None and Output Directory: Do not copy -
the question assembly properties.
build action: none copy output directory: not copy oddly, these settings still land assemblies in bin. i've read answer question: what various "build action" settings in visual studio project properties , do? seems these shouldn't landing in bin.
- why these landing in bin?
- is expected behavior settings?
- if isn't expected behavior, settings more appropriate?
scenario: we're deploying sql server ce entity framework windows azure web app.
after running install-package entityframework.sqlservercompact, our csproj has _bin_deployableassemblies directory. directory contains bunch of assemblies azure web app requires (we don't need them locally if sql server ce installed.)
when build csproj, of assemblies end in bin. good.
images
assembly properties
build results
i wrong, think if msbuild detects dependency on dll include in output regardless of setting, if 1 of things are copying output folder has such dependency you'll 1 also. check build messages "including blahblah.dll..." (the exact wording escapes me now).
perhaps list in referenced libraries project?
fwiw, use post-build step handle things this.