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

Handle virtual paths in FilePathResult #1201

Closed
javiercn opened this issue Sep 30, 2014 · 7 comments
Closed

Handle virtual paths in FilePathResult #1201

javiercn opened this issue Sep 30, 2014 · 7 comments

Comments

@javiercn
Copy link
Member

The current implementation doesn't handle "~/" paths. This requires something like Server.MapPath
See #1190 and #429

@danroth27
Copy link
Member

@loudej @davidfowl We need some way to figure out what file system we get.

@javiercn
Copy link
Member Author

This should be provided to the action result via a constructor or resolved within the action result

@javiercn
Copy link
Member Author

javiercn commented Oct 6, 2014

@davidfowl @Tratcher We need something like Server.MapPath exposed by the host, and this is probably also required for Razor, @pranavkm am I right?

@Tratcher
Copy link
Member

Tratcher commented Oct 6, 2014

@loudej? We were discussing this Friday.

@lodejard
Copy link
Contributor

lodejard commented Oct 7, 2014

Yes, we should cover that on Wednesday too

@javiercn
Copy link
Member Author

aspnet/Hosting#86

@javiercn
Copy link
Member Author

Last remaining work here is to actually support virtual paths using aspnet/Hosting#86

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

4 participants