- 25 6月, 2015 2 次提交
-
-
由 Jason Ramsay 提交于
-
由 Jason Ramsay 提交于
document.Project.LanguageServices.GetService().GetAdditionalReferencesAsync(document, symbol, cancellationToken) throws a null reference exception. Adding the null check to support this scenario.
-
- 24 6月, 2015 8 次提交
-
-
由 Andrew Casey 提交于
Remove contradictory ProjectReference properties
-
由 Andrew Casey 提交于
It doesn't make sense to have both ReferenceOutputAssembly=false and IncludeOutputGroupsInVSIX=BuildProjectOutputGroup. (The upshot is that the affected references end up in the VSIX unsigned.)
-
由 Neal Gafter 提交于
In a switch's default clause that is unexpected, for example, we should throw ExceptionUtilities.UnexpectedValue(value); Long ago this was a standard but we've drifted from it. Closes #3495
-
由 Tom Meschter 提交于
Add documentation on rule set files Add documentation describing the relevant portions of the .ruleset file format. Fixes #1073.
-
由 Neal Gafter 提交于
Fix copyrights
-
由 Kevin Halverson 提交于
Prefer System.Linq over System.Core... (fixes #2547)
-
由 Kevin Halverson 提交于
When we optimistically load a "LINQ library", prefer to load System.Linq (and then fall back to System.Core if that fails).
-
由 Tom Meschter 提交于
Add details about the command line switches and MSBuild properties used to pass rule set files.
-
- 23 6月, 2015 20 次提交
-
-
由 Manish Vasani 提交于
Use a JSON serializer for serializing strings to errorlog file. Fixes #3337
-
由 Tom Meschter 提交于
Fix DeclarePublicAPIAnalyzer The analyzer can report three different diagnostics, but currently only returns two from the `SupportedDiagnostics` property. This is the first step in addressing #3626. The second step is moving to a new build of the Roslyn diagnostics once it has been checked in.
-
由 AlekseyTs 提交于
C#: Improve error reporting for an Overload Resolution failure due to an ambiguity.
-
由 AlekseyTs 提交于
Fixes #2985.
-
由 AlekseyTs 提交于
Reconcile SemanticModel behavior for imports/using aliases with errors across VB and C#.
-
由 Manish Vasani 提交于
Fixes #3337 (errorlog JSON output should escape backslashes)
-
由 Tom Meschter 提交于
The analyzer can report three different diagnostics, but currently only returns two from the `SupportedDiagnostics` property.
-
由 Tom Meschter 提交于
Add initial documentation on Additional Files This commit covers the following: * Uses of Additional Files * Passing Additional Files on the command line * Specifying an individual item as an `AdditionalFile` in an MSBuild project * Specifying an entire set of items as `AdditionalFile`s in an MSBuild project * Accessing and reading additional files through the `AnalyzerOptions` type * Includes sample analyzers that read additional files Fixes #3543.
-
由 AlekseyTs 提交于
-
由 Manish Vasani 提交于
Add documentation to guide the code fix authors on correct way to implement a FixAllProvider. Fixes #2902
-
由 VSadov 提交于
Corrected misspellings in code comments
-
由 Tom Meschter 提交于
And move the real one from docs/analyzers to docs/compilers.
-
由 Tom Meschter 提交于
Adds information on the additional file analyzer samples.
-
由 Tom Meschter 提交于
-
由 Tom Meschter 提交于
Add copyright headers to analyzer samples source files.
-
由 Tom Meschter 提交于
Add a couple of sample analyzers that demonstrate the use of additional files. The SimpleAdditionalFileAnalyzer uses the additional file's `SourceText` instance to read it line by line, while the XmlAdditionalFileAnalyzer writes the contents out to a `Stream` so that it can be read by `XDocument.Load`.
-
由 Tom Meschter 提交于
Fix some small typos in the C# Additional Files analyzer samples.
-
由 Andy Gocke 提交于
Update version to 1.1.0 and PreRelease tag to -beta1
-
由 Tom Meschter 提交于
Fix up Analyzer paths so we correctly find the analyzer assemblies in the Microsoft.CodeAnalysis.Analyzers package.
-
由 Tom Meschter 提交于
Add a couple of sample analyzers that demonstrate the use of additional files. The SimpleAdditionalFileAnalyzer uses the additional file's `SourceText` instance to read it line by line, while the XmlAdditionalFileAnalyzer writes the contents out to a `Stream` so that it can be read by `XDocument.Load`.
-
- 22 6月, 2015 1 次提交
-
-
由 Manish Vasani 提交于
-
- 21 6月, 2015 2 次提交
-
-
由 CyrusNajmabadi 提交于
Fix crash in the solution size tracker for solutions that don't support syntax.
-
由 Cyrus Najmabadi 提交于
-
- 20 6月, 2015 7 次提交
-
-
由 VSadov 提交于
[VB Compiler Scanner] Unifies TryScanToken & ScanTokenFullWidth
-
由 Andy Gocke 提交于
-
由 AlekseyTs 提交于
This change is related to issue #2805. When an alias target cannot be resolved, GetSymbolInfo(<alias reference node>) – returns Nothing in VB, but returns an ErrorTypeSymbol in C# GetAliasInfo(<alias reference node>) – returns Nothing in VB, but returns corresponding AliasSymbol in C#. GetSymbolInfo should never return error types, so VB behavior is correct and this change adjusts C# behavior accordingly. GetAliasInfo should return an AliasSymbol even if the alias target cannot be resolved, so C# behavior is correct. VB behavior was caused by the fact that, if target couldn’t be resolved, the AliasSymbol wasn’t even created. This change ensures that the AliasSymbols are created.
-
由 Tom Meschter 提交于
Update Rule Set Format.md to use a relative path to the rule set schema file.
-
由 Tom Meschter 提交于
Add documentation describing the relevant portions of the .ruleset file format. Fixes #1073.
-
由 Tom Meschter 提交于
1. Add examples to the "Uses" section. 2. Correct the MSBuild item name: `AdditionFile` -> `AdditionalFiles`. 3. Show an example XML terms file for one of the samples.
-
由 AdamSpeight2008 提交于
Implement the requested changes to the Pull Request.
-