317 reputation
213
bio website
location
age
visits member for 2 years, 6 months
seen Jul 26 at 13:30

Long time .NET developer recently returned to SharePoint after running a mile following a brief brush with 2003. Things seem to be a little better these days at least.


Mar
13
awarded  Commentator
Mar
13
comment FBA and the People Picker
I'm using a custom provider which is written specifically for this application and hence I don't have ApplicationName fields in my database schema and am not using the application name property to filter results when accessing the database and therefore am not even reading this value from the configuration. I think this is the only use of this property? I tried with it hard coded to '/' anyway but no change. I didn't expect it to make any difference as it works everywhere else except the people picker on a site collection but worth a try anyway.
Mar
13
comment FBA and the People Picker
I have exactly the same configuration for PeoplePickerWildcards in the web.config for the SharePoint Web Application as I do for in the web.config for the Central Admin site where people picker is finding users from my custom provider. As I said I have very thoroughly checked configuration for both the providers. I'll update here if/when I eventually find the problem.
Mar
12
asked FBA and the People Picker
Feb
2
comment Managing WebParts with dependencies on Web scoped Features
I implemented the WebPartGallerySourceBase this morning and put the feature dependency logic into a gallery source base which a derived gallery source class can instantiate with 1-n dependencies. As you recommended, omlin, I added the check inside the web part as well to scupper those pesky advanced users! Thank you both for contributing to an elegant solution.
Feb
2
awarded  Scholar
Feb
2
accepted Managing WebParts with dependencies on Web scoped Features
Feb
1
comment Managing WebParts with dependencies on Web scoped Features
FeatureDependency won't work as the dependency already exists in reverse i.e. the web scoped feature is dependent on the site scoped feature containing the webparts. In fact they are mutually dependent, though for the site scope only with respect to these webparts. +1 because the custom WebPartGallerySourceBase seems like it could be an excellent solution, though I haven't implemented it yet I will let you know if it works. There is another good blog post on the subject from Chris O'Brien here - sharepointnutsandbolts.com/2012/01/…
Feb
1
comment Managing WebParts with dependencies on Web scoped Features
Thanks omlin. This is the sort of solution I envisaged but was wondering if there was a WebPart.OnAdding or similar event I could override to do the check. I know I could use a custom WebPartManager and override OnWebPartAdding but I want to keep this contained to the WebPart itself so it will apply on any page. +1 for the link to the T4 just because I am a big T4 fan and can think of lots of other applications of something similar.
Feb
1
asked Managing WebParts with dependencies on Web scoped Features
Jan
31
awarded  Tumbleweed
Jan
24
awarded  Supporter
Jan
24
comment Nested (inherited) content type and inherits false in 2010
I think you're right there. In reality it is even stranger than this. The behaviour is in fact different for three different configurations; TRUE, FALSE and not defined. That is if you don't set the attribute at all the behaviour, with respect to these subtleties at least, is slightly different again. I have resolved to using a Feature Receiver to fix up the fields on activation; we have to do this for Lookups which can't find their list anyway so... thanks for the research, if I get time I might try another run with the configuration you mentioned. Thanks for the extra research!
Jan
24
awarded  Teacher
Jan
24
answered Sharepoint Toolpart Values Not Being Retrieved
Jan
19
comment Nested (inherited) content type and inherits false in 2010
@PirateEric - I will happily defer to your better judgement as this is indeed my first question here in comparison to your quite epic rep. However, the tag 2010 was quite deliberate. To the best of my knowledge the issue surrounding the behaviour of Inherits attribute for ContentTypes is specific to 2010 and this problem would not have exhibited in the same manner in 2007..?
Jan
19
comment Nested (inherited) content type and inherits false in 2010
I have to some extent solved my problem although it isn't a true answer to my question as my current solution is not CAML based. The first step was to delete the Title field from the ContentTypes programmatically in a feature receiver. However now SharePoint handily recreates the Title field on the ListInstance, presumably as it is defined in the default ONET file. I then created a ListAdded event receiver, which deletes the Title field from the List and all ContentTypes within if the TemplateId matches.
Jan
19
awarded  Student
Jan
19
asked Nested (inherited) content type and inherits false in 2010