1. 26 10月, 2016 4 次提交
  2. 25 10月, 2016 12 次提交
  3. 24 10月, 2016 1 次提交
    • J
      Compiler server should be tolerant of corrupted application settings · 74363cfc
      Jared Parsons 提交于
      When a machine.config or app.config is corrupted it's possible for `ConfigurationManager.AppSettings` to throw an exception.  The compiler server was not tolerant of such a failure and as a result would terminate immediately after startup.
      
      The compiler workflow is generally very tolerant of failures in the server.  It is an optimization only, and any crashes, bad results, etc ... are ignored and the workflow will fall back to the command line.  Failing on startup is one case the workflow does not handle well right now.  The workflow does not distinguish between a crash at startup and a very slow JIT situation (as is the case with old, single core machines).  As such it ends up adding an unnecessary 25 second delay to the compilation.  Issue #14265 tracks fixing this delay but it won't make RC.
      
      Up until now only one incident of corrupted app settings was reported and it was considered an extremely unlikely problem (as it would break a lot of apps).  Going through VS feedback last night I found one other incident which could would be explained by this problem.  Hence it's possible this is more likley than originally thought (although still very rare) and decided to put it into RC.
      
      closes #14288
      74363cfc
  4. 23 10月, 2016 1 次提交
  5. 22 10月, 2016 5 次提交
  6. 21 10月, 2016 16 次提交
  7. 20 10月, 2016 1 次提交