119 reputation
9
bio website
location
age
visits member for 2 years, 10 months
seen 9 hours ago

Sep
5
comment Search in private Exchange 2013 mailbox with Sharepoint 2013 Search Center
Federated Search to Exchange (use Exchange type result source) doesn't work. I've tried to add a result block for local sharepoint sites => no results. I also tried using that result source directly in "Search Results Web Part" => Exceptions, saying "Malformed Discovery Query". It seems that you can use an Exchange Result Source only in eDiscovery Center, which is documented here: technet.microsoft.com/en-us/library/jj683115(v=office.15).aspx
Sep
4
revised Search in private Exchange 2013 mailbox with Sharepoint 2013 Search Center
edited title
Sep
4
asked Search in private Exchange 2013 mailbox with Sharepoint 2013 Search Center
Jul
2
awarded  Curious
Jan
23
asked Business Connectivity Services vs. ADO.NET
Jan
9
awarded  Popular Question
Oct
24
revised Is updating a .resx file as an editor possible in Sharepoint 2013?
edited tags
Oct
23
comment Is updating a .resx file as an editor possible in Sharepoint 2013?
Edited my question. Forgot to mention, that sharepoint users / editors should be able to update the localized texts
Oct
23
revised Is updating a .resx file as an editor possible in Sharepoint 2013?
added 118 characters in body; edited title
Oct
23
asked Is updating a .resx file as an editor possible in Sharepoint 2013?
Sep
2
awarded  Popular Question
Nov
16
awarded  Tumbleweed
Nov
10
revised Get last major published version of items returned as DataRow (from SPSiteDataQuery)
deleted 4 characters in body; edited title
Nov
9
asked Get last major published version of items returned as DataRow (from SPSiteDataQuery)
Jun
21
asked Backup and Restore Sitecollection: users on target machine not existing
Jun
10
revised Enterprise built .wsp deployable to Standard Edition?
added 8 characters in body
Jun
10
comment Enterprise built .wsp deployable to Standard Edition?
Thanks, that's exactly what I meant. With "built" I meant the compiled and packaged .wsp file, not "developing". Your second point is absolutly right. If I include features of enterprise edition in my code and deploy it to a standard edition server, those things will not work.
Jun
10
accepted Enterprise built .wsp deployable to Standard Edition?
Jun
9
asked Enterprise built .wsp deployable to Standard Edition?
Jun
7
accepted Add custom error handler at beginning of modules section in web.config (not manually)