- 03 8月, 2017 1 次提交
-
-
由 Heejae Chang 提交于
removed semantic version tracking code which recently caused some issue on RPS test. this code is already removed from master (15.5)
-
- 01 8月, 2017 2 次提交
-
-
由 Ravi Chande 提交于
-
由 Ravi Chande 提交于
Breaks the internal GTD infrastructure into seperate symbols for determining the navigable symbol at the caret position and performing the navigation.
-
- 16 6月, 2017 1 次提交
-
-
由 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.
-
- 18 5月, 2017 1 次提交
-
-
由 Heejae Chang 提交于
state progress as below 1. StartCandidacyRequirementsTracking <- first time user user LB (only once per user) 2. HasMetCandidacyRequirements <- when requirement is met (only once per user) 3. AnalyzerEnabledFlight <- when the user accepted as flight group (multiple times until user take action) 4. InfoBarShown <- when info bar is shown (multiple times until user takes an action) actions user can take. (this can only happen once) 1. AnalyzerVsixHyperLine <- user choose to go to the link 2. NeverShowAgain <- user decide not to participate in the experiment if user choose to install vsix (this can only happen once - unless user manually reinstall the vsix...) 1. Installed 2. Uninstalled the first time user installed the vsix, we will report these extra info 1. DocumentDiagnostics - report only once per a document 2. ProjectDiagnostics - report only once per project these 2 report include count per errors and FSA status. these only report once and never report again.
-
- 13 5月, 2017 3 次提交
-
-
由 Fredric Silberberg 提交于
-
由 Fredric Silberberg 提交于
-
由 Tomas Matousek 提交于
-
- 11 5月, 2017 1 次提交
-
-
由 Fredric Silberberg 提交于
-
- 10 5月, 2017 1 次提交
-
-
由 Fredric Silberberg 提交于
-
- 09 5月, 2017 1 次提交
-
-
由 Fredric Silberberg 提交于
-
- 04 5月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 03 5月, 2017 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 01 5月, 2017 1 次提交
-
-
由 Jared Parsons 提交于
This is an automated migration of our project files to the new SDK / PackageReference. It is done using the tool located here: https://github.com/jaredpar/ConvertPackageRef
-
- 30 4月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 23 4月, 2017 1 次提交
-
-
由 Srivatsn Narayanan 提交于
-
- 20 4月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 18 4月, 2017 1 次提交
-
-
- 07 4月, 2017 1 次提交
-
-
由 Kevin Pilch 提交于
While investigating #17570, I discovered that we would sometimes create "deferred" Roslyn projects for .NET Core projects that just hadn't been asynchronously created yet. In *theory* that did no functional harm - they would just get closed and converted to real projects when the project system created the real project, but might as well not even bother creating them. While I'm here, clean up PR feedback from #17335.
-
- 22 3月, 2017 1 次提交
-
-
由 Jason Malinowski 提交于
We either don't use these, or pull them in from NuGet.
-
- 15 3月, 2017 1 次提交
-
-
由 Julien Couvreur 提交于
-
- 14 3月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 13 3月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 09 3月, 2017 1 次提交
-
-
由 Heejae Chang 提交于
also, now merged separate vs telemetry logger to one since telemetry activity is now obsolete. also remote host also now share logger since both is now on new API
-
- 07 3月, 2017 1 次提交
-
-
由 Daniel Plaisted 提交于
-
- 02 3月, 2017 1 次提交
-
-
由 Kevin Pilch 提交于
So, it turns out that when you AdviseSolutionEvents, the shell actually checks the same object for all of the related solution events interfaces to fire events to them. This meant that after commit e6a43cb5, we never actually received any IVsSolutionLoadEvents or IVsSolutionWorkingFoldersEvents. The impact of this is that we never called "FinishLoad" to populate the Roslyn workspace with the projects that had been loaded. Most features would appear to work, as we would load a project and it's dependencies when a file was opened, but we would then not load any thing that depends on it, so features like Find All References and Rename wouldn't work reliably. Fixes https://devdiv.visualstudio.com/DevDiv/_workitems?_a=edit&id=389698.
-
- 01 3月, 2017 1 次提交
-
-
由 Heejae Chang 提交于
-
- 24 2月, 2017 1 次提交
-
-
由 Kevin Pilch 提交于
In Lightweight solution load, we depend on IVsSolutionEvents.OnAfterOpenSolution being called to populate the workspace and create projects. However we were subscribing from VisualStudioProjectTracker, which we defer create until a project is opened. This meant we never got the event for the first time a solution was opened, and so we failed to populate the workspace.
-
- 23 2月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 10 2月, 2017 1 次提交
-
-
由 Heejae Chang 提交于
move down diagnostic analyzer executor down to workspace layer since all requires one now lives in workspace layer.
-
- 05 1月, 2017 1 次提交
-
-
由 Jared Parsons 提交于
This changes our build so it will no longer consider the GAC when resolving assembly references.
-
- 31 12月, 2016 4 次提交
-
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
Ensure that all *.*proj, *.props, and *.targets files are prefixed with the xml and copyright elements
-
- 29 12月, 2016 4 次提交
-
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-