A project for creating a SharePoint 2010 branding wsp package, the package includes custom masterpage, minimalmaster(New!), stylesheet, logo and favicon. The wsp includes an activation and deactivation feature as well as a childweb eventreciever to apply branding on all subsit...
This is very helpful. The working example actually worked right away and the instructions were clear and helpful. I was looking to do something like this, but not finding clear instructions. This solution accelerated my understanding and now I am moving right along with my own solutins.
I really love this template it is awesome. Can I convert this template to VB.NET for you. I know there are a lot of people who would like this in VB.NET. Other than that your are awesome! Keep up the good work and I will be visiting your blog more frequently now.
A very nice solution on a very complex problem! All of a sudden you are able to control the branding...instead of trying to keep track of css files and where you did the last branding tweaks..and on which sub site etc...
Thomas - Next step - WYSIWYG editor running in Visiual Studio for SharePoint!
Any chance of extending this into SharePoint 2013? I am not a SharePoint guru, but have built various types of websites (PHP, ASP.Net, etc) and so i am porting my knowledge (as much as i can) to SharePoint 2013. There is alot of knowledge to be had and a Mtn Everest learning curve.
Does this solution solve the problem where you update your branding solution assets (i.e. a style sheet gets edited) but because the file already exists it doesn’t actually overwrite the old file? I have written a solutions for branding and in the past I had to turn of the branding feature, back the solution out, physically delete all the branding assets that were installed with the solution including the style library “customBrand” folder and master pages/page layouts and then force install the new bran solution and go through the rigors of turning everything back on. This is of course on a box that I didn’t dev the brand solution on and thus can’t use VS to deploy.
Sorry for the slow reply, missed it somehow.
This solution will replace the css on every deployment. I have done many many many changed to the css and it 'takes' every time.
In some production Environments, you may have to go in to the actual files and publish them, or it is only the admins who can access it. But, thats not due to this solution, it is SHarePoint at its best! :-)