- 18 2月, 2017 1 次提交
-
-
由 Heejae Chang 提交于
-
- 17 2月, 2017 1 次提交
-
-
由 Heejae Chang 提交于
-
- 14 2月, 2017 1 次提交
-
-
由 Heejae Chang 提交于
Ensure package is loaded by loading CPS project
-
- 11 2月, 2017 1 次提交
-
-
由 Ravi Chande 提交于
Capture better dumps for DevDiv #363724
-
- 10 2月, 2017 3 次提交
-
-
由 Heejae Chang 提交于
-
由 Neal Gafter 提交于
Duplicate some existing scoping tests for pattern declarations in declarator arguments, where they are not permitted. (#16804) * Duplicate some existing scoping tests for pattern declarations in declarator arguments, where they are not permitted. Fixes #13660
-
由 Kevin Pilch 提交于
Remove space preventing editorconfig settings from applying to vb files
-
- 09 2月, 2017 6 次提交
-
-
由 Jonathon Marolf 提交于
Downgrade SyntaxVisualizerExtension dependencies
-
由 Kevin Pilch-Bisson 提交于
-
由 Jonathon Marolf 提交于
-
由 Jason Malinowski 提交于
Bump the NuGet moniker to -rc5
-
由 Jason Malinowski 提交于
We've shipped -rc4 packages to nuget.org, so any future builds should be versioned higher.
-
由 Ravi Chande 提交于
Capture better dumps for https://devdiv.visualstudio.com/DevDiv/_workitems?id=363724&fullScreen=true&_a=edit Very infrequently, ImplementsClauseCompletionProvider is asked to provide symbols with a null context. It's not clear why this would happen. Add a FatalError.Report if we try to call any provider with a null context.
-
- 08 2月, 2017 6 次提交
-
-
由 DanMcNultyDev 提交于
Merging on behalf of @DanMcNultyDev
-
由 AlekseyTs 提交于
Add test coverage for Out Vars in global code in remaining executable statements.
-
由 Omar Tawfik 提交于
Added test to verify intellisense on Enumerable.Join parameter types
-
由 AlekseyTs 提交于
Closes #14113.
-
由 Omar Tawfik 提交于
More pattern matching scope tests
-
由 Omar Tawfik 提交于
-
- 07 2月, 2017 4 次提交
-
-
由 Jonathon Marolf 提交于
Prevent error on Analyzer project creation
-
由 Jonathon Marolf 提交于
this change prevents an error on RC.3
-
由 Tomáš Matoušek 提交于
Add test binding redirect for System.Xml.XmlDocument
-
由 Tomas Matousek 提交于
-
- 05 2月, 2017 1 次提交
-
-
由 Heejae Chang 提交于
changed all caller to call JsonRpc.StartListener once all states are set
-
- 04 2月, 2017 8 次提交
-
-
由 Heejae Chang 提交于
-
由 Neal Gafter 提交于
-
由 Omar Tawfik 提交于
-
由 Jonathon Marolf 提交于
Gather better info when AddDeclarationConflictsAsync crashes
-
由 Jonathon Marolf 提交于
Avoid deadlocks when unloading unloading multitargeted Asp.NET projects, or .NET Standard (CPS) Projects (directly or via Solution close) referencing Shared Projects
-
由 Jonathon Marolf 提交于
capture document on findtoken crash in linked files
-
由 Omar Tawfik 提交于
-
由 Julien Couvreur 提交于
-
- 03 2月, 2017 7 次提交
-
-
由 Jonathon Marolf 提交于
We are seeing reports of Visual Studio crashing in FindToken with argument out of range exceptions. It appears that this is causes by linked files being of differing lengths. This change captures the original and linked documents on the stack so we can better understand what is happening.
-
由 CyrusNajmabadi 提交于
Fix crash in roundtripping a symbol that references a LocalFunction's TypeParameter.
-
由 Jason Malinowski 提交于
Fix VisualStudioWorkspace thread affinity and defer creation
-
由 David Poeschl 提交于
Avoid deadlocks when unloading .NET Standard Projects (directly or via Solution close) referencing Shared Projects Fixes https://github.com/dotnet/roslyn/issues/14479 The problem here is that unloading projects takes a serialization lock, which can cause Shared Project IVsHierarchys to notify us that their context hierarchy has changed. In response to this, we try to set the new active context document for open files, which also tries to take the serialization lock, and we deadlock. For .NET Framework Projects that reference Shared Projects, two things prevent deadlocks when projects unload. During solution close, any Shared Projects are disconnected before the projects start to unload, so no IVsHierarchy events are fired. During a single project unload, we receive notification of the context hierarchy change before the project is unloaded, avoiding any IVsHierarchy events if we tell the shared hierarchy to set its context hierarchy to what it already is. Neither of these behaviors are safe to rely on with .NET Standard projects, so we have to prevent the deadlock ourselves. We do this by remembering if we're already in the serialization lock due to project unload, and then not take the lock to update document contexts if so (but continuing to lock if it's not during a project unload).
-
由 Jared Parsons 提交于
Move to new VS SDK build tools
-
由 Omar Tawfik 提交于
Add tests to ref return error codes
-
- 02 2月, 2017 1 次提交
-
-
由 Jared Parsons 提交于
-