- 13 7月, 2016 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 12 7月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 11 7月, 2016 2 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
- 09 7月, 2016 2 次提交
-
-
由 Jonathon Marolf 提交于
These tags were missing from the telemetry vsix and the setup.next vsix.
-
由 CyrusNajmabadi 提交于
-
- 07 7月, 2016 24 次提交
-
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
Combine Kernel32.cs, Ole32.cs and User32.cs into a single NativeMethods.cs. The distinction is not meaningful
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
* Add ClearEditor() API to editor tests that is called at the start of each test * Add named parameters to VerifyCurrentLineText(...) and VerifyTextContains(...) test helpers to make it clearer when the caret position is specified and intended to be asserted * Move calls which wait for async operations into the APIs and out of test helpers * Other minor tweaks
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
This change makes SendKeys less flaky and removes the delay between characters, which was hiding bugs. Now, we just wait for application idle before blasting keys to the VS process. Additionally, I've started more cleanly separate code that runs in process vs. out of process.
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
This makes it more natural to set up tests where the editor is expected to have some code and the caret is expected to be positioned. This also removes some crusty DTE code that was executed over RPC.
-
由 Dustin Campbell 提交于
This is the initial punch through that contains: - A few more tests ported from CSharpAutomaticBraceCompleteion - Tons of clean up (and more to come) in the SendKeys implementation - Fix for incorrectly defined `VkKeyScan` Win32 API P/Invoke (needs to be unicode CharSet!) - Fix code which tests text before and after caret - Fix loads of bugs in the existing tests
-
由 Dustin Campbell 提交于
-
- 06 7月, 2016 1 次提交
-
-
由 Jason Malinowski 提交于
-
- 05 7月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 01 7月, 2016 5 次提交
-
-
* Merge pull request #12041 from heejaechang/buildsyncrace found one more case where documentId can be null * prevent VS from crashing if VS got shutdown while build error reporting is in progress. * Update our NuGet package version to 1.3.2 * Update Microsoft.DiaSymReader.Native to 1.4.0 RTM (#12141) * Enable building of release nuget packages. This commit makes it so that we will always try to generate release nugets except if they depend on prerelease packages. If one of our nuget packages happens to depend on prerelease packages, then when building release nugets, we will simply print a message in the build output and skip release nuget generation for that package (and allow the overall build to succeed). * Address code review feedback. * Simplify script to use nuget.exe for prerelease dependency validation instead of adding custom logic in the script for this. * Remove Microsoft.CodeAnalysis.EditorFeatures from list of prerelease nuget packages. * Change the name of the error log file to skipped_packages.txt. * fixed DifferenceViewer leak this leak was responsible for about 14% of managed memory in customer's dump. basically, in certain condition, if cancellation exception is thrown, we will not close difference viewer which cause all text views to leak. that cause all taggers and text buffers to leak and that cause our preview workspaces to alive. which in turn cause all solutions to alive and so on. all those objects (view, buffer, workspace, solution) are quite big graphs. so ends up eat up 14% of memory. added assert to make sure if we leak viewers again, we get some kind of notification.
-
由 Jared Parsons 提交于
-
由 DotNet Bot 提交于
-
由 Kevin Pilch-Bisson 提交于
-
由 Kevin Pilch-Bisson 提交于
-
- 30 6月, 2016 1 次提交
-
-
由 Charles Stoner 提交于
-
- 28 6月, 2016 1 次提交
-
-
由 Manish Vasani 提交于
* Display analyzer assemblies with no applicable diagnostic analyzers towards the end of analyzers list in solution explorer For most cases, these are analyzer depedencies with no analyzers. For few cases, these might be analyzer assemblies with no analyzers applicable for the given project langauge. For few other cases these might be analyzer assemblies whose diagnostic analyzers could not be instantiated for some reason, and hence have no rules. We still display such analyzers in the solution explorer so the user is aware that the project file contains these analyzer references, but display them towards the end to avoid clutter. Fixes https://github.com/dotnet/roslyn/issues/12047 * Address PR feedback and completely hide the analyzer dependencies (analyzer assembly has no diagnostic analzyers and also has no load errors)
-