Comments on: SharePoint Branding Part 5 – Feature Improvements and Bugs http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/ After much frustration, it seems DEFAULT is the way to go... Thu, 02 Feb 2012 17:45:46 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: ThomasG http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/comment-page-1/#comment-79355 ThomasG Thu, 03 Mar 2011 14:58:41 +0000 http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/#comment-79355 Very good articles in Sharepoint CSS. Very good articles in Sharepoint CSS.

]]> By: Privi http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/comment-page-1/#comment-15881 Privi Thu, 10 Sep 2009 05:31:11 +0000 http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/#comment-15881 i have working similar to this but in my case when i am deactivating the feature the data remains same but it changes in the alignment...for example its displays the data's from horizondal to vertical. how to remove this dependency? i have working similar to this but in my case when i am deactivating the feature the data remains same but it changes in the alignment…for example its displays the data’s from horizondal to vertical. how to remove this dependency?

]]> By: Yaroslav Pentsarskyy’s SharePoint and .NET adventures » Performing SharePoint branding and it’s deployment http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/comment-page-1/#comment-13868 Yaroslav Pentsarskyy’s SharePoint and .NET adventures » Performing SharePoint branding and it’s deployment Mon, 06 Jul 2009 23:42:00 +0000 http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/#comment-13868 [...] Part 5 SharePoint Branding Part 5 – Feature Improvements and Bugs [...] [...] Part 5 SharePoint Branding Part 5 – Feature Improvements and Bugs [...]

]]> By: Sander de Koning http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/comment-page-1/#comment-3140 Sander de Koning Fri, 24 Oct 2008 10:17:02 +0000 http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/#comment-3140 Great post! Same issues :-( Great post! Same issues :-(

]]> By: Hannah http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/comment-page-1/#comment-797 Hannah Fri, 20 Jun 2008 09:15:51 +0000 http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/#comment-797 Next problem... im getting the following error - similar to the one you mention in your post: Feature '3ee204ab-d154-49fa-89c8-82e62118ed41' could not be installed because the loading of event receiver assembly "CleverWorkarounds_Test2.PimpMySharePoint2, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0e28904f8b90dfe0" failed: System.IO.FileNotFoundException: Could not load file or assembly 'CleverWorkarounds_Test2.PimpMySharePoint2, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0e28904f8b90dfe0' or one of its dependencies. The system cannot find the file specified. File name: 'CleverWorkarounds_Test2.PimpMySharePoint2, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0e28904f8b90dfe0' at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.Load(String assemblyString) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() .... Ive been round and round in circles with this now for the last 24 hours. The assembly is definately in the GAC on all my servers in the farm (ive tried it in the app bin folders as well); the feature deploys ok but i can't activate it without receiveing this message. Im not a programmer so feeling a little lost - Any further suggestions would be greatly appreceiated! Cheers Hannah Next problem… im getting the following error – similar to the one you mention in your post:

Feature ’3ee204ab-d154-49fa-89c8-82e62118ed41′ could not be installed because the loading of event receiver assembly “CleverWorkarounds_Test2.PimpMySharePoint2, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=0e28904f8b90dfe0″ failed: System.IO.FileNotFoundException: Could not load file or assembly ‘CleverWorkarounds_Test2.PimpMySharePoint2, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0e28904f8b90dfe0′ or one of its dependencies. The system cannot find the file specified.
File name: ‘CleverWorkarounds_Test2.PimpMySharePoint2, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0e28904f8b90dfe0′
at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()

….

Ive been round and round in circles with this now for the last 24 hours. The assembly is definately in the GAC on all my servers in the farm (ive tried it in the app bin folders as well); the feature deploys ok but i can’t activate it without receiveing this message.

Im not a programmer so feeling a little lost – Any further suggestions would be greatly appreceiated!

Cheers
Hannah

]]> By: Hannah http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/comment-page-1/#comment-791 Hannah Thu, 19 Jun 2008 13:54:31 +0000 http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/#comment-791 Having re-read the post again i now get what you mean - the FeatureId refers to the Office SharePoint Server Publishing Infrastructure feature. I am now a little greyer :) Having re-read the post again i now get what you mean – the FeatureId refers to the Office SharePoint Server Publishing Infrastructure feature.

I am now a little greyer

:)

]]> By: Hannah http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/comment-page-1/#comment-790 Hannah Thu, 19 Jun 2008 13:48:20 +0000 http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/#comment-790 Hi I am probably being really thick here - but im trying to figure out what you have used a feature activation dependency for? Im following your examples through and as i understand it you have created one feature (PimpMySharePoint) containing a masterpage, some css files and some images as well as one feature.xml and one provisionedfiles.xml file. So, what feature does the FeatureID for the activation dependency in feature.xml refer to??? With my understanding of your set up i am of course returning errors since there is nothing corresponding to the FeatureId. Please please explain as this is driving me mad! Many thanks Hannah Hi

I am probably being really thick here – but im trying to figure out what you have used a feature activation dependency for? Im following your examples through and as i understand it you have created one feature (PimpMySharePoint) containing a masterpage, some css files and some images as well as one feature.xml and one provisionedfiles.xml file. So, what feature does the FeatureID for the activation dependency in feature.xml refer to??? With my understanding of your set up i am of course returning errors since there is nothing corresponding to the FeatureId.

Please please explain as this is driving me mad!

Many thanks
Hannah

]]> By: CleverWorkarounds » SharePoint Branding - How CSS works with master pages - Part 1 http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/comment-page-1/#comment-249 CleverWorkarounds » SharePoint Branding - How CSS works with master pages - Part 1 Thu, 20 Mar 2008 23:36:08 +0000 http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/#comment-249 [...] Links: [Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part [...] [...] Links: [Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part [...]

]]> By: CleverWorkarounds » More SharePoint Branding - Customisation using JavaScript - Part 6 http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/comment-page-1/#comment-227 CleverWorkarounds » More SharePoint Branding - Customisation using JavaScript - Part 6 Wed, 12 Mar 2008 13:13:47 +0000 http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/#comment-227 [...] are a couple of minor points that I think are worth pointing out. One issue I covered back in my first branding series. If you deactivate this feature, the web part will not be removed from the web part [...] [...] are a couple of minor points that I think are worth pointing out. One issue I covered back in my first branding series. If you deactivate this feature, the web part will not be removed from the web part [...]

]]> By: CleverWorkarounds » SharePoint Branding Part 7 -The ‘governance’ of it all.. http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/comment-page-1/#comment-74 CleverWorkarounds » SharePoint Branding Part 7 -The ‘governance’ of it all.. Sat, 17 Nov 2007 09:40:01 +0000 http://www.cleverworkarounds.com/2007/10/27/sharepoint-branding-part-5-%e2%80%93-feature-improvements-and-bugs/#comment-74 [...] I recommend that all branding should be implemented as a SharePoint solution. Check article four, five and six for more info. For me personally, I consider that if an application developer does not [...] [...] I recommend that all branding should be implemented as a SharePoint solution. Check article four, five and six for more info. For me personally, I consider that if an application developer does not [...]

]]>