Generate a VisualStudio solution more compatible with VisualStudio
- Use tabs and windows newlines
- Fix the definition of configurations
Create all VisualStudio projects as 'Makefile' projects
- Remove any attempt to create a functional native Visual Studio project
- Use gradle as 'Makefile' engine for project building
Simplify mapping of Gradle components to Visual Studio projects
- Each executable component maps to a single Exe VS project
- Each library component maps to a Dll and Lib VS project
- All sources for every binary for component are included in VS project
- Flavor and platform contribute to configuration name if multiple are defined for component
    - This means that the 'configuration' portion of a VS configuration is unique in a project
Map all VisualStudio configurations as "Win32"
- This prevents VisualStudio from generating duplicate configurations on first open
- We might find a more sophisticated mapping in the future
VS Project contains sources for any binary included in project
Generate the full set of configurations for a VisualStudio solution
- Solution is now generated for a VSProject, rather than a specific binary
VisualStudio configuration names match binary names
Fix building with VisualStudio
- Use 'gradle' instead of 'gradlew.bat' as build tool
- Include full path to binary lifecycle task
Better support for VS executing Gradle for building
- detect and use the wrapper if present
- allow the gradle command to be configured
Use relative paths in generated VS files where possible:
- Include '-p' argument to force grade to run from the rootDir
Better support for building in VS
- Don't create inter-project references
- Only the primary project should build when the solution builds
Enable debugging from within VisualStudio
- Build using the InstallExecutable task
- Use the install directory as output