This repository was archived by the owner on Nov 1, 2018. It is now read-only.
publish-iis needs to understand portable vs. self contained apps #109
Comments
moozzyk
changed the title
|
Fixed in 1410a5a |
jkotalik
pushed a commit
that referenced
this issue
Dec 8, 2017
#109) * Antares blocks some windows APIs. We have use socket instead of calling GetExtendedTcpTable to check whether the backend is listening on given port. * Use socket instead of calling GetExtendedTcpTable to check if the backend process listens on given port since Antares blocks couple APIs * Antares blocks some windows APIs. We have use socket instead of calling GetExtendedTcpTable * update format * format change
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently publish-iis always sets
processPathattribute to the exe - e.g. (processPath="..\myapp.exe"). If the application is using the shared runtime there will be no .exe and the config file should look differently -processPath="dotnet" arguments="..\myapp.dll"Note that IIS runs using its own account and dotnet may not be on the path/accessible - we will probably need some guidance about this.
/cc @danroth27
The text was updated successfully, but these errors were encountered: