Try our conversational search powered by Generative AI!

Filehandling: VirtualPathVersioningProvider vs. VirtualPathNativeProvider


I have had alot of problems using VirtualPathVersioningProvider as det default provider for Global files. (This is the default provider for both Page Files and Global Files when installing EPiServer CMS).

1. In combination with the coderesort project "Picture Gallery" I've got out of memory exceptions when adding large images (>2MB).

2. Storing .swf files. The files become corrupt.

Both problems where solved when I switched and used VirtualPathNativeProvider.

Has anybody experienced the same thing?

May 21, 2008 1:02

No, but It would be intresting to see a call stack (from UI or from log)...


May 23, 2008 10:21
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.