- 05 10月, 2017 26 次提交
-
-
由 Jason Malinowski 提交于
TestWorkspaceFixture is a type you can use to have a single TestWorkspace be shared between multiple tests. To ensure that the TestWorkspace doesn't end up with views being opened between tests, many tests in their dispose method call CloseTextView(). This was calling GetWorkspace(), which creates the workspace lazily, so in some cases we'd create a test when we didn't expect it. Since this was happening in xUnit's Dispose() handling, there wasn't a synchronization context which is now required due to 0911290b06184eb.
-
由 Jason Malinowski 提交于
This shouldn't have to reference anything magic -- it's a simple library.
-
由 Jason Malinowski 提交于
All these uses weren't didn't need the IWpfTextView specialization, so it's a simple swap.
-
由 Jason Malinowski 提交于
This removes WPF and XML references.
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
ForegroundThreadAffinitizedObject took a WPF dependency so it could create a lower-priority DispatcherSynchronizationContext, which is something we can set up during our package load where we were already forcing the foreground thread information to be initialized. We also have to strengthen an assertion since we can't check for application initialization anymore.
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
Right now some of this depends on our ability to make text views when we hover over things, so for now we'll leave it up here. This is a fairly weak dependency and will be able to move back soon.
-
由 Jason Malinowski 提交于
Thankfully the only things still using the old glyph types (versus the new image monikers) are already in the Visual Studio layer, so this is an easy move.
-
由 Jason Malinowski 提交于
No reason to have trivial extension methods used in one place.
-
由 Jason Malinowski 提交于
This is a really ugly refactoring that removes the WPF APIs from IDeferredQuickInfoContent and adds a service in EditorFeatures.Wpf that converts from them to WPF elements. It's a straightforward refactoring and everything still works, but it's not pretty at all. EventHookup also worked with QuickInfo directly, and thus had to be moved out of CSharpEditorFeatures. There isn't a CSharp-specific EditorFeatures.Wpf assembly, so it's going into the Visual Studio layer for now.
-
由 Jason Malinowski 提交于
This uses WPF clipboard operations to allow us to save fancy interactive command history to the clipboard.
-
由 Jason Malinowski 提交于
This is our abstraction for showing dialogs, so the WPF implementation needs to depend on WPF.
-
由 Jason Malinowski 提交于
The editor provides an API if it's in high contrast mode which can happen either because the system is in high contrast mode or they've chosen a Visual Studio theme that is higher contrast. This eliminates an icky WPF dependency. We stil disable generation of the classification if we are in this mode, because editor ignores the tags we'd produce anyways when in contrast mode.
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
Our presenter depends on the VS completion APIs (which aren't currently implemented in a cross-platform way) and also depends on creating WPF elements for tooltips, which means it can't live in EditorFeatures.Wpf for now.
-
由 Jason Malinowski 提交于
This should have been deleted in my merging of EditorFeatures.Next but I missed it.
-
由 Jason Malinowski 提交于
These speak in terms of WPF colors and brushes, so must be moved out.
-
由 Jason Malinowski 提交于
Given this depends on various VS APIs and low demand for it to work in other hosts, we can just move it here for now.
-
由 Jason Malinowski 提交于
Unfortunately the tagger exposes "LineSeparatorTag" which itself exposes WPF elements for how the tagging should be done. If it wasn't for this mix we could have kept the tagger as a data layer in EditorFeatures but that's not going to work.
-
由 Jason Malinowski 提交于
This lets us remove a dependency in EditorFeatures.csproj on System.Drawing.
-
由 Jason Malinowski 提交于
Although this could be split out more precisely, for now we'll just move the entire feature to the WPF layer. IEditorInlineRenameService.cs is left behind however, as that interface is implemented by TypeScript and other languages. For now I'm considering EditorFeatures.Wpf to be an implementation assembly for now and so interfaces implemented should still live in the base assembly. In CSharpEditorFeatures and BasicEditorFeatures, there was the implementation of IEditorInlineRenameService which had no language specific details other than the language name the service was exported for. I have moved those into EditorFeatures.Wpf rather than have additional assemblies for language specific stuff, since I anticipate that to be nearly non-existent.
-
由 Jason Malinowski 提交于
This wasn't included in the project file, so clearly wasn't being used.
-
由 Jason Malinowski 提交于
This is a (currently empty) project that will contain parts of EditorFeatures that demand the WPF surface area.
-
由 Jinu 提交于
* Adding cobyrc file for testing * Adding isImplicit info to ioperation tests * Adding Language name to the test dumper * Formatting change to test dumper * Removing cobyrc file * Fixing more tests * Resolving conflicts * Moving the language to assert check * Resolving conflicts * Reacting to merge conflict
-
由 Andy Gocke 提交于
Fixes #21768 Fixes #22027
-
- 04 10月, 2017 14 次提交
-
-
由 Julien Couvreur 提交于
-
由 Julien Couvreur 提交于
-
由 Julien Couvreur 提交于
-
由 Jason Malinowski 提交于
Reduce DocumentId array allocations
-
由 Jason Malinowski 提交于
Since ImmutableDictionary and ImmutableSortedDictionary are both implemented via trees; you can think of an ImmutableDictionary as just being a sorted dictionary where the underlying key is the hash int. Since our hash is just a hash of a GUID, we can compare by the GUID, switch to a ImmutableSortedDictionary, and then avoid another sort when we're computing checksums.
-
由 Heejae Chang 提交于
-
由 Omar Tawfik 提交于
-
由 Jason Malinowski 提交于
Bump NuGet monikers for the preview 1 split
-
由 Andy Gocke 提交于
There is no conversion between ref like types and either object or generic parameters (even if constrained to struct) in either direction. This change enforces that rule and adds tests around pattern matching, which exercises this rule.
-
由 Jason Malinowski 提交于
We previously were using ImmutableArrays, so if you had a large number of documents (say thousands) we'd be creating huge numbers of huge arrays over and over again. For this pattern, ImmutableList is more appropriate.
-
由 Ashley Hauck 提交于
Fix bug in build-utils Ensure-SdkInPathAndData
-
由 Manish Vasani 提交于
Add unit tests for omitted arguments
-
由 Ashley Hauck 提交于
-
由 Manish Vasani 提交于
Add unit tests for IArrayElementReferenceExpression and make the API …
-