I have originally created custom PerformancePoint filters in SharePoint 2010 and I am now trying to deploy the filters in SharePoint 2013. I was able to successfully upgrade and deploy filters for everything except the ScriptDependency class in the filter custom control. In 2010, I have included external javascript files for the filter using the ScriptDependencies property of the custom filter renderer and specifying the assemby name and script location. These external javascript files were included as embedded resources within the same assembly as the custom renderer and everything worked as intended.
When upgrading to SP2013, I am not able to specify an assembly name for the script dependency anymore and have not been able to get the external javascript files loaded to the page in this manner anymore. My question is, A) How do I use the ScriptDependency class in SP2013? or B) What is the best way to load these external javascript files to the page?
Thanks!
