Well the extension upgrade itself went smooth but project wise I wasn't aware at first there was any upgrading needed. Right clicking the Thunder theme still uploaded the themes to the project. Only after accidentily clicking the thunder explorer I was presented with a message that the installed Thunder Module wasn't updated.
Perhaps after the next update a redirect to an 'upgrade documentation/release page' instead of the standard documentation would be best cause it was only by accident I discovered the 'register widget' icon on the Solution Explorer as well.
So I went ahead and chose 'Install Sitefinity Thunder Module' which only worked on my remote site and not my working copy solution. (Maybe this is because I keep the .config files as a seperate project in the solution?)
And manually had to copy/paste back the changes into my working copy.
Error message: thunder.svc not found.
Manually browsing through the Sitefinity error.log gave me this:
Type : System.ServiceModel.EndpointNotFoundException, System.ServiceModel, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b77a5c561934e089
Message : The service '/Sitefinity/Public/Services/Thunder/ThunderService.svc' does not exist.
Source : System.ServiceModel.Activation
But nowhere in Sitefinity this error message is shown (not as a pop-up or on output).
Thunder and VisualStudio solutions/project.
There has been some small debate going on about what to do with configuration/storage folders, source control and deployment instances. Perhaps its time you guys do a best practices aka 'this works'.
Whenever I do a project that is image heavy, I tend to use the filestorage provider. Using 'publish' to deploy to various instances I keep the configuration files outside of the normal VS2010 project as well. So in a 'normal' solution I've got a minimum of 3 projects:
- ThunderTheme. (the thunder proj with the theme)
- SitefinityConfiguration (the configuration and storage folder)
- SitefinityWebApp. (the regular Sitefinity project without configuration or storage)
But the 'register a widget functionality' doesn't work 'solution wide' as stated. All I'm getting is an 'Could not find configuration folder' message and then followed by the empty register widget screen.
So you might want to change this in the documentation that registering a widget only works inside the project and not inside the solution.
And perhaps by default all error messages can be shown in output as well?