Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could Use the ApplicationHost.config in The Folder in Project #33

Open
MarkSky opened this issue Nov 20, 2017 · 3 comments
Open

Could Use the ApplicationHost.config in The Folder in Project #33

MarkSky opened this issue Nov 20, 2017 · 3 comments

Comments

@MarkSky
Copy link

MarkSky commented Nov 20, 2017

I would like to know if I can use the ApplicationHost.config file in the project folder?
Just like the Visual Studio 2017, the iisexpress will use the .vs folder in project not in C:\Users<user>\Documents\IISExpress\config\applicationhost.config

@madsoulswe
Copy link

My colleague made a PR =)
#36

@warrenbuckley
Copy link
Owner

Thanks @madsoulswe I will try & get to look at it as soon as I can

@phil-w
Copy link

phil-w commented Sep 30, 2020

I know I've used the extension 51 times without contributing, but that's kind of because it hasn't been working. I'm still not there.

However I have discovered a couple of things which may be of interest to others wading through the closed issues:

  1. The extension uses the default ApplicationHost.config for the machine, and it appears to take the first available AppPool from that to use for any sites it creates. That's not good if the machine happens to have a managed code pool or two kicking around. Setting the default pool to "not managed" doesn't fix it. I ended up deleting all the other pools, adding an un managed one and setting that as the default. That seemed to help somewhat.

  2. Depending on your machine history, the machine's ApplicationHost.config may have lots of interesting archaeology, and may not have stuff you're going to need such as AspNetCoreModuleV2. I WinMerged it with the one which Visual Studio creates because that one works, and this one didn't.

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

No branches or pull requests

4 participants