Skip to content

Missing doc: How should paths starting with /_framework be resolved? #49816

@jhudsoncedaron

Description

@jhudsoncedaron

Help us make content visible

After a fruitless google search I searched dotnet docs for _framework and found only two hits, both kind of useless. I also tried C:\Program Files\dotnet>dir _framework /a:d /s which was also ineffective as nothing matches.

Describe the new article

dotnet watch works by injecting scripts with /_framework. This doesn't work properly when using a custom static file provider. (Which we use because of a different bug.) We can easily detect when we are running under debug environment and should resolve /_framework paths but no idea how to provide the files.

I suspect it's serving files out of C:\Program Files\dotnet but I have no idea how to find them.

Document outline probably works as follows:

When using a custom static file provider, dotnet watch doesn't work.

_framework should resolve to this (fill in) directory within dotnet shared runtime whenever the environment variable __ASPNETCORE_BROWSER_TOOLS is set.

To locate this directory on Windows, ...

To locate this directory on Mac OSX, ...

To locate this directory on Linux ...

Seems pretty short.


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

Metadata

Metadata

Assignees

Labels

area-commandlinetoolsIncludes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPIfeature-hot-reloadThis issue is related to the Hot Reload feaaturetriaged

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions