-
Notifications
You must be signed in to change notification settings - Fork 65
Add recommended virtual directory setup to docs #175
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In docs/diagnostics.md
# Diagnostics
There is an initial system to help diagnose commone issues that can be opted into. Currently, this is only available on the ASP.NET Framework application
There is a typo, the correct is "commons" instead of "commone" right?
8252a48
to
afe96d6
Compare
Removing the diagnostic code for now in favor of going down a more generalized approach for health checks: #176 |
afe96d6
to
df24bac
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we specify the two applications must be on different sites to prevent my issues on #174 ?
Recomendation: Ensure your two applications have the same virtual directory path and are hosted on different websites.
@gumbarros good catch. I've updated the recommendation |
Virtual directories must be the same between the core and framework app. This may not be obvious to users as they get started, but a number of issues have been filed around this. This change adds some docs to guide people to this.
Fixes #174