This is a migrated thread and some comments may be shown as answers.
Extensions do not work with custom VirtualPathProvider
1 Answer 11 Views
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
John McDowall
Top achievements
Rank 1
John McDowall asked on 25 Sep 2009, 11:16 AM
The extensions make a physical file check on the filesystem for a given Asset, rather than using the VirtualPathProvider which has been registered with ASP.NET MVC.

Is there any plan to address this?

1 Answer, 1 is accepted

Sort by
0
Atanas Korchev
Telerik team
answered on 25 Sep 2009, 11:18 AM
Hi John McDowall,

You are absolutely right. We will do our best to use the VirtualPathProvider in the official release of Telerik Extensions for ASP.NET MVC.

Regards,
Atanas Korchev
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Tags
General Discussions
Asked by
John McDowall
Top achievements
Rank 1
Answers by
Atanas Korchev
Telerik team
Share this question
or