- 12 1月, 2018 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 22 12月, 2017 1 次提交
-
-
由 v-mdriml 提交于
-
- 12 12月, 2017 1 次提交
-
-
由 Zbyněk Sailer 提交于
-
- 09 12月, 2017 1 次提交
-
-
由 Tomáš Matoušek 提交于
-
- 08 12月, 2017 1 次提交
-
-
由 Sam Harwell 提交于
-
- 07 12月, 2017 2 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
This centralizes the logic for detecting the language of the tmp_proj files that are generated during WPF compilation.
-
- 06 12月, 2017 1 次提交
-
-
由 Tom Meschter 提交于
-
- 05 12月, 2017 1 次提交
-
-
由 Sam Harwell 提交于
-
- 01 12月, 2017 1 次提交
-
-
由 Julien Couvreur 提交于
-
- 30 11月, 2017 7 次提交
-
-
由 Sam Harwell 提交于
Closes #23479
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
-
由 Jason Malinowski 提交于
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
-
- 29 11月, 2017 4 次提交
-
-
由 Jason Malinowski 提交于
The QuickInfoDisplayDeferredContent type was somewhat evil: it had a set of properties that were intended as test-only accessors, that would give you access to fields of type IDeferredQuickInfoContent but would cast to the expected concrete type. In a previous refactoring I started using those properties in the product which breaks F# because it may create different implementations from IDeferredQuickInfoContent. My fix here is just to delete the properties and clean up the test helpers to do explicit casting. By refactoring the helpers a bit the test complexity doesn't change and eliminates the trap in the first place.
-
由 Sam Harwell 提交于
The new ILSpy functionality will be driven by the existing Go To Definition command.
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
-
- 28 11月, 2017 2 次提交
-
-
由 Siegfried Pammer 提交于
-
- 23 11月, 2017 1 次提交
-
-
由 Julien Couvreur 提交于
-
- 18 11月, 2017 1 次提交
-
-
由 Jason Malinowski 提交于
This takes care of Microsoft.VisualStudio.Imaging and Microsoft.VisualStudio.ImageCatalog, which for now aren't available outside Visual Studio. ImageCatalog is a pretty simple data API so one day it might be useful, but for now isn't. Fixes dotnet/roslyn#23189.
-
- 17 11月, 2017 1 次提交
-
-
由 Jason Malinowski 提交于
Moving up to EditorFeatures.Wpf for now. It could potentially go higher if we determine this is a Visual Studio-only thing, but for now it's unclear where it will ultimately land. Fixes dotnet/roslyn#23184.
-
- 16 11月, 2017 1 次提交
-
-
由 Jason Malinowski 提交于
This depends on VS APIs that we don't have open source yet, and we don't need the feature for now in VS for Mac. Fixes dotnet/roslyn#23192.
-
- 11 11月, 2017 4 次提交
-
-
由 Ravi Chande 提交于
-
由 Ravi Chande 提交于
-
由 Ravi Chande 提交于
-
由 Ravi Chande 提交于
The trim_trailing_whitespace can affect tokens to the right of the caret so we need to check the token to the left.
-
- 29 10月, 2017 1 次提交
-
-
由 Jason Ramsay 提交于
-
- 27 10月, 2017 1 次提交
-
-
由 Heejae Chang 提交于
* added time tracking to completion set. from the point we start completion set to first time we are called from VS for best match (which indicate that completion set is actually shown to users first time for this particular completion session) the event is vs/ide/vbcs/intellisense/completion if completion is done without showing UI to users (etc or tab), then event will be marked as cancelled. * added perf tracking to LB fix all. there were already existing events so I just made those to include perf info (duration) as well. among all those events, these 2 are ones we were planning to add vs/ide/vbcs/codefixes/fixalloccurrencescomputation this shows time from the point user invoked fix all to where we shows preview window to users. vs/ide/vbcs/codefixes/applychanges this shows time from user clicked Apply from preview window to where we actually applied the changes to VS there are more events between them in case we want to dig in details later such as how long it took to calculate diagnostics, how many files are affected and etc. also all related events have correlation id to group related code fix events. also for fix all case, it contains scope to show whether fix all is for document, project, solution. * PR feedback. removed unnecessary parameter * removed repeated correction id set * updated comments.
-
- 26 10月, 2017 3 次提交
-
-
由 Jason Malinowski 提交于
It wasn't even being used. :-(
-
由 Heejae Chang 提交于
looks like I broke it when I did refactoring on KeepAliveSession by giving in wrong callback object. fix https://github.com/dotnet/roslyn/issues/22806 opened this for adding unit test - https://github.com/dotnet/roslyn/issues/22808 currently we don't have test around ISymbolSearchService.
-
由 Jason Malinowski 提交于
Call Hierarchy items hold onto their project so we can relocate the symbol, but instead of using the project that contained the caller, we were creating items with the project of the original method. This meant that further expansions wouldn't work correctly.
-
- 20 10月, 2017 3 次提交
-
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
Before this, if we couldn't find the project we'd throw exceptions and possibly crash or do something bad.
-
由 Jason Malinowski 提交于
Holding onto Project directly meant the snapshot would be leaked. We should only hold onto the SymbolKey so we can resolve it later.
-
- 19 10月, 2017 1 次提交
-
-
由 Jason Malinowski 提交于
-