1. 16 Aug, 2014 1 commit
  2. 10 Aug, 2014 2 commits
  3. 01 Aug, 2014 1 commit
  4. 31 Jul, 2014 1 commit
  5. 30 Jul, 2014 2 commits
  6. 29 Jul, 2014 3 commits
  7. 28 Jul, 2014 1 commit
  8. 26 Jul, 2014 3 commits
  9. 25 Jul, 2014 2 commits
  10. 24 Jul, 2014 1 commit
  11. 23 Jul, 2014 3 commits
  12. 14 Jul, 2014 1 commit
  13. 11 Jul, 2014 1 commit
  14. 01 Jul, 2014 2 commits
    • Chun-wei Fan's avatar
      MSVC 2012/2013 Support: Update Property Sheet Creation · fe66e7b3
      Chun-wei Fan authored
      Be a bit more carful when copying and updating the property sheets, so that
      we don't accidently change fields with '10' in them that are actually not
      indicating the Visual Studio version.
      fe66e7b3
    • Chun-wei Fan's avatar
      Build: Provide Simple Support for MSVC 2012/2013 · e895f9e5
      Chun-wei Fan authored
      As the Visual Studio 2012/2013 are only slightly different from the Visual
      Studio 2010 projects, we can provide support for them by using scripts to
      copy the Visual Studio 2010 projects, and update the specific parts as
      necessary.  Thus, there would be little maintenance overhead for these as
      only the 2010 projects need to be kept up-to-date as a result.
      
      This might change when we do get the stack working with WinRT/Metro, but
      that's going to be another totally different issue.
      e895f9e5
  15. 27 Jun, 2014 1 commit
  16. 24 Jun, 2014 4 commits
  17. 23 Jun, 2014 2 commits
  18. 20 Jun, 2014 3 commits
  19. 10 Jun, 2014 1 commit
  20. 09 Jun, 2014 1 commit
    • Chun-wei Fan's avatar
      MSVC 2010+ Projects: Update "Installation" Process · 809246a6
      Chun-wei Fan authored
      Currently, due to the way that Visual Studio 2010+ projects are handled,
      the "install" project does not re-build upon changes to the sources, as it
      does not believe that its dependencies have changed, although the changed
      sources are automatically recompiled.  This means that if a part or more
      of the solution does not build, or if the sources need some other fixes
      or enhancements, the up-to-date build is not copied automatically, which
      can be misleading.
      
      Improve on the situation by forcing the "install" project to trigger its
      rebuild, so that the updated binaries can be copied.  This does trigger an
      MSBuild warning, but having that warning is way better than not having an
      up-to-date build, especially during testing and development.
      809246a6
  21. 31 May, 2014 1 commit
  22. 08 May, 2014 2 commits
  23. 10 Apr, 2014 1 commit