PhysicalFileSystem constructor should only take absolute paths #17

Tratcher · 2014-09-10T23:26:23Z

Right now PhysicalFileSystem calls CallContextServiceLocator.Locator to get the IApplicationEnvironment.ApplicationBasePath. CallContextServiceLocator breaks Razor on desktop.

This service resolve should be done by the caller (StaticFiles middleware) so we don't have to use CallContextServiceLocator internally.

@pranavkm

The text was updated successfully, but these errors were encountered:

pranavkm · 2014-09-10T23:35:40Z

…e paths.

Tratcher added enhancement 1 - Ready labels Sep 10, 2014

Tratcher self-assigned this Sep 10, 2014

Tratcher added this to the 1.0.0-alpha4 milestone Sep 10, 2014

Tratcher added a commit that referenced this issue Sep 12, 2014

#17 - Remove smart-auto-base-path logic, it breaks razor. Use absolut…

4adb10d

…e paths.

Tratcher mentioned this issue Sep 12, 2014

Remove smart-auto-base-path logic, it breaks razor. Use absolute paths. #19

Merged

Tratcher added 2 - Working 3 - Done and removed 1 - Ready 2 - Working labels Sep 12, 2014

Tratcher closed this as completed Oct 20, 2014

Tratcher removed the 3 - Done label Oct 20, 2014

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

PhysicalFileSystem constructor should only take absolute paths #17

PhysicalFileSystem constructor should only take absolute paths #17

Tratcher commented Sep 10, 2014

pranavkm commented Sep 10, 2014

PhysicalFileSystem constructor should only take absolute paths #17

PhysicalFileSystem constructor should only take absolute paths #17

Comments

Tratcher commented Sep 10, 2014

pranavkm commented Sep 10, 2014