Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
[wip] New UbiDiff Prototype (based on devops/build-on-2019) #2234
Conversation
…Starting with the display of diffs on the Create Pull Request page.
This will happen when the Pull Requests for Visual Studio extension isn't available.
Use VsDiffBaseFactory to conditionally create VsDiffBase.
| readonly Lazy<object> diffBaseServiceObject; | ||
|
|
||
| // store this in a static because this class does not seem to be a singleton | ||
| static object ChangesList; |
jcansdale
Feb 20, 2019
Collaborator
I'm surprised about this. I thought MEF components were singletons by default?
Holding back on committing csproj changes until I get a public NuGet package built.
…ng/VisualStudio into UbiDiffPrototypeOn2019
…oryCommitsClient.Compare instead.
|
Clearing up old PRs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Rework of the previous WIP (#2204) to use a NuGet package containing the UbiDiff work.