- 16 11月, 2016 1 次提交
-
-
由 David Poeschl 提交于
Fixes #15217 Also, change the column header from "Style" to "Required Style"
-
- 15 11月, 2016 2 次提交
-
-
由 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.
-
由 David Poeschl 提交于
Fixes #12669. Addresses one part of #9674 Fixes both the general code styles page and the naming styles page
-
- 25 10月, 2016 1 次提交
-
-
由 Omar Tawfik 提交于
-
- 21 10月, 2016 1 次提交
-
-
由 David Poeschl 提交于
This reverts commit 9f30b914.
-
- 20 10月, 2016 2 次提交
-
-
由 David Poeschl 提交于
This reverts commit 12ce69e2. Reverting this because it is causing VSI test failures, especially around Razor.
-
由 David Poeschl 提交于
This change also introduces Specification and Style management (deleting and editing). Also, fixes #14358
-
- 10 9月, 2016 2 次提交
-
-
由 Jason Malinowski 提交于
Now that our existing options have been tagged with the appropriate metadata, we can use that metadata to drive serialization. This updates IOptionSerializers to make them no longer have any language- specific metadata, and are simply driven from the metadata included on the option. This also renames IOptionSerializer to IOptionPersister, which is a better name.
-
由 Jason Malinowski 提交于
Since we only apply the options that finally changed, this behavior should be redundant, but requires us to categorize options in a not- obvious way.
-
- 20 7月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 12 7月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 09 7月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 24 6月, 2016 1 次提交
-
-
由 gafter 提交于
-
- 16 6月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 15 6月, 2016 3 次提交
-
-
由 Jason Malinowski 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 11 6月, 2016 1 次提交
-
-
由 Julien 提交于
-
- 26 5月, 2016 1 次提交
-
-
由 Brett V. Forsgren 提交于
-
- 21 5月, 2016 1 次提交
-
-
由 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)]
-
- 19 5月, 2016 1 次提交
-
-
由 Paul Vick 提交于
-
- 17 5月, 2016 1 次提交
-
-
由 Matt Warren 提交于
-
- 10 5月, 2016 3 次提交
-
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
-
由 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.
-
- 28 4月, 2016 1 次提交
-
-
由 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
-
- 26 4月, 2016 2 次提交
-
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
-
- 25 4月, 2016 3 次提交
-
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
This reverts commit ffec6afc.
-
由 Manish Vasani 提交于
-
- 23 4月, 2016 1 次提交
-
-
由 Srivatsn Narayanan 提交于
-
- 22 4月, 2016 2 次提交
-
-
由 Heejae Chang 提交于
to support this, I added a way to set different default value per language
-
由 Heejae Chang 提交于
to support this, I added a way to set different default value per language
-
- 05 4月, 2016 2 次提交
-
-
由 Balaji Krishnan 提交于
-
由 Balaji Krishnan 提交于
.. is selected, use the first codestyle to show a preview.
-
- 01 3月, 2016 4 次提交
-
-
由 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.
-
由 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.
-
由 Balaji Krishnan 提交于
-
由 Balaji Krishnan 提交于
-