Skip to content
This repository has been archived by the owner on Nov 1, 2018. It is now read-only.

Remove old packages #122

Closed
Tratcher opened this issue Apr 7, 2016 · 8 comments
Closed

Remove old packages #122

Tratcher opened this issue Apr 7, 2016 · 8 comments
Assignees
Milestone

Comments

@Tratcher
Copy link
Member

Tratcher commented Apr 7, 2016

These packages have been replaced. We left the existing ones until we could get tooling support and covert projects over. Remove these packages before RC2 ships, after https://github.com/aspnet/Coherence-Signed/issues/222.
Microsoft.AspNetCore.IISPlatformHandler
dotnet-publish-iis
And associated tests.
@Eilon @muratg

@muratg
Copy link
Contributor

muratg commented Apr 11, 2016

I guess this consists of removing these from the build script for now? GitHub and CI changes can probably come in later.

Don't forget to update packages.csv :)

@Tratcher
Copy link
Member Author

I'd rather remove the sources before RC2 ships to avoid confusion of what shipped. We should be ready this week.

@mjeson
Copy link

mjeson commented May 26, 2016

What are values for the LAUNCHER_PATH and LAUNCHER_ARGS mentioned in the new web.config ?

Been getting error when deploying the published files to IIS 8.5 (2012 R2). I dont see any executables in the published files.

Apologize for placing this question here. The announcements thread is locked.

@guardrex
Copy link
Contributor

@mjeson To use the publish-iis tooling. See the tools and scripts sections of project.json in the samples at: https://github.com/aspnet/cli-samples

To manually setup the web.config, see the IISIntegration sample at: https://github.com/aspnet/IISIntegration/tree/dev/samples/IISSample

@moozzyk
Copy link
Contributor

moozzyk commented May 26, 2016

%LAUNCHER_PATH% and %LAUNCHER_ARGS% are used by VS. publish-iis tool (if configured) will override them when you publish your application.

@mjeson
Copy link

mjeson commented May 27, 2016

Thank you for your help @guardrex and @moozzyk . I have my deployment working now. Here are my findings (also posted in stackoverflow).

After several hours dealing with them, I found there are two web.configs that we need to deal with: src\ProjectName\wwwroot\web.config and src\ProjectName\web.config . If you dont have the latter, VS2015 publish will generate one for you with %LAUNCHER_PATH% and %LAUNCHER_ARGS% by default.

To have the project run and debuggable locally under VS2015 via IISExpress, both web.config need to have the default value below. Replacing LAUNCHER_PATH and LAUNCHER_ARGS to something else causes VS2015 to hang indefinitely.

<aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false"/>

However, upon deploying to IIS (I am using 8.5 on WinServer 2012 R2), the value on src\ProjectName\web.config must be replaced with the following

<aspNetCore processPath="dotnet" arguments=".\ProjectName.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false"/>

If you are migrating from RC1, change the http bound directory as well to Project root folder, not wwwroot. Example: from C:\inetpub\ProjectName\wwwroot to C:\inetpub\ProjectName.

I am using RC2 Toolkit Preview 1

@moozzyk
Copy link
Contributor

moozzyk commented May 27, 2016

I don't think you need the config in the wwwroot - as per aspnet/Announcements#173 the web.config was moved to approot. If you configure publish-iis in your project.json like this: https://github.com/aspnet/cli-samples/blob/master/HelloMvcApi/project.json#L21-L29. You won't have to deal with %LAUNCHER_*% values - they will be taken care of for you.

@mjeson
Copy link

mjeson commented May 27, 2016

Thank you @moozzyk . You are awesome! I am missing that snippet from project.json. It works as expected now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants