Jul 7, 2010 at 7:50 PM
Edited Jul 7, 2010 at 7:50 PM
I have SHFB's Documentation Sources node pointed to a solution which contains 25 project files, one of which I do not wish to have documentation generated for (unit tests). In the release build for this solution, that project file is not built.
When I attempt to generate output from SHFB for the release build, i get this error.
"SHFB: Error BE0040: Project assembly does not exist: C:\Projects\blahblah\bin\Release\AssemblyIWantToExclude.dll"
Does SHFB not honor the build configurations set in the solution?
This discussion says it will be in the "next build"...
Was that implemented but has some bugs?
I attempted to exclude that namespace through the apifilter and was successful in setting that up (i had to build the debug version in SHFB before it would let me open the apifilter dialog), however SHFB still errors out expecting to find the dll in the