1. 16 11月, 2016 1 次提交
  2. 15 11月, 2016 2 次提交
    • D
      Localize "Error"/"Warning" etc. in the code style UIs · 46d64f7a
      David Poeschl 提交于
      Fixes part 2 of #9674 for both the general code style page and the
      naming style option page.
      
      This also removes the superfluous "EnforcementLevel" class in the
      NamingPreferences namespace that was basically a duplication of
      "NotificationOption"/"NotificationOptionViewModel" in the general
      CodeStyle namespace.
      46d64f7a
    • D
      Localize strings in DataGrid headers · d9d352aa
      David Poeschl 提交于
      Fixes #12669. Addresses one part of #9674
      
      Fixes both the general code styles page and the naming styles page
      d9d352aa
  3. 25 10月, 2016 1 次提交
  4. 21 10月, 2016 1 次提交
  5. 20 10月, 2016 2 次提交
  6. 10 9月, 2016 2 次提交
  7. 20 7月, 2016 1 次提交
  8. 12 7月, 2016 1 次提交
  9. 09 7月, 2016 1 次提交
  10. 24 6月, 2016 1 次提交
  11. 16 6月, 2016 1 次提交
  12. 15 6月, 2016 3 次提交
  13. 11 6月, 2016 1 次提交
  14. 26 5月, 2016 1 次提交
  15. 21 5月, 2016 1 次提交
    • M
      Roslyn side changes for the new toggle button added to the Error list… (#11439) · d55123f8
      Manish Vasani 提交于
      * Roslyn side changes for the new toggle button added to the Error list to turn on/off full solution analysis
      
      We are moving the "Enable full solution analysis" option from Tools Option to the error list for improved discoverability, while also making it language agnostic. This change ensures that we set the Roslyn full solution analysis options when this button is toggled in the error list. Additionally, when we identify that the error list toggle button is available (Dev14 U3 or later), we will hide the tools option checkbox for "Enable full solution analysis" and show a note about it being moved to the error list. Note that we still continue with language specific defaults (C# off, VB on), but once the user has hit the error list toggle, the option setting is consistent across all languages.
      
      Addresses workitem https://github.com/dotnet/roslyn/issues/11392
      
      * Address PR feedback from Heejae - localization of strings.
      
      * Address PR feedback from Heejae
      
      * Address PR feedback
      
      * Move to newer MS.VS.Shell.14.0 dll to consume the new error list changes.
      
      * Move the code accessing the new IErrorList2 type into a separate method marked with [MethodImpl(MethodImplOptions.NoInlining)]
      d55123f8
  16. 19 5月, 2016 1 次提交
  17. 17 5月, 2016 1 次提交
  18. 10 5月, 2016 3 次提交
    • J
      Delete some dead code passing options around · c9d91a93
      Jason Malinowski 提交于
      c9d91a93
    • J
    • J
      Add a new API to get solution/document-specific options · 14ae44d3
      Jason Malinowski 提交于
      As a part of this change, I'm converting OptionSet from being a sealed,
      non-publically creatable type to an abstract type. I have chatted with
      @jaredpar and @davkean and we have all concluded this is a safe
      operation to make, assuming that anybody who was constructing the type
      is being recompiled. Since the only creator is within Roslyn itself,
      this is safe. I did have to update our PublicAPI.Shipped.txt baseline,
      because our public API checker includes modifiers in the list and is
      unaware that this particular modification is safe.
      
      Two APIs are added; Solution.Options exists that will eventually give a
      snapshotted OptionSet to ensure the same snapshot guarantees you get
      from the rest of the Solution API, and Document.Options exists to get
      the options that apply to a specific Document. I considered adding
      Project.Options, but discovered in practice nobody had a meaningful use
      for it. I had expected it could be used when generating new documents,
      but since style options can be specified on a file/folder basis, this
      wouldn't be safe to use in that case.
      
      This API isn't implemented in a meaningful way yet, but allows for
      features to consume the new system once it exists.
      14ae44d3
  19. 28 4月, 2016 1 次提交
    • D
      Accessibility Improvements · 39815e1b
      David Poeschl 提交于
      Extract Interface (fixes #9958)
      - Read textbox labels
      - Read extractable members
      
      Generate Type (fixes #9959)
      - Read label text on dropdowns
      - Read combobox items
      
      Change Signature (fixes #9957)
      - Read parameter and button text
      
      Options pages (fixes #9962)
      - Read labels/checkboxes/radiobuttons
      39815e1b
  20. 26 4月, 2016 2 次提交
  21. 25 4月, 2016 3 次提交
  22. 23 4月, 2016 1 次提交
  23. 22 4月, 2016 2 次提交
  24. 05 4月, 2016 2 次提交
  25. 01 3月, 2016 4 次提交
    • D
      Code Style: Analyzer/Fixer/Options for naming conventions · 8051eec3
      David Poeschl 提交于
      Implements #7064
      
      This change includes:
      
      - An analyzer and codefix for enforcing naming styles and fixing symbol names to comply with a chosen & configurable set of naming rules.
      - A set of Enforcement Levels that can be applied to different naming rules.
      - A mechanism for linking from a lightbulb preview to the option that caused the related diagnostic to be created (could be moved to a different PR or release)
      - Moving of the "Formatting" options pages under the Code Style node.
      8051eec3
    • B
      Don't throw from properties used in databinding. · d088a7e3
      Balaji Krishnan 提交于
      The BooleanCodeStyleOptionViewModel are a glue between older checkbox
      style options and the new grid UI with severity levels. Well, the older
      options don't have severity levels and I was throwing NotSupportedEx,
      but forgot they were used in databinding. As a result we had non-fatal
      exceptions. This change removes them.
      d088a7e3
    • B
      211370e3
    • B
      Localize strings. · 69e9c10b
      Balaji Krishnan 提交于
      69e9c10b