Create a new ASP.NET Core 1.1 Web Application targeting .NET Core using the project template. Right-click the project in Solution Explorer, and create a new publish profile using the Folder publish target. Right-click the resulting .pubxml file, and select Add Config Transform from the context menu:
The config transform file is nested beneath the root web.config file:
Upon opening the config transform file, I see the following content:
<?xml version="1.0" encoding="utf-8"?>
<!-- For more information on using web.config transformation visit https://go.microsoft.com/fwlink/?LinkId=125889 -->
<configuration xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform">
<!--
In the example below, the "SetAttributes" transform will change the value of
"connectionString" to use "ReleaseSQLServer" only when the "Match" locator
finds an attribute "name" that has a value of "MyDB".
<connectionStrings>
<add name="MyDB"
connectionString="Data Source=ReleaseSQLServer;Initial Catalog=MyReleaseDB;Integrated Security=True"
xdt:Transform="SetAttributes" xdt:Locator="Match(name)"/>
</connectionStrings>
-->
<system.web>
<compilation xdt:Transform="RemoveAttributes(debug)" />
<!--
In the example below, the "Replace" transform will replace the entire
<customErrors> section of your web.config file.
Note that because there is only one customErrors section under the
<system.web> node, there is no need to use the "xdt:Locator" attribute.
<customErrors defaultRedirect="GenericError.htm"
mode="RemoteOnly" xdt:Transform="Replace">
<error statusCode="500" redirect="InternalError.htm"/>
</customErrors>
-->
</system.web>
</configuration>
This transform clearly applies to the web.config, yet I was able to create it from the publish profile. The Add Config Transform option shouldn't appear in the publish profile's context menu.
mlorbetske
commented
7 years ago
Create a new ASP.NET Core 1.1 Web Application targeting .NET Core using the project template. Right-click the project in Solution Explorer, and create a new publish profile using the Folder publish target. Right-click the resulting
.pubxmlfile, and select Add Config Transform from the context menu:The config transform file is nested beneath the root
web.configfile:Upon opening the config transform file, I see the following content:
This transform clearly applies to the
web.config, yet I was able to create it from the publish profile. The Add Config Transform option shouldn't appear in the publish profile's context menu.