- 29 9月, 2015 40 次提交
-
-
由 Dustin Campbell 提交于
Specify correct ComDefaultInterface for EnvDTE.CodeClass, fixing the results of System.ComponentModel.TypeDescriptor.GetProperties(...)
-
由 Andy Gocke 提交于
Change Windows CI build to use core clr
-
由 Andy Gocke 提交于
Always use GetEncoding(0) to try getting the default encoding
-
由 Kevin Pilch-Bisson 提交于
Save Diagnostic tokens automatically when debugging
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
-
由 Dustin Campbell 提交于
Code Model: Fix CodeFunction.Name for C# conversion operators
-
由 Andy Gocke 提交于
Remove linux coreclr binary patching
-
由 Dustin Campbell 提交于
Smart indenter should not throw when enter is pressed after invalid query continuation
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
-
由 Jason Malinowski 提交于
Implement Go To Implementation
-
由 Dustin Campbell 提交于
In Visual Studio 2013, CodeFunction.Name for C# conversion operators listed the "implicit/explicit" keyword first and the "operator" keyword second. In Visual Studio 2015, we accidentally swapped these. Unfortunately the v1 Workflow Designer depends on this value and the change broke scenarios where conversion operators are used. That change fixes that discrepancy and adds more unit tests around FullName and Name for operators.
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
-
由 Jason Malinowski 提交于
-
由 Andy Gocke 提交于
After updating to the latest CoreCLR NuGet packages we no longer need to be copying binaries from a drop share to run. This change adds a csc.sh and a vbc.sh so we can run on the CoreRun host on Linux like we do on Windows. The change also eliminates some cruft from the cibuild like the semaphore restore.
-
由 Jason Malinowski 提交于
By placing it under the IDG_VS_EDIT_GOTO menu with CommandWellOnly, the command gets the name we want -- Edit.GoToImplementation -- but isn't visible. We then place it where we want it to be.
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
This behaves more or less exactly the same as IGoToDefinitionService.
-
由 Jason Malinowski 提交于
This requires some updated handling of our INavigableItem interface. The Visual Studio implementation previously would only show the DisplayString if it had children, and would otherwise show file location and the source snippet. For implementations, the source snippet is somewhat useless: in the case of methods you just see the method signature a bunch of times. Thus, we wanted to show source location and a fully qualified name, something which wasn't expressible. The new interface now has DisplayString, which can be null if you want the string to be line from the source. Whether you want to show the file location is explicitly called out now too.
-
由 Jason Malinowski 提交于
It can contain modifiers or other things, so it's not just a name.
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
Our INotificationService took a title and a message. In VS, the title and message were just concatenated together on consecutive lines and both displayed in the "message" portion of the message box. In other hosts, we used the title as the "real" message box title. Features were terribly inconsistent with how this was handled. Some features expected the VS behavior (and would have had clipped text in other hosts). Other features didn't expect the VS behavior, making ugly dialogs. The new behavior: the title is reserved for the title bar. This is ignored for the VS implementation, but should just be (if anything) the name of the feature complaining about something. All features who actually wanted the concatenation behavior are now doing so explicitly.
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
-
由 Dustin Campbell 提交于
In the smart indenter, we try to find a reasonable query clause. However, in a particular mangled case (e.g. "from i in l into x") there isn't a clause to use. If that happens, just compute the default indentation rather than throwing an InvalidOperationException.
-
由 Kevin Pilch-Bisson 提交于
Add CodeFix providers for warnings BC40003 and CS0108
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
TryGoToDefinition accepted a containingTypeSymbol which was used to do some specific logic to see if third-party navigation is allowed. Move that logic to the AbstractGoToDefinitionService and just pass the result of the logic through.
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
-
由 Dustin Campbell 提交于
Fix issue when pressing ENTER in XML doc comments with a selection
-
由 Dustin Campbell 提交于
In order to insert XML doc comment exterior trivia (e.g. /// or '''), we grab the caret position prior to the new line being inserted into the editor and then perform a bit of analysis afterward using that position. However, if there's a selection in the editor and the caret is at the end of that selection, the position will be in an unexpected place in the syntax tree, causing that bit of analysis to fail. So, in this case (and all cases), we use the start of the selection as the position to perform analysis on since that position will be consistent after the new line is inserted.
-