The MSBuild.SDK.SystemWeb.RazorLibrary SDK type only obeys OverwriteAppConfigWithBindingRedirects and does not have the enhanced functionality of MSBuild.SDK.SystemWeb and GeneratedBindingRedirectsAction which was added in #36 to address #34.
We should copy the base functions of MSBuild.SDK.SystemWeb.BindingRedirects.targets to the Razor SDK type.
In the case of an MVC based project, it is often required to have a separate web.config in the Views directory and any Area's Views directory.
In the Razor SDK this is handled with an item type of RazorAppConfigFiles and an XmlPeek / XmlPoke for each file in the target that updates the main web.config file.
Now that we have a common files mechanism, and the fact you may have such additional web.config files in the main 'head' application, it would make sense to make this a combined/common feature.
The
MSBuild.SDK.SystemWeb.RazorLibrarySDK type only obeysOverwriteAppConfigWithBindingRedirectsand does not have the enhanced functionality ofMSBuild.SDK.SystemWebandGeneratedBindingRedirectsActionwhich was added in #36 to address #34.We should copy the base functions of
MSBuild.SDK.SystemWeb.BindingRedirects.targetsto the Razor SDK type.In the case of an MVC based project, it is often required to have a separate
web.configin theViewsdirectory and anyArea'sViewsdirectory.In the Razor SDK this is handled with an item type of
RazorAppConfigFilesand an XmlPeek / XmlPoke for each file in the target that updates the main web.config file.Now that we have a common files mechanism, and the fact you may have such additional web.config files in the main 'head' application, it would make sense to make this a combined/common feature.