Configure IIS Website doesnt allow for net.tcp or net.pipe

kirk_quinbar · 5 March 2014 15:21

for v2.x of octopus I noted that you now have the ability to create IIS websites and application pools. it seems to have all the features we need except one. The bindings section only include http or https. for wcf services, you would also need to support net.pipe and net.tcp. Is this something that was already thought of or can you add it to the list for the next version. right now we have a custom predeploy script to handle the website creation, but if octopus can handle with something built in, then we can get rid of that step.

Paul_Stovell · 6 March 2014 02:59

Hi Kirk,

Happy to look at adding it since we’re working on that information now. You wouldn’t happen to know what the right syntax for a net.tcp binding in IIS is would you? It seems to be different to the way a HTTP/HTTPS binding is specified (*:80: for example)

Paul

kirk_quinbar · 6 March 2014 15:15

as far as the website bindings, net.tcp and net.pipe have no other configuration. they configure themselves.

I did think of something else though, is this bindings section you change at the website level or at the application level? the other thing we set (although we have a default now) at the application level is a property called “Enabled Protocols”. we will set this to “http,net.pipe,net.tcp”. That might be a different setting than the bindings, but is as important when dealing with wcf services. by default, you only get http and you have to add the other two supported protocols if you want to call wcf services on something other than an http channel (which we do).

robert_broomandan · 22 April 2014 02:50

Hi Paul,
I am also interested in this feature. I am hosting my WCF services under IIS/WAS, I have configured these sites with http and tcp bindings. I am currently using appCmd command after each deployment(see below). I have also attached two screen shots of what is the end result of these commands in IIS setting.

Thanks,
Robert Broomandan

1- %windir%\system32\inetsrv\appcmd.exe set app “serviceviceName/” /enabledProtocols:http,net.tcp
2- %windir%\system32\inetsrv\appcmd.exe set site “serviceviceName” -+bindings.[protocol=‘net.tcp’,bindingInformation=‘8006:*’]
0

Jonathan_Parker · 3 February 2015 06:52

Hi,

We’re currently evaluating OctopusDeploy at my workplace and also need to create net.tcp and net.pipe bindings in IIS. Is this feature being added or do we have to use a custom script?

Thanks,
Jonathan.

Paul_Stovell · 4 February 2015 22:53

Hi Jonathan,

You’ll need to use a custom script for it at the moment, I’m afraid. If it helps, here’s how we do the normal IIS configuration:

gist.github.com

https://gist.github.com/PaulStovell/3f4f265f3224296f0e4a

gistfile1.ps1

## --------------------------------------------------------------------------------------
## Configuration
## --------------------------------------------------------------------------------------

$isEnabled = $OctopusParameters["Octopus.Action.IISWebSite.CreateOrUpdateWebSite"]
if (!$isEnabled -or ![Bool]::Parse($isEnabled))
{
   exit 0
}

This file has been truncated. show original

Paul

gavinduffy1 · 25 February 2015 11:54

Hi guys,

I came across this problem recently as well and I made sure to save the script for future use. The below might help people in the future as a starting point

https://www.codingcurve.com/snippet/481/creating-iis-net-tcp-binding-using-powershell/

Gavin

Daniel_Basilio · 19 October 2015 15:03

Is this going to be added to the roadmap at all?

Damian_Brady · 20 October 2015 04:59

Hi Daniel,

There is an existing UserVoice suggestion for this feature, however it has relatively few votes. Because there’s currently a workaround, it’s unlikely to be a high priority.

We do keep track of UserVoice suggestions and continually evaluate where our time is best spent. If this becomes a common issue, it will float up the list.

Sorry it’s not better news.
Damo