Final answer:
Creating a Visual Studio project outside the webroot enhances solution portability, simplifies source control file management, but does not intrinsically affect build speeds or eliminate code deployment needs.
Step-by-step explanation:
Creating the Visual Studio project outside the webroot is often recommended for several reasons. Firstly, solution portability is improved because the project can be moved and set up on a different server or environment without being tied to the specific structure of a particular web server's directory. Moreover, this approach is not necessarily required for source control usage, but it does make managing project files easier, especially when working in a team. Fast builds are advantageous, but the location of the project relative to the webroot does not inherently determine build speed; so the build process may not be necessarily faster outside of the webroot. Lastly, separating the project from the webroot doesn't eliminate the need to deploy code changes; regardless of where the development occurs, changes must still be deployed to the live server environment.