And overall I think it went quite well. My Suave Sessions session was attended by a whopping ONE PERSON! I seem to recall his name is Mark, and he runs the Ft. Worth DNUG, so kudos to him for picking a great session! I know it wasn't sexy, but good session handling is something we should all be concerned about, certainly more so than getting an intro to DNN by the great Shaun Walker (who was presenting at the same time and whom I blame for stealing all my potential attendees). The good news is that it's recorded and Wrox will be hosting it on their web site, so all of you folks who made the unfortunate decision not to attend can still get the session. :)
Download the dotNetTemplar Session Management Module (for the Suave Sessions Session) - Even if you didn't see the session, you can start adding good session handling to your pages right away. There's demo web project there to show how to use it. If you want the demos from the presentation, let me know.
The EntLib session didn't go quite so well. Apparently, I should really check to ensure my old demos work before the day of when I give a repeat session, he thought, embarrassed. So I apologize again to all the troopers who toughed out the session with no running demos. Thankfully, the core concepts could still be expressed; it just wasn't as fun as it could be.
Download the ELMAH EntLib Exception Handler/Logger - This can be used to both specify ELMAH as a custom EntLib exception handler and use EntLib for your db access in ELMAH.
To use it, configure ELMAH as usual. If you want to use the EntLib logger, use GotDotNet.Elmah.EntLibErrorLog as the error log type instead of the standard SQL one.
To use the custom exception handler in EntLib, you just need to choose it in the EntLib GUI by loading the ELMAH DLL and picking the GotDotNet.Elmah.ElmahEntLibExceptionHandler as the handler type. It should look something like this in the standard config:
"System.Exception, mscorlib, Version=220.127.116.11, Culture=neutral, PublicKeyToken=b77a5c561934e089
"GotDotNet.Elmah.ElmahEntLibExceptionHandler, GotDotNet.Elmah, Version=2.0.50727.42, Culture=neutral, PublicKeyToken=58d6fbf09c89f721
"Elmah EntLib Exception Handler
The public key token will differ, though. I just reconditioned this for public use real quick like, so let me know if you have any issues.
Download the Slides From Both Presentations - In case you didn't get the DVD.
Other than that, I have to give some big kudos to David Walker and his team for putting the conference together. I've spoken at a number of code camp activities, and this was definitely one of the best organized and professionally done. I can't help but think that their not shunning sponsors (like Infragistics) helped in making it better. While I appreciate the academic ideal of trying to keep the code camp focused on devs sharing with devs, I think it is perhaps not in the best interests of anyone to shun sponsorship. The vendors who sponsor conferences like that have tools that are supposed to make devs lives better, so in my opinion, it only makes sense to welcome them in as long as it is done tastefully.
And no, I didn't just start thinking this now that I'm working for a vendor; you can ask Joe Healy--I was pushing for sponsors when I was helping organize the Tampa code camp. After all, it's not like Microsoft's stuff is free, and if the conference is about using Microsoft's technologies, why limit the vendor sponsors and topics to Microsoft? Microsoft does a lot to make software development better, and we all welcome that. I'm just suggesting the same thinking be extended to other companies who do the same thing.
Anyways, I didn't intend to rant about that really; I mainly wanted to say that David et al did a great job. It was good to visit my hometown again, and while I didn't make it out to Ron's Chli & Hamburgers Too for that sausage chili cheeseburger I've been missing, I still thoroughly enjoyed the visit. Tulsa certainly has been growing its dev community, and I hope they continue to do so.
That's it. Hope everyone's having a great day! Sorry bout the delay in getting this up.