问题描述
我们一直在努力了相当严重依赖VirtualPathProviders在ASP.NET应用程序。
We've been working on an application that quite heavily relies on VirtualPathProviders in ASP.NET.
我们刚刚来把这件事情直播服务器，以展示它，它看来，VirtualPathProviders简单的不工作的时，该网站是pre-编译！
We've just come to put the thing on a live server to demonstrate it and it appears that the VirtualPathProviders simply don't work when the site is pre-compiled!!
我一直在寻找已经张贴在这里变通方法：的，但到目前为止，我还没有能够得到上班，要么！ （嗯 - 它工作在Visual Studio的Web开发服务器罚款 - 只是没有在我们的IIS盒 - ！再次）。
I've been looking at the workaround which has been posted here: http://sunali.com/2008/01/09/virtualpathprovider-in-precompiled-web-sites/, but so far I haven't been able to get that to work, either! (Well - it works fine in visual studio's web development server - just not on our IIS box - again!).
在这里是否有人有问题的信息吗？难道是固定的.NET v3.5版本（我们目前正在为V2.0）？
Does anybody here have any more information on the problem? Is it fixed in .NET v3.5 (we're currently building for v2.0)?
推荐答案
不幸的是不正式支持。请参见下面的。
Unfortunately that is not officially supported. See the following MSDN article.
如果网站是pcompiled部署$ P $，由一个的VirtualPathProvider实例提供的内容没有被编译，并且没有的VirtualPathProvider实例由precompiled现场使用。
您所提到的网站是一个非官方的解决办法。我不认为它被固定在.NET 3.5 SP1
The site you referred to is an unofficial workaround. I don't think it's been fixed in .NET 3.5 SP1
这篇关于.NET VirtualPathProviders和pre-编译的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！