- 24 6月, 2016 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 23 6月, 2016 1 次提交
-
-
由 Tomas Matousek 提交于
This reverts commit c6a1c2c8.
-
- 22 6月, 2016 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 06 6月, 2016 1 次提交
-
-
由 Charles Stoner 提交于
-
- 02 6月, 2016 2 次提交
-
-
由 Tomáš Matoušek 提交于
* Tests: fix minasync Task<T> to derive from Task * Tests: provide MinAsyncCorlibRef This combines the async features of minasync with mincorlib to produce a minimum unversioned corlib with async stubs. * Compilation: use System.Object from target corlib When creating a script compilation without an explicit return type, System.Object was being resolved via reflection from the host. This resulted in an implicit dependency of a script compilation on the host corlib, even if a different corlib was specified as a reference for the compilation (e.g. Xamarin.iOS). Fix this by using System.Object as defined in the corlib resovled for the compilation.
-
由 Aaron Bockover 提交于
* Tests: fix minasync Task<T> to derive from Task * Tests: provide MinAsyncCorlibRef This combines the async features of minasync with mincorlib to produce a minimum unversioned corlib with async stubs. * Compilation: use System.Object from target corlib When creating a script compilation without an explicit return type, System.Object was being resolved via reflection from the host. This resulted in an implicit dependency of a script compilation on the host corlib, even if a different corlib was specified as a reference for the compilation (e.g. Xamarin.iOS). Fix this by using System.Object as defined in the corlib resovled for the compilation.
-
- 21 5月, 2016 3 次提交
-
-
由 VSadov 提交于
-
由 Evan Hauck 提交于
-
由 Julien 提交于
-
- 28 4月, 2016 2 次提交
-
-
由 Julien 提交于
-
由 Tomas Matousek 提交于
-
- 22 4月, 2016 1 次提交
-
-
由 Manish Vasani 提交于
-
- 21 4月, 2016 2 次提交
-
-
由 Manish Vasani 提交于
Ensure that we generated a CompilationCompletedEvent for compilations with no source files (example an empty VSIX projects).
-
由 Manish Vasani 提交于
Ensure that we generated a CompilationCompletedEvent for compilations with no source files (example an empty VSIX projects).
-
- 20 4月, 2016 1 次提交
-
- 16 4月, 2016 1 次提交
-
- 07 4月, 2016 1 次提交
-
-
由 Charles Stoner 提交于
-
- 02 4月, 2016 1 次提交
-
-
由 Charles Stoner 提交于
-
- 29 3月, 2016 1 次提交
-
-
由 Charles Stoner 提交于
-
- 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.
-
- 01 3月, 2016 1 次提交
-
-
由 Charles Stoner 提交于
-
- 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).
-