7.1 to 7.5 upgrade - Changes in API


The guide provided by EPiServer for migrating the VPP data into the database states:


Changes in API

If the site uses the Virtual Path Provider API, then you need to change your code as well, since most sites do not use this API including the Alloy sample site in EPiServer 7. The old API will work without throwing any exceptions, but will not return any files after you migrated. The old API was accessed using the ASP.NET API HostingEnvironment.VirtualPathProvider. Examples of using content-based files are available in the Developer Guide under the Content section in the CMS SDK.


The site we are upgrading is using HostingEnvironment.VirtualPathProvider. The guide says "you need to change your code as well" and referes to "Examples of using content-based files are available in the Developer Guide under the Content section in the CMS SDK". Where exactly is the code examples for the changes that has to be made? Icannot find the relevant section in the Developers Guide.

Feb 11, 2015 13:49

How to fetch and create new media data:


If you have any dynamic content controls that has properties where you select an image or document those properties wont be handeld by the VPP migration tool, you need to handle those links and map them to the coresponding ImageData.  


Feb 11, 2015 14:21

Thank you, but i solved the problem by using for example "UrlResolver.Current.GetUrl(file.ContentLink)" instead.

http://world.episerver.com/Blogs/Johan-Bjornfot/Dates1/2013/12/Working-with-Media-programmatically/ helped alot.

Feb 12, 2015 14:39
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
* 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.