Quantcast
Channel: Web Deployment Tool (MS Deploy)
Viewing all articles
Browse latest Browse all 663

NET.TCP EnabledProtocol with MSDeploy not working

$
0
0

Hello

I'm deploying a web application in my local IIS instance via MSDeploy. I need this web app to have the HTTP and NET.TCP protocols enabled in the "advanced settings". The zip archive has the following manifest.xml and parameters.xml files:

manifest.xml

<?xml version="1.0" encoding="utf-8"?>
<MSDeploy.iisApp>
  <iisapp path="WebAppName" />
</MSDeploy.iisApp>

parameters.xml

<?xml version="1.0" encoding="utf-8"?>
<parameters>
  <parameter name="Application Path" defaultValue="SiteName/WebAppName" tags="iisapp">
    <parameterEntry type="ProviderPath" scope="iisapp" match="WebAppName" />
  </parameter>
  <parameter name="Virtual Directory Path" defaultValue="D:\SiteName\WebAppName" tags="DestinationVirtualDirectory">
    <parameterEntry type="DestinationVirtualDirectory" scope="SiteName/WebAppName" />
  </parameter>
  <parameter name="EnabledProtocols" defaultValue="http,net.tcp">
    <parameterEntry type="DeploymentObjectAttribute" scope="application" match="application/@enabledProtocols" />
  </parameter>
</parameters>

I'm executing the command:

msdeploy.exe -verb:sync -source:package=webapp.zip -dest:auto -useChecksum

Everything is deployed with no errors, but the "enabled protocols" setting only contains the HTTP verb and no NET.TCP setting is added. Moreover the SiteName site has the net.tcp binding configured.

Both the NetTcpActivator and NetTcpPortSharing services are running.

What could be the problem?


Viewing all articles
Browse latest Browse all 663

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>