{"push_id":1205331003,"size":1,"distinct_size":1,"ref":"refs/heads/EXSRV003","head":"005f05f7c6def1ee7ef4e42d59a0e00bb2107f3f","before":"1292900da9432f9638822f04784059f6a59e3fe1","commits":[{"sha":"005f05f7c6def1ee7ef4e42d59a0e00bb2107f3f","author":{"name":"mnivens","email":"b63fca6af16cae3a01223af6ac86d1c978a3dfa1@microsoft.com"},"message":"Update to .NET framework detection\n\nI offloaded the .NET registry build to friendly build mapping to an XML\nfile (FrameworkBuildMapping.xml) and did the same for the support matrix\n(DotNetSupportMatrix.xml).  I refactored the test to pull the server\nversion installed as well as the registry info and compare to the xml\ncontents to report on whether or not the .NET version installed is A)\nsupported, and b) recommended.  Going forward we should only have to\nmake changes to the XML files when a new support matrix or .NET build\ngets released.  The only exception would be a new minor build of\nexchange, which would be a new version all together.","distinct":true,"url":"https://api.github.com/repos/ExchangeAnalyzer/ExchangeAnalyzer/commits/005f05f7c6def1ee7ef4e42d59a0e00bb2107f3f"}]}
{"actor":{"display_login":"mnivens"}}