HutzelGutzel

104 reputation

bio	website
	location
	age
visits	member for	1 year, 6 months
	seen	May 17 at 8:43
stats	profile views	6

	104 reputation	bio	website		visits	member for	1 year, 6 months
6 badges		location			seen	May 17 at 8:43

summary answers questions tags badges favorites bounties reputation activity

56 Actions

suggestions reviews revisions comments badges posts accepts all

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)
Jun 7	revised	Add custom error handler at beginning of modules section in web.config (not manually) added 22 characters in body
Jun 7	comment	Add custom error handler at beginning of modules section in web.config (not manually) Thanks for your effort but I gave up the custom error handling httpModule approach. Didn't have the time to test your last update. But I read it a dozen times (and tested it ) that it has to be the first module in web.config. And that is not possible neither with SPWebModifications nor with the supplemental web.config approach. See my solution in my answer below
Jun 7	revised	Add custom error handler at beginning of modules section in web.config (not manually) deleted 700 characters in body
Jun 7	answered	Add custom error handler at beginning of modules section in web.config (not manually)
Jun 5	revised	Add custom error handler at beginning of modules section in web.config (not manually) deleted 7 characters in body
Jun 5	comment	Add custom error handler at beginning of modules section in web.config (not manually) Added the Module code in my question. If I debug, the code, HandleError is executed, but sharepoint delivers the standard exception page. However, if the module is placed as first module in web.config it works fine
Jun 5	revised	Add custom error handler at beginning of modules section in web.config (not manually) added 581 characters in body
Jun 5	comment	Add custom error handler at beginning of modules section in web.config (not manually) here's the citation from my question above: "The problem is that the custom error handler has to be placed before the standard handlers. If you don't, sharepoint handles the exception itself and delivers the standard exception page."
Jun 5	comment	Add custom error handler at beginning of modules section in web.config (not manually) That's really poor. So the only solution is to edit the web.config manually...
Jun 5	asked	Add custom error handler at beginning of modules section in web.config (not manually)
Feb 13	revised	How to do a (performant) check if postback is caused by my custom webpart? added 7 characters in body