You do not need to add a provider of the virtual path ~/Views/ , which occurs automatically by agreement, and the above search paths are only the result of two viewing engines (Razor and Spark), which are slightly different from each other. Spark has the root path of the Views view already, when it tells Account\Logon.spark that it is already in the Views folder.
I have the feeling that your spark glances are not actually copied to Azure during packaging and deployment. It is similar to the MVC3 DLL, before they were there, you had to install them to copy locally in order to provide access to Azure.
If you rename the Azure package to a .zip file and open it to see if the views have been included in the content. If not, try highlighting one of the Spark files in Solution Explorer and check the properties. Set Copy to Output Directory to Copy Always , and then create and repackage your Azure project.
Your local bin folder in the project should also have a Views folder with the Spark views contained for validation.
Try downloading this package and see if it does the trick?
Hope that helps
Rob
source share