Changes:
* Update to latest core-setup dependencies (generated using https://github.com/aspnet/AspNetCore-Internal/pull/1830)
* Add a step which asserts that version.props and versions.details.xml are in sync
* Add PR check which ensures solution files are not broken
Two changes:
* Update packages to 3.0.0-preview3.$(buildnumber) per latest 3.0 plan from the PMs
* Update packages to use SemVerV2 like most other repos are doing. Preview 1 of the packages in this repo were released with SemVer v1 "3.0.0-preview-18579-0056". We didn't update to SemVer v2 like everyone else because semver v2 would have sorted as "older" than 3.0.0-preview-18579-0056. But, now that we're updating the prerelease label to "preview3", semverv2 packages should appear as newer than 3.0.0-preview-18579-0056.
- Changed the LiveShare model from posting its entire state after every ProjectSnapshotManager event to post just the event state and then maintain the project manager on the guest.
- Because of the recent design change to abstract `ProjectSnapshots` away from a Roslyn project I was able to remove all `ProjectSnapshot`/`ProjectSnapshotManager` custom LiveShare implementations to decouple ourselves from LiveShare's remote language service workspace.
- Changed how we detect remote sessions. Instead of relying on an internal API we now look for a specific UI context that only exists during a LiveShare guest session.
- Changed the project snapshot handle proxies to use `ProjectWorkspaceState` instead of directly transporting TagHelpers.
- Updated the `RazorGuestInitializationService` to use public file list APIs to pre-download ViewImports for Razor projects.
- Updated tests to consume new product bits.
aspnet/Razor.LiveShare#47
This change updates the following dependencies
- Microsoft.Extensions.DependencyModel - 3.0.0-preview-27330-4
- Microsoft.NETCore.App - 3.0.0-preview-27330-4
This change updates the following dependencies
- System.Text.Encodings.Web - 4.6.0-preview.19080.5
- System.Diagnostics.DiagnosticSource - 4.6.0-preview.19080.5
This change updates the following dependencies
- Microsoft.Extensions.DependencyModel - 3.0.0-preview-27329-4
- Microsoft.NETCore.App - 3.0.0-preview-27329-4
This change updates the following dependencies
- System.Text.Encodings.Web - 4.6.0-preview.19079.11
- System.Diagnostics.DiagnosticSource - 4.6.0-preview.19079.11
* Remove unused package versions
* Remove references to Html.Abstractions
Removing this package since it's from the aspnet/AspNetCore.
* Remove System.ValueTuple package inside remove
* Add versions.details.xml items from corefx
* Add Microsoft.NETCore.App
* Fill up Version.Details.xml
* Update dependencies
* Fix failing test
- Retargeted VisualStudio.Editor.Razor to point towards Visual Studio's versions of Roslyn (it lifts).
- VSCode depends on Microsoft.CodeAnalysis.Razor.Workspaces and that entire stack depensd on publicly available bits.
Updates our VSIX version numbering to 16.1 and removes some workarounds
for the version numbering.
This change is only for master, we're still building 16.x VSIXes in
other branches.
Fixes: aspnet/AspNetCore#6635
We're deciding to use semver1 for the prerelease version of 3.0 since we
shipped preview1 that way. We don't want to swap to semver2 and have
preview2 show up on nuget.org with a *lower* version than we had in
preview1.
We'll go back to semver2 after 3.0 goes RTM
This is a bit of a rework of how we initially set this up, but with more
forethought to how this will work in the project system. I have not yet
surfaced this through VS.
My immediate next step is to light up the component integration tests
and something like this is on the critical path to get that work since
we need a way to specify in tests that a document should be treated as
a component.
This change adds a set of workarounds that we need to enable publishing to
BAR from this repo.
1. Workaround the attempt to call the Execute task on every project
2. Move symbol publishing to its own step so that it keeps happening
3. Reenable BAR publishing
1. Our dev builds have a smaller build number than our official builds
because they were missing a digit. OOPS
2. The AssemblyInformationVersion was wrong. I'm not sure why this
workaround is required.