- 15 3月, 2018 5 次提交
-
-
由 Sam Harwell 提交于
Improvements in decompiler output
-
由 Vladimir Sadov 提交于
Merge from Features/constraints to dev15.7.x
-
由 Andy Gocke 提交于
This code was built as a prototype for porting the compiler server to other platforms. It has now been ported to CoreCLR and multiple OSes through multitargeting. The portable server cannot meet our security requirements and will never ship, so it's continued existence in our code is merely confusing to anyone who happens upon it.
-
由 Julien Couvreur 提交于
-
由 Julien Couvreur 提交于
-
- 14 3月, 2018 9 次提交
-
-
由 Vladimir Sadov 提交于
Merge from dev15.7.x to features/constraints
-
由 vsadov 提交于
-
由 Jared Parsons 提交于
Fix our coreclr job definition
-
由 Jared Parsons 提交于
The intent was to create a debug and release leg for our CoreClr tests. Our groovy code though gave both jobs the same name and Jenkins let the last one win. Hence we've only ever been running release CoreClr legs. This changes the definition to give each a separate name.
-
由 Heejae Chang 提交于
fix codeFix info bar behavior and fix AutoProperty to only offer refactoring when it is on right context (#25363) * it looks like codefix info bar has been broken for a while, (since 2016 - https://github.com/dotnet/roslyn/commit/eb5d3f83c07e2494dd5901c07fe8950e23e95b7e#diff-69343eea131fc14c4f6cff1408eb016a) this fixes it to behave correctly. * fix AutoProperty to offer the fix only when it is on right context. * added test * wrong cancellation token is used. it cause refactoring to not cancellable
-
由 vsadov 提交于
-
由 Jared Parsons 提交于
Move to the 2.1 SDK
-
由 Jinu 提交于
Use-auto-prop should not be offered if accessors differ in accessibility
-
由 Heejae Chang 提交于
* fixed MEF composition issue. <ImportMany> got left out when listener were changed. and it caused VBSnippetInfo to left out on MEF composition. * removed obsolete waiter types.
-
- 13 3月, 2018 12 次提交
-
-
由 Vladimir Sadov 提交于
'unmanaged' constraint fixups for merge
-
由 Cyrus Najmabadi 提交于
-
由 Siegfried Pammer 提交于
-
由 Siegfried Pammer 提交于
-
由 Siegfried Pammer 提交于
* Add header region to decompiled code (useful for debugging). * Add EscapeInvalidIdentifiers transform to make sure generated code is always parsable.
-
由 Jared Parsons 提交于
-
由 Julien Couvreur 提交于
-
由 Jason Malinowski 提交于
Refactor CodeModel hookup
-
由 Andy Gocke 提交于
Merge ref reassignment into 15.7
-
由 vsadov 提交于
-
由 vsadov 提交于
-
由 Jared Parsons 提交于
Fix netcoreapp2.0 use in TestUtilities
-
- 12 3月, 2018 2 次提交
-
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
Add some more tests for semantic model and IDE
-
- 11 3月, 2018 1 次提交
-
-
由 Dustin Campbell 提交于
Add Project.OutputRefFilePath and ProjectInfo.OutputRefFilePath
-
- 10 3月, 2018 11 次提交
-
-
由 Jared Parsons 提交于
This is referenced in the TestUtilities.csproj but for some reason not explicitly copied to the output folder here. Manually adding for now. https://github.com/dotnet/sdk/issues/2035
-
由 vsadov 提交于
-
由 vsadov 提交于
-
由 Jason Malinowski 提交于
This fails because in unit tests (unlike before) we are now creating a ProjectCodeModel. And now we're calling OnSourceFileRemoved when we try removing files, but the logic to create an actual CodeModelProjectCache is going to fail. If we don't have a cache, that's fine for these because we're only trying to update documents we've already handed out. If we don't have a cache, there's no documents to fix.
-
由 Jason Malinowski 提交于
-
由 Jared Parsons 提交于
-
由 Jason Malinowski 提交于
Hey, if the only thing they're doing now is new ProjectCodeModel, then we can do that in the base types where we're running unit tests anyways. It's harmless unless somebody actually asks for code model.
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
It's the only remaining stuff in CSharpProjectShimWithServices, so just move it down a layer.
-
由 Jason Malinowski 提交于
VisualStudioWorkspace had a virtual method to send a call over to the code model logic. Since we now have the requisite interface callable directly, we should just call it directly. It also saves us the trouble of passing a DocumentId only to re-decompose the type again.
-
由 Jared Parsons 提交于
This moves Roslyn to use the 2.1 SDK. This may appear to be moving the SDK version backwards from 2.2 to 2.1. In reality though it is a move forward. There was a brief time when the SDK switched their versions to 2.2 before reverting back to 2.1. Roslyn took a dependency on SDK in that small window. More details available here: https://github.com/dotnet/announcements/issues/57
-