Author Topic: Beta5: VS2010 purpose of build command  (Read 2004 times)


  • Senior Community Member
  • Posts: 261
  • Hero Points: 26
Beta5: VS2010 purpose of build command
« on: September 17, 2014, 01:44:06 AM »
I have a C# solution with a lot of (VS) projects. When modifying files under one or more of these projects, Build (Ctrl-m) never compiles those projects. I need to either build the entire solution, or specifically select and build the modified project csproj. Am I misinterpreting the purpose of 'build' for VS workspaces?


  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1299
  • Hero Points: 130
Re: Beta5: VS2010 purpose of build command
« Reply #1 on: September 17, 2014, 02:09:15 PM »
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.
« Last Edit: September 17, 2014, 03:43:14 PM by Lee »