- 23 4月, 2017 8 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 21 4月, 2017 6 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
After investigating with jason, we've concluded this strange code was written back in the days where roslyn workspaces and VS documents were not something you could trust to be in sync. So we had to have a lot of painful code to try to detect and bail out when that happened. This is definitely not necessary now, and we can just use the simple and correct function we already hve for this task.
-
由 CyrusNajmabadi 提交于
-
- 20 4月, 2017 26 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
Move helper API up as it will be using functionality in EditorFeatures as part of FAR refactoring work.
-
由 CyrusNajmabadi 提交于
The synchronous API still exists for TS to use until they move over to the entirely async api.
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
We can use this for FindRefs to compute the 'classified text' we produce for the display in the OOP server so that we don't have to go back to semantic-models back on hte client side when we get the results.
-
由 Ivan Basov 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
This reverts commit 4f7b313c, reversing changes made to 6d59ad84.
-
由 CyrusNajmabadi 提交于
-
由 vsadov 提交于
-
由 vsadov 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Neal Gafter 提交于
Fixes #18257
-
由 CyrusNajmabadi 提交于
-
由 Jared Parsons 提交于
In order to leverage LUT testing we need to have both of the follownig packages in our build. - xunit.runner.desktop - xunit Both of these include xunit.abstractions.dll in different forms: content and reference respectively. This creates a double write violation in our build. I've spoken with the xunit team and at this point they believe the feature is executing as designed. The content use in xunit.runner.desktop is meant to support 1.X clients who can't reference the package. I'm still working with them to find a better way to exclude this but for now this will remove the race in our build. Issue #18573 will remain open to track the handling here and find a better solution.
-