- 17 11月, 2015 2 次提交
-
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
-
- 16 11月, 2015 2 次提交
-
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
-
- 15 11月, 2015 1 次提交
-
-
由 Andy Gocke 提交于
-
- 14 11月, 2015 11 次提交
-
-
由 Andy Gocke 提交于
-
由 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.
-
由 Andy Gocke 提交于
Mark *CompilationOption overloads as backcompat
-
由 Andrew Casey 提交于
Restore missing nuget implementations
-
由 Andrew Casey 提交于
...to Roslyn.VisualStudio.Setup.vsix
-
由 Manish Jayaswal 提交于
add imports for System.Console in response file - fixes #6768
-
由 Manish Jayaswal 提交于
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
NuGet ZIP is now used everywhere in CI
-
由 Jason Malinowski 提交于
Enable F5 deployment atop Visual Studio 2015 Update 1
-
由 drognanar 提交于
Handle case when not all projects exit break state
-
- 13 11月, 2015 10 次提交
-
-
由 Manish Vasani 提交于
Fix the batch pragma suppression fixer to handle the case where multiple diagnostics with different IDs are being suppressed on the same token Current logic in batch pragma fixer merges individual fixes in a document by applying each pragma fix sequentially and keeping track of new diagnostics spans for remaining diagnostics. The latter logic that computes new spans was using out of date spans, causing the subsequent fixes to be incorrectly applied. This change fixes that logic. Fixes #6455
-
由 Jason Malinowski 提交于
-
由 Tomáš Matoušek 提交于
Avoid hard test dependency on FX 3.5
-
由 Jared Parsons 提交于
Fix a couple of flaky suites
-
由 Tomáš Matoušek 提交于
Skip GAC test
-
由 Tomas Matousek 提交于
-
由 Jason Malinowski 提交于
-
由 Nick Guerrera 提交于
Adjust ErrorLogger to conform to current SARIF draft
-
由 Kevin Halverson 提交于
Rename VB Scripting Namespace...
-
由 Manish Vasani 提交于
Fix the batch pragma suppression fixer to handle the case where multiple diagnostics with different IDs are being suppressed on the same token Current logic in batch pragma fixer merges individual fixes in a document by applying each pragma fix sequentially and keeping track of new diagnostics spans for remaining diagnostics. The latter logic that computes new spans was using out of date spans, causing the subsequent fixes to be incorrectly applied. This change fixes that logic. Fixes #6455
-
- 12 11月, 2015 14 次提交
-
-
由 Neal Gafter 提交于
Documentation for csc and vbc command-line.
-
由 Jared Parsons 提交于
This test was failing because it's possible for a Task to execute on the thread where Wait is called (scheduler can run it inline). The particular assert here must run on a different thread as it's checking the ability to acquire a Mutex handle. Use an explicit thread now to ensure the check is correct.
-
由 Jared Parsons 提交于
Under stress scenarios even seeing if the timeout was at least a specific period of time fails. Going to a simpler check that we simply hit the value.
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
The compiler server suites were using a flawed method for tracking process used in the test. It tried to identify the processes used by the test by the installation path. At the end of any test it would then kill all processes originating from that path. That's flawed for a couple of reasons: 1. There is no guarantee that all processes with that path were started by the unit test 2. There is no guarantee external events won't prematurely kill the processes created by the unit tests. Both of these were happening in our build environment. To fix these tests I: - Remove all path based identification of processes - Changed all tests that used long running processes to instead use in-proc servers closes #6540
-
由 Jared Parsons 提交于
This suite was flaky because it relied on timeouts and cross process communication. The latter in particular was problematic because it depended on being able to control the lifetime of VBCSCompiler.exe. This is a process frequently killed in our scripts as it can lock DLLs and is always safe to kill. Fixed the flakiness by refactoring the APIs and eliminating the timeouts
-
由 John Hamby 提交于
Moving IOperation from future to master
-
由 Tomáš Matoušek 提交于
Enable vb test
-
由 Heejae Chang 提交于
put more information for analyzer exception
-
由 Tomas Matousek 提交于
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
We sometimes need an .exe and sometimes need a .dll, so let's just make it explicit. We can still get the assembly name either way.
-