183 reputation
110
bio website
location Chemnitz, Germany
age 24
visits member for 2 years, 11 months
seen Nov 5 '12 at 7:31

I'm developer for Microsoft Office SharePoint 2010 since December 2010, and I'd like to share my knowledge about SP and other programming related topics on http://sharepoint.stackexchange.com and http://stackoverflow.com

Also, I am playing guitar since 2006 and I learned a lot about the instrument, it's history and other things I'd like to share with you on http://guitar.stackexchange.com


Jan
10
awarded  Popular Question
May
21
awarded  Notable Question
May
8
awarded  Popular Question
Nov
14
awarded  Teacher
Oct
21
comment call stsadm.exe programmatically (using System.Diagnostics.Process) doesn't seems to work
thanks man, it works like a charm. The tip with the InitAlertTemplatesFromFile() method is worth gold! I realized it this way in one neat line: new SPAlertTemplateCollection((SPWebService)SPWebApplication.Lookup(new Uri(SPContext.Current.Site.Url)).Parent).InitAlertTemplatesFromFile(@"path\alert‌​templates.xml");
Oct
21
accepted call stsadm.exe programmatically (using System.Diagnostics.Process) doesn't seems to work
Oct
21
comment call stsadm.exe programmatically (using System.Diagnostics.Process) doesn't seems to work
@bmm6o, I wasn't aware of the fact that using the object model is an option, too. I'll check out your answer, it looks intriguing. :)
Oct
20
comment call stsadm.exe programmatically (using System.Diagnostics.Process) doesn't seems to work
normally there's no plus; (And I highly doubt that would be a problem) I only did it here so it looks cleaner. Also thanks for the info with the " in front and at the end. But when using " in Verbatim-strings \" wouldn't work, instead using "" is the right way.
Oct
20
comment call stsadm.exe programmatically (using System.Diagnostics.Process) doesn't seems to work
@Matthias Neither. The "worked" object is a bool, and the Start() Method returns true every time. I don't see the shell-window as well, so I have no visual confirmation. (I tried to set CreateNoWindow on false; didn't work) And of course I check the prgFilePath with File.Exists() too.) The only indication I have that something is running, is that when debugging the code, the line with the WaitForExit() method takes a few seconds to skip. (about the same time the stsadm command needs to perform, when I do this manually) Is there some way to log the lines the stsadm.exe prints?
Oct
20
revised call stsadm.exe programmatically (using System.Diagnostics.Process) doesn't seems to work
grammar...
Oct
20
asked call stsadm.exe programmatically (using System.Diagnostics.Process) doesn't seems to work
Sep
26
awarded  Commentator
Sep
26
comment Search issue with People Picker when limited to select from one group only
@Vedran , yes it's similiar but still different. The other question is about improving the search results with FBA users; while this one is about the issue of the not working search when the PP selection is limited to a group. One solution to one question wouldn't solve the other, that's why I posted two questions. I hope you can understand my decision.
Sep
26
awarded  Benefactor
Sep
23
revised Search issue with People Picker when limited to select from one group only
added "EDIT"-region
Sep
23
comment improve People Picker search on a claims-based-authentification server (forms-based; FBA)
thanks, that helped to improve the search quality quite a bis. The wildcard doesn't work 100% the way I want but I guess that is not possible anyway. I have posted another yet similiar question about the PP here on SharePoint SE, you might want to check it out: Search issue with People Picker when limited to select from one group only
Sep
23
accepted improve People Picker search on a claims-based-authentification server (forms-based; FBA)
Sep
23
asked Search issue with People Picker when limited to select from one group only
Sep
13
asked improve People Picker search on a claims-based-authentification server (forms-based; FBA)
Aug
22
comment Deactivate email-notifications for SPLists only temporally (and programmatically)
Since it's monday and after 3pm (in my time zone) I took myself some minutes to test your code again with >Type="Computed"<, and it works like a charm. You should update your answer, in case someone else has this problem. (People are so lazy about reading comments, these days)