{"push_id":1084742524,"size":1,"distinct_size":0,"ref":"refs/heads/release","head":"d9fe7936c382980f02f163849237b9ced3c04395","before":"6a59d9d3d157be7e13f75fba2c8c56b7de0fec59","commits":[{"sha":"d9fe7936c382980f02f163849237b9ced3c04395","author":{"email":"2dd1590fd832a5e1c8567d718938b5e15c0e595b@microsoft.com","name":"N. Taylor Mullen"},"message":"Add support for net451 projects.\n\n- Previous to this any net451 projects that Razor-tooling would attempt to load would explode.\n- We now dispatch to ourselves within a users output to ensure that all dependencies are matched up correctly.\n- Added framework/configuration options to enable dispatching to properly find where our counterpart exists in a projects output.\n- Renamed bin directory option to build base path. With dispatching logic VisualStudio can't easily determine the users RID which is required for an output path to dotnet.\n- Replaced `AssemblyLoadContext` logic with `Assembly.Load` since we now always invoke ourselves in an environment where `Assembly.Load` is accurate. This way logic in the desktop process and non-desktop processes are identical.\n- Broke the `ResolveTagHelpersCommand` into 3 pieces so we can determine dispatching logic at the Program.Main level. This was required to use pieces of the `DotnetToolDispatcher`.\n- We utilize DotnetToolDispatcher for dispatch logic, this also ensures that we never have mismatched references for dotnet-razor-tooling in tools/dependencies sections.\n- Worked around an issue in `ProjectDependenciesCommandFactory` where configuration isn't properly flowed from constructor to `Create` method: https://github.com/dotnet/cli/issues/2512\n- Worked around an issue where binding redirects were not being created for executable desktop packages. This involved upping Newtonsoft.Json to 8.0.3: https://github.com/dotnet/cli/issues/2505\n\n#55","distinct":false,"url":"https://api.github.com/repos/aspnet/RazorTooling/commits/d9fe7936c382980f02f163849237b9ced3c04395"}]}