Depending on your emulation, I am guessing that key is bound to project-build command and that would only build current active project (and dependencies). There is a Build Solution for Visual Studio projects, but not bound to that command. There is no SlickEdit equivalent for building an entire workspace, so that is only available as an extra tool for Visual Studio projects. You can record a macro calling Build Solution, and then bind the build key to the recorded macro. Though if you replace the key-binding for project-build with the custom macro, then you will have issues using that macro command with SlickEdit projects as there is not a supported build tool.
