Changes:
- Replaces PackageLineup with the dependencies.props approach to manage package versions.
- Generate the csproj/fsproj files that go into template packages
- Remove the DependencyUpdater and PullRequestSubmitter tasks
- Remove bower.json and bowerrc from Microsoft.DotNet.Web.ProjectTemplates
- Set MyGet feeds via MSBuild instead of NuGet.config
- Upgrades to the functional tests
- Update Selenium
- Make it possible to run tests on macOS/linux
- Disable test parallelization
When the code lived in dotnet/templating, the 1.x, 2.0, and 2.1 templates all needed to sit side-by-side.
Now that this code builds from aspnet/templating, we're reorganizing the folder and branch structure to
match the aspnetcore runtime repos.
Branches:
rel/1.1.5 = Microsoft.DotNet.Web.ProjectTemplates.1.x
rel/2.0.3 = Microsoft.DotNet.Web.ProjectTemplates.2.0
dev = Microsoft.DotNet.Web.ProjectTemplates.2.1
Changes:
Remove the 2.0 and 1.x templates projects from this branch
- Had to add extra logic to track document structure changes so listeners could know if an event was on its way or not.
- Added and fixed some tests.
#1748
When the code lived in dotnet/templating, the 1.x, 2.0, and 2.1 templates all needed to sit side-by-side.
Now that this code builds from aspnet/templating, we're reorganizing the folder and branch structure to
match the aspnetcore runtime repos.
Branches:
rel/1.1.5 = Microsoft.DotNet.Web.ProjectTemplates.1.x
rel/2.0.3 = Microsoft.DotNet.Web.ProjectTemplates.2.0
dev = Microsoft.DotNet.Web.ProjectTemplates.2.1
SendAsync was using InvokeCoreAsync code to send messages. In case of exception InvokeCoreAsync is blocking and returns a task to the user so they can await for the remote call to complete. Any exception thrown is caught and used to fail the task returned to the user. SendAsync does not return a special task to the user so re-using InvokeCore resulted in swallowing exceptions. While SendAsync is fire and forget it actually should throw if the message could not be send and it was not happening.
While adding tests it turned out we did not test cases where Invoke/SendAsync/StreamAsync were invoked before starting the connection and this resulted in a NullReferenceException. I also fixed that.
- Today we use localhost which binds to both the ipv4 and ipv6 addresses.
ANCM never communicates over ipv6 so it's pointless. This should also properly crash
the process if the ipv4 address fails to bind (which we've seen reports in real applications for).