- 06 8月, 2019 1 次提交
-
-
由 Petr Houska 提交于
-
- 30 7月, 2019 1 次提交
-
-
由 Petr Houska 提交于
-
- 22 5月, 2019 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 21 5月, 2019 1 次提交
-
-
由 Sam Harwell 提交于
-
- 27 3月, 2019 1 次提交
-
-
由 Heejae Chang 提交于
* removed IEditorClassificationService that is marked obsolete since 2017 and bunch of other code that only existed for the IEditorClassificationService. according to vso, only F# still has dependency so I talked to them to move to new API (IClassificationService) - https://devdiv.visualstudio.com/DevDiv/_git/DotNet-Source-Build-Tarball?path=%2Fsrc%2Ffsharp%2Fvsintegration%2Fsrc%2FFSharp.Editor%2FClassification%2FColorizationService.fs&version=GBmaster and a bunch of clean up and move code that has no dependency to the editor to lower layers so that I can consume in razor scenario. * added shim project for FSharp that has internal visible to FSharp editor * merged https://github.com/dotnet/roslyn/pull/31941 * addressing PR feedback * moved some type (such as DocumentSpan, ClassifiedSpan and etc) back to where fsharp has IVT to. can't move those since partner team is using them and they don't have IVT to workspace layer for some reasons. also, have put the IEditorClassificationService back and add a proxy in FSharp External Access so that it can still work until they remove all IVT.
-
- 15 12月, 2018 1 次提交
-
-
由 Manish Vasani 提交于
-
- 10 12月, 2018 1 次提交
-
-
由 dotnet-bot 提交于
-
- 23 10月, 2018 2 次提交
-
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
- 27 9月, 2018 1 次提交
-
-
由 Manish Vasani 提交于
Implementation of the custom column support has been kept extensible, so that each reference item can have customized key-values info, where key corresponds to the name of the custom dynamic column and values are set of one or more values the table entry. Columns become dynamically visible if at least one row in the table has a value for it. Fixes #24877
-
- 01 7月, 2018 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 21 3月, 2018 1 次提交
-
-
由 Neal Gafter 提交于
-
- 09 8月, 2017 1 次提交
-
-
由 Jason Malinowski 提交于
When we were navigating to a symbol with Go to Definition, we were roundtripping the symbol to a symbol key, and then trying to reconstitute the symbol by finding a project that had the reference and then grabbing that symbol. There are two problems with this approach: 1. We might get the symbol for the wrong language, which impacts the language we use to generate metadata as source. This fixes dotnet/roslyn#16818. 2. We might not even get the right symbol. Assembly identity in this case was using display name, which could be the wrong portable surface area or wrong version. The fix is to instead carry along the project ID of the originating symbol, and resolve against that.
-
- 15 7月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 17 6月, 2017 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 29 5月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 17 5月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 23 4月, 2017 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 21 4月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 20 4月, 2017 3 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
Move helper API up as it will be using functionality in EditorFeatures as part of FAR refactoring work.
-
- 14 3月, 2017 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 13 3月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 11 3月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 10 3月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 01 12月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 30 11月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 20 11月, 2016 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 18 11月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
Rename intenral code to 'FindUsages' so it better reflects that it can present results for more than just FindReferences.
-
- 10 11月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 24 9月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 07 8月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 06 8月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 31 7月, 2016 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 30 7月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-