Hello Jaco De Villiers,
Can you check the AppManifest.xaml
- the file that identifies the packaged assemblies and the application entry point. Under the :
you can find the reference paths of the ExtensionParts
created by the Application Library Caching. This will allow you to check whether the application can access these paths and whether the zipped assemblies are actually placed in those folders.
Also, does the exception occur only when you deploy the application or can it be reproduced locally as well, while running the project by hitting F5?
You can have a look at this article
describing how to work with Application Library Caching and at this blog post
. That might also hep you narrow down the reason for this issue.
the Telerik team
Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat
for a walk through all the exciting stuff we ship with the new release!