...
Alternatively you can start up a solution file from within GoGui. Select the root directory. Then, in the bottom navigator pane, navigate to the subdirectory with a name like studio\Window-i386-32bit-vc90-Debug. You can start up VS by right-clicking on any solution file and selecting the Studio 
menu item.
Known issues
Installing headers
VS project files do not have the same level of granularity that SCons does in handling the installation of header files. SCons parses C++ source to compute dependencies on headers and will automatically install any header needed to compile an object it is trying to build. As far as I can tell, VS project files do not natively support the idea of installing files. The approach I took was to generate a .bat file for each package which installs files (headers, job options, xml, etc.) belonging to that package, then invoke it in a project file belonging to that package. Usually it's the same project file that builds the package's library. If the package doesn't build a library, there is an extra VS project file which does nothing but invoke the .bat file. However, there is no easy way to determine dependencies and build order among these project files.
I think that most scenarios of modifying headers from within Studio will be handled correctly, but this needs to be tested. The intent is that developers modify the original (within the package) copy of the header,job options file or what have you, and the build process should install it.