- 09 7月, 2015 9 次提交
-
-
由 Jared Parsons 提交于
Unit test assembly for our MSBuild tasks
-
由 Dustin Campbell 提交于
Remove CompletionTriggerInfo.IsAugment property
-
由 Jared Parsons 提交于
This is the start of our unit test assembly for our MSBuild assets.
-
由 Andy Gocke 提交于
The targets files were previously split into an open version in Microsoft.CodeAnalysis.Toolset.Open and a closed version in build/. This unifies the four targets into two new targets, VSL.Settings.targets and VSL.Imports.targets, and moves all the targets from ..Toolset.Open into the build/ folder.
-
由 Dustin Campbell 提交于
This propery was essentially unused. It was only ever checked by the SuggestionModeCompletionProviders and in that case, it was always true.
-
由 Dustin Campbell 提交于
Unify C# and VB suggestion mode completion providers
-
由 Tomáš Matoušek 提交于
More PE Writer cleanup
-
由 Dustin Campbell 提交于
Currently, the C# and VB suggestion mode completion providers both implement ICompletionProvider in nearly the same way. This change introduces a new base class containing the shared implementations. Note: prior to this change, C# and VB returned different values for IsCommitCharacter: false and true respectively. Now they'll both return false. However, this is OK because the completion controller handles builder completion items specially and IsCommitCharacter so that is never actually called in this case.
-
由 Tomas Matousek 提交于
-
- 08 7月, 2015 10 次提交
-
-
由 Dustin Campbell 提交于
Remove special VB Implements/Inherits statement completion list provider
-
由 Tomáš Matoušek 提交于
Text section header cleanup
-
由 Tomas Matousek 提交于
-
由 Dustin Campbell 提交于
There is a special completion list provider in VB for showing completions within Inherits or Implements statements. This change removes that customer completion list provider and pushes its logic down into the recommendation service. That way the Recommender API will correctly return these symbols, and the symbol completion provider will service them up into the completion list. Because the Implements/Inherits completion list provider produced an exclusive lists, a small tweak needs to be made to the built-in type keyword recommender. Otherwise, keywords like 'Boolean' would be recommended after Inherits, which isn't legal. Additionally, I've added a unit test to verify that 'Global' **does** show up after Inherits and Implements.
-
由 Tomáš Matoušek 提交于
Remove unused PE sections
-
由 Tomas Matousek 提交于
-
由 Wonseok Chae 提交于
[Bug][VB] RudeEdit error message blindly blames AutoProperty It fixes #3605
-
由 Wonseok Chae 提交于
It fixes #3605
-
由 Tom Meschter 提交于
Remove dependency on Microsoft.CodeAnalysis.Workspaces FixerWithFixAllAnalyzer references types in the Workspaces assembly in a couple of places: ``` C# private static string CodeFixProviderMetadataName = typeof(CodeFixProvider).FullName; ``` This creates a runtime dependency on Microsoft.CodeAnalysis.Workspaces.dll which is part of VS but not part of the compilers (csc/vbc/vbcscompiler). The analyzers that derive from this type thus work in VS but fail during build with a `TypeInitializationException`. The fix is to use hard-coded strings for the names of these types. As they are part of the public API, their names won't be changing anytime soon. This does not remove the project-to-project reference to Workspaces. Doing so would have required fixing up a bunch of `<see cref="..." />` elements in the doc comments to use the full name of these types as well, generally making them much uglier. This isn't necessary to fix the runtime issue. Fixes #3706.
-
由 Tom Meschter 提交于
FixerWithFixAllAnalyzer references types in the Workspaces assembly in a couple of places: ``` C# private static string CodeFixProviderMetadataName = typeof(CodeFixProvider).FullName; ``` This creates a runtime dependency on Microsoft.CodeAnalysis.Workspaces.dll which is part of VS but not part of the compilers (csc/vbc/vbcscompiler). The analyzers that derive from this type thus work in VS but fail during build with a `TypeInitializationException`. The fix is to use hard-coded strings for the names of these types. As they are part of the public API, their names won't be changing anytime soon. This does not remove the project-to-project reference to Workspaces. Doing so would have required fixing up a bunch of `<see cref="..." />` elements in the doc comments to use the full name of these types as well, generally making them much uglier. This isn't necessary to fix the runtime issue.
-
- 07 7月, 2015 18 次提交
-
-
由 Matt Mitchell 提交于
Fix modified path to nuget.exe
-
由 Matt Mitchell 提交于
-
由 Wonseok Chae 提交于
RudeEdit error message has a placeholder not filled in This fixes #3604 by passing the display name for rude edit diagnostics.
-
由 Charles Stoner 提交于
Fix typos
-
由 Tomáš Matoušek 提交于
Remove reference to Cci.IModule from PEWriter
-
由 Charles Stoner 提交于
-
由 Tomas Matousek 提交于
-
由 Tomáš Matoušek 提交于
PEWriter refactoring: sync PE header structures with those of PEReader
-
由 Tomáš Matoušek 提交于
More PE header tests
-
由 Tomas Matousek 提交于
-
由 Wonseok Chae 提交于
This fixes #3604 by passing the display name for rude edit diagnostics.
-
由 Andrew Casey 提交于
Include usings debug info for expr-bodied members
-
由 Tomáš Matoušek 提交于
Avoid translating global imports in presence of declaration errors
-
由 Andrew Casey 提交于
Don't look for labels in UsingsBinders
-
由 Andrew Casey 提交于
They were getting dropped in ```MethodCompiler.BindMethodBody```.
-
由 Andrew Casey 提交于
Prefer statements to expressions in the Immediate Window
-
由 Andrew Casey 提交于
...as in the native expression evaluators. Note: VB is unaffected since it only allows implicit local declarations in the Immediate window. CR: @KevinH-MS, @cston Fixes #3822
-
由 Charles Stoner 提交于
-
- 06 7月, 2015 3 次提交
-
-
由 Tomas Matousek 提交于
-
由 Tomáš Matoušek 提交于
Add PE header test
-
由 Tomas Matousek 提交于
-