IntegratedMiddleware throws when Piranha is hosted in a Virtual Directory

[eloekset]

Like mentioned in #372, Piranha is not tested when hosted in a Virtual Directory.

There may be more unexpected behavior, but at least I've tracked down one bug, which I know how to fix.

It starts after adding support for empty url at line 53, so I can send a PR for that.

[eloekset]

I just wanted to update this issue with the results after building my own fork and trying to use it in a site hosted as a Virtual Directory within an Azure App Service.

The site starts up, but routing doesn't work as it should. At least I've confirmed that the /seed route defined in the SetupController doesn't work.

The error message that I find in the event log is:

System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\home\site\<virtual-directory-name>\seed'.

I'm not sure what this indicates, but it seems like Azure App Service tries to navigate to a folder, while instead ASP.NET Core should use this as a route. I will link to a new issue and send another PR if I find the solution to this.

[tidyui]

Hi! This error looks like you’ve published but haven’t included the seed folder in the published files! This is needed if you want to run the seed after deploy.

Best regards

[eloekset]

Thanks! You're absolutely right. The manager works fine, so there's obviously no routing issues.