- 19 5月, 2015 3 次提交
-
-
由 Tom Meschter 提交于
In unit tests, the `AnalyzerDependencyCheckingService` may be null. Check for that case before attempting to use it.
-
由 Tom Meschter 提交于
When running the `AnalyzerDependencyChecker` we need to apply assembly binding redirects while checking for missing assemblies. Otherwise we'll report an error that, for example, `System.Collections.Immutable Version=1.1.34` cannot be found when it has instead been redirected to `System.Collections.Immutable Version=1.1.36`.
-
由 Tom Meschter 提交于
Check analyzer consistency after solution load. Right now we only invoke the `AnalyzerDependencyCheckingService` when explicitly pushing a change in the set of analyzers down to the workspace. As we batch up all changes during a solution load and wait to push them to the workspace once at the end, we end up skipping this check until the next time the user adds or removes an analyzer. This change causes us to explicitly run the check when solution load completes.
-
- 16 5月, 2015 1 次提交
-
-
由 Tom Meschter 提交于
This commit updates the `AnalyzerDependencyChecker` type to reflect the recent changes to require all analyzers and dependencies to be specified, and the changes in how we load analyzer assemblies. Now that we require all analyzers and dependencies to be specified, we no longer look next to the specified analyzers to optimistically locate dependencies. Instead, we only consider the list of passed-in analyzers *plus* the assemblies already loaded into the `AppDomain`. The latter avoids unhelpful warnings in the event that the analyzer assembly includes a code fix that take a dependency on a Visual Studio assembly, which of course can't be included in the list of analyzers. We now create a warning when we identify a missing dependency. We now also check analyzers themselves for conflicts (i.e., assemblies at different paths with the same identity but different contents) instead of just their dependencies.
-
- 15 5月, 2015 5 次提交
-
-
由 Tomáš Matoušek 提交于
Remove duplicate sequence point and unnecessary nops emitted to VB iterators
-
由 Jared Parsons 提交于
Delete unused Desktop assemblies
-
由 Tomas Matousek 提交于
-
由 Jared Parsons 提交于
This deletes the empty and unused Desktop assemblies from the code base.
-
由 Andy Gocke 提交于
Right now the IDE uses the Csc/Vbc host objects from the build task by loading the task from the GAC (since the task is only installed in the MSBuild directory otherwise). However, this breaks using a different task for ETA tests since the GAC will always take precedence. This change adds the build task to the VS setup to include the task in the IDE installation.
-
- 14 5月, 2015 31 次提交
-
-
由 Dustin Campbell 提交于
Fix issue with C# character literals in InitializeComponent() method
-
由 Shyam N 提交于
Suppress a false positive error reported by FxCop
-
由 Shyam N 提交于
FxCop is currenly reporting a false positive error for calls to XmlReader.Create() in projects that compile against the .NET portable (core) framework. Suppress this error until the rule owners fix the rule to account for portable framework. Fixes internal bugs 1169525, 1169526, 1169527
-
由 Heejae Chang 提交于
fixed crash due to null project id
-
由 Heejae Chang 提交于
-
-
由 Andrew Casey 提交于
Refine construction of DynamicFlagsCustomTypeInfo
-
由 Andrew Casey 提交于
Separate factory methods for each of the projects that consumes it and a little less copying.
-
由 Andrew Casey 提交于
Expand transparent identifiers in the EE
-
由 Tomáš Matoušek 提交于
EnC: Renaming captured variables is rude
-
由 Neal Gafter 提交于
Generalize assert to include source statements that result in bound try
-
由 Andrew Casey 提交于
...the same way we expand display classes and state machines. If we see a local or parameter with a transparent identifier generated/mangled name, we should instead include the properties of its (anonymous) type in our list of bindable symbols. Points of interest: 1. Transparent identifiers can be chained (i.e. have transparent identifier properties). 2. Transparent identifiers can be captured (i.e. they might be display class fields, rather than locals or parameters). 3. Display class instance locals cannot appear within transparent identifiers (i.e. the recursion goes in only one direction). 4. For the benefit of the debugger, we're actually using fields, rather than properties. As a bonus, this was more consistent with the display class case and, therefore, easier to implement. TODO: Make a (hopefully) similar change in VB.
-
由 Heejae Chang 提交于
-
由 Tomas Matousek 提交于
-
由 Heejae Chang 提交于
we forgot to add null check before calling GetProject
-
由 Tomáš Matoušek 提交于
EnC: Fix mapping of variables declared in lambdas.
-
由 Andrew Casey 提交于
Enable test filtering with wildcards
-
由 Matt Warren 提交于
Bug2435
-
由 Neal Gafter 提交于
Fixes #2567
-
由 Tomáš Matoušek 提交于
Replace public fields with properties in Microsoft.CodeAnalysis
-
由 Shyam N 提交于
Fix an InvalidCastException in simplifier.
-
由 Andrew Casey 提交于
msbuild /m BuildAndTest.proj /p:IncludePattern="*Compilers*UnitTests*.dll"
-
由 Kevin Halverson 提交于
Unskip a couple tests that now pass on 64-bit...
-
由 Matt Warren 提交于
Add support for explicit interface members in DocumentCommentId
-
由 Matt Warren 提交于
Handle converting between interface implementation kinds
-
由 Matt Warren 提交于
Fix elastic formatting rule with comments
-
由 Matt Warren 提交于
Do not throw if paths are bad
-
由 Matt Warren 提交于
-
由 Kevin Halverson 提交于
-
由 Matt Warren 提交于
-
由 Matt Warren 提交于
-