- 21 6月, 2017 1 次提交
-
-
由 Heejae Chang 提交于
-
- 20 6月, 2017 3 次提交
-
-
由 Sam Harwell 提交于
Optimize fast path for "Use 'var'" code style
-
由 Andy Gocke 提交于
-
由 David Poeschl 提交于
Update IDE Test Plan with 15.3 features
-
- 18 6月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
Properly push events to the OOP side so that we know when things like solution-closing happens. Fixes #19768
-
- 17 6月, 2017 8 次提交
-
-
由 Jared Parsons 提交于
Include Commit in our NuGet package
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Ivan Basov 提交于
-
由 David Poeschl 提交于
-
由 Jared Parsons 提交于
-
由 CyrusNajmabadi 提交于
Move over to the new ITextImage platform API.
-
由 Jason Malinowski 提交于
Some performance and reliability fixes around file change tracking
-
- 16 6月, 2017 15 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
Switch back to the UI thread when cleaning up the solution in integration tests.
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
7x speedup on many SymbolFinder calls.
-
由 Sam Harwell 提交于
Do not allow ReadValue to return while a stream is still being read
-
由 David Poeschl 提交于
Use the new valid rename field tag id in integration tests
-
由 David Poeschl 提交于
-
由 Ravi Chande 提交于
Fix crash in VB type inferrer
-
由 David Poeschl 提交于
Accessibility for Inline Rename in the Editor
-
由 Ivan Basov 提交于
This reverts commit 2fba37a6.
-
由 Andy Gocke 提交于
By design, when data flow analyzes local functions it does so devoid of surrounding context and records possibly unassigned variables rather than reporting a diagnostic. Thus, all captured variables are expected to be marked unassigned during data flow analysis without reporting a diagnostic. However, reporting a diagnostic is not the only side effect of running data flow analysis. By calling virtual methods data flow analysis informs derived types of unassigned variables. While the diagnostic is suppressed and recorded, currently the virtual method is still called. This has negative consequences for region analysis, which considers these calls as indications of variables flowing out of the given region, which may not be the case for local functions. This PR changes data flow analysis to only call the ReportUnassigned virtual method if not inside a local function, excluding local functions from all unassignment reporting. Fixes #17165, #18347
-
由 David Poeschl 提交于
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems?id=391624&_a=edit - Inline Rename fields now consist of a themeable/customizable background, foreground, and border. The border is used in High Contrast. - Resolved and Unresolved conflict borders can now be themed & customized. - Resolved and Unresolved conflict borders now have different dash styles so they are distinct from each other and regular Inline Rename fields. The Dashboard shows a key indicating which type of conflict corresponds to which border dash style.
-
由 Jared Parsons 提交于
-
- 15 6月, 2017 9 次提交
-
-
由 Ravi Chande 提交于
Skip repl VSI tests
-
由 Jared Parsons 提交于
-
由 Jason Malinowski 提交于
Log telemetry if we see ITextBufferEdit.Apply() throwing exceptions
-
由 Ravi Chande 提交于
Failure tracked by https://github.com/dotnet/roslyn/issues/20219
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
Looks like there is still fall out from the licensing issue. VS integration tests still failing at 100% due to a timeout issue. Change them to not run by default while we look into this. Can still be run manually for testing with test vsintegration please
-
由 Jason Malinowski 提交于
Before this change we were immediately trying to add file watchers on the UI thread when we added a new analyzer. This can get delayed because of slow disks, or because the file watcher service's lock is held by a background thread. There's no reason to do it until we are actually observing and loading the analyzer, which typically happens on a background thread.
-
由 Jared Parsons 提交于
This change adds the git commit which produced the NuGet package to the description section. This makes it easy to both - Determine what source is included in a NuGet - Determine if a given change is included in our NuGet Lacking this only way to understand which commit produced a NuGet is to download the NuGet, crack open the binary and look at the version we embed into the PE. This allows us to see the version on the NuGet page itself.
-
由 Sam Harwell 提交于
-
- 14 6月, 2017 3 次提交
-
-
由 Ivan Basov 提交于
-
由 Jared Parsons 提交于
Move language settings after SDK import
-
由 CyrusNajmabadi 提交于
-