- 20 4月, 2016 1 次提交
-
- 16 4月, 2016 1 次提交
-
- 17 3月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 09 3月, 2016 2 次提交
-
- 05 3月, 2016 1 次提交
-
-
由 Jason Malinowski 提交于
-
- 03 3月, 2016 1 次提交
-
-
由 Gen Lu 提交于
The flag name is "IOperation". Register opeartion actions and calling SemanticModel.GetOperation while the feature is disabled will throw an InvalidOperationException. Also log a non-fatal-watson when SemanticModel.GetOperation crashes.
-
- 25 2月, 2016 1 次提交
-
-
由 Ty Overby 提交于
-
- 14 11月, 2015 1 次提交
-
-
由 Andy Gocke 提交于
Sometimes called "fake sign" or "OSS sign" public signing is including the public key in an output assembly and setting the "signed" flag, but not actually signing the assembly with a private key. This is useful for open source projects where people want to build assemblies which are compatible with the released "fully signed" assemblies, but don't have access to the private key used to sign the assemblies. Since almost no consumers actually need to check if the assembly is fully signed, these publicly built assemblies are useable in almost every scenario that the fully signed one would be used in. This PR implements support only for C# -- VB will be added soon. If being used at the command line, the /publicsign flag can be passed to csc and the /keyfile flag can specify the public key. Unlike fully signing, a full key pair encoded in the SNK file format is not currently supported. When using /publicsign, just the public key must be in the /keyfile file. When using the API, the public key can be passed directly using the CryptoPublicKey CompilationOption.
-
- 04 11月, 2015 1 次提交
-
-
由 Neal Gafter 提交于
-
- 31 10月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 27 10月, 2015 1 次提交
-
-
由 Kevin Halverson 提交于
-
- 20 10月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 16 10月, 2015 1 次提交
-
-
由 Paul Harrington 提交于
-
- 14 10月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 07 10月, 2015 1 次提交
-
-
由 Bart Koelman 提交于
-
- 30 9月, 2015 1 次提交
-
-
由 Ty Overby 提交于
-
- 25 9月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 17 9月, 2015 1 次提交
-
-
由 Manish Vasani 提交于
Add a new CompilationOption "ReportSuppressedDiagnostics" to enable reporting compiler diagnostics suppressed in source. Note that the command line compilers will report such suppressed diagnostics in the SARIF errorlog file but not on the console output. This new compilation option was approved by the design team. Fixes #5216
-
- 15 9月, 2015 1 次提交
-
-
由 Manish Vasani 提交于
-
- 11 9月, 2015 2 次提交
-
-
由 Manish Vasani 提交于
Emit "isSuppressedInSource" boolean property for diagnostics in the ErrorLog file and report suppressed analyzer diagnostics in the error log.
-
由 Manish Vasani 提交于
1. CompilationWithAnalyzers can now report analyzer diagnostics with source suppressions (pragma/SuppressMessageAttribute). This will eventually allow us to surface diagnostics with source suppressions in the error list. Note that the behavior of command line compilers and all the GetDiagnostics APIs is unchanged, only the compiler analyzer will report diagnostics with source suppressions. 2. Add FixAll support for Suppression code fixes. Light bulb suppression fixes now show the "Fix all occurrences" options for Document/Project/Solution. This change adds the basic functionality to bulk suppress diagnostics. This will eventually be consumed for baselining all/selected diagnostics from error list/solution explorer. 3. Simplify the Suppression light bulb menu to remove the option to add a local SuppressMessageAttribute. The only options now are to suppress in source (pragma) or suppressions file (assembly level SuppressMessageAttribute).
-
- 05 9月, 2015 1 次提交
-
-
由 Kevin Halverson 提交于
-
- 26 8月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 25 8月, 2015 1 次提交
-
-
由 Andrew Casey 提交于
Since they can be used in subsequent submissions, they are always considered to be used. Fixes #4392
-
- 21 8月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 19 8月, 2015 1 次提交
-
-
- 05 8月, 2015 1 次提交
-
-
由 Manish Vasani 提交于
Changes include: 1. Enhance CompilationWithAnalyzers to allow computing analyzer diagnostics for a specific tree/span within a compilation and/or for a subset of analyzers. Implementation ensures no duplicate analysis by tracking partial analysis state and caching the reported analyzer diagnostics. 2. Overview of the new APIs added to CompilationWithAnalyzers: 1. GetAnalyzerSyntaxDiagnostics(tree, analyzers, ct) 1. Analogous to SyntaxTree.GetDiagnostics(ct) 2. Gets analyzer diagnostics reported by executing syntax tree actions on the given tree. 2. GetAnalyzerSemanticDiagnostics(semanticModel, spanOpt, analyzers, ct) 1. Analogous to SemanticModel.GetDiagnostics(spanOpt, ct) 2. Gets analyzer diagnostics reported by executing rest of the non-compilation actions on the given tree span. 3. GetAnalyzerCompilationDiagnostics(analyzers, ct) 1. Gets rest of the analyzer diagnostics which are reported by either of the following means: 1. Compilation actions (and compilation end actions) 2. Non-compilation actions reporting diagnostics on different tree: Executing a symbol action on a symbol definition in a tree, can report diagnostic on its partial definition in some other tree. 3. Simplify IDE analyzer driver by switching it to using the new CompilationWithAnalyzers APIs for analyzer diagnostic computation. Both the IDE and compiler drivers now use the compilation event queue model for driving analysis.
-
- 14 7月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 08 7月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 07 7月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 03 7月, 2015 1 次提交
-
-
由 Andrew Casey 提交于
As an optimization, submissions not containing declarations are not emitted. However, when we short-circuit emission, we also skip diagnostic reporting (e.g. in usings) that can trigger an assert in the next submission (which assumes that all errors have been reported). Fixes #3795
-
- 02 7月, 2015 2 次提交
-
-
由 Andrew Casey 提交于
This reverts commit 15443a23. Conflicts: src/Compilers/CSharp/Portable/CommandLine/CommandLineParser.cs src/Compilers/CSharp/Portable/PublicAPI.txt src/Compilers/Core/Portable/PublicAPI.txt src/Compilers/VisualBasic/Portable/CommandLine/CommandLineParser.vb Fixes #2888 Fixes #3786
-
由 Jared Parsons 提交于
Fell out of our normal cadence for this during the push for RTM. Now that we had a bit more breathing room getting us back on track here.
-
- 01 7月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 30 6月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 29 6月, 2015 1 次提交
-
-
由 bkoelman 提交于
-
- 24 6月, 2015 1 次提交
-
-
由 Manish Vasani 提交于
Add DiagnosticDescriptor.GetEffectiveSeverity(CompilationOptions) API to get the effective severity of diagnostics created based on the descriptor for the given compilation options. This change also removes the clone of this functionality in the IDE layer used by the solution explorer rule severity display and error list/diagnostic service. It now uses this public API. Fixes #2598
-
- 18 6月, 2015 2 次提交
-
-
由 bkoelman 提交于
-
由 Tomas Matousek 提交于
-