| |
|
|
|
|
|
|
|
|
| Raymond Lewallen, L-3 Communications |
 |
685 Views ::
0 Comments :: Raymond Lewallen
|
|
L-3 Communications
For the last 11 years, Raymond Lewallen has worked with more programming languages than he can recall, but currently specializes in VB and C# as well as Sql Server. Working primarily in the public sector during his career, Raymond has designed and built several high profile enterprise level applications for all levels of the government.
Raymond currently works as a Senior Software Developer on a project for the Federal Aviation Administration as a contractor employed by L-3 Communications, Titan Group. Raymond is primarily a framework designer and developer.
He loves to talk about agile methodologies, patterns and practices, solution architecture and framework design in general.
|
|
|
|
|
|
|
|
|
|
|
|
| Raymond Lewallen - Continuous Integration |
 |
5984 Views ::
2 Comments :: Test Driven Development TDD / Agile, Raymond Lewallen
|
Continuous Integration The session will cover Continuous Integration using CruiseControl.Net. In this session, we will do an entire walkthough on setting up a continuous integration server. Tools that will be provided and covered are Subversion, Tortoise, NDepend, FxCop, NCover, NUnit (from TestDriven.Net), NAnt and CruiseControl.Net. We will cover each tool, what it does, why it is important and finally tying it all together into an automated build and integration process. Bring your laptop and walk away with an integration server running by the end of the session, including all the tools listed. Because of a single, small issue with running one of the tools under framework 2.0, we will be targeting framework 1.1. All tools listed are available under BSD or GPL, and are freely distributable and free to use.
|
|
|
|
|
| Raymond Lewallen - Strongly-Typed Session Wrapper |
 |
6369 Views ::
2 Comments :: Web Development Track 2, Raymond Lewallen, 9:00 AM
|
Strongly-Typed Session Wrapper
The session will cover building a strongly-typed session wrapper class. Session has always been an issue, because for one, its not strongly-typed, and secondly, you have to worry about developers just stuffing things into it and bloating it badly. With a wrapper class, you can use strongly-typed properties and store the entire class itself in session, thus only have a single key-value pair session variable for your users. You also enforce the use of the wrapper so that your session doesn't get out of control. Also, for those rare occassions when you might want to, your session wrapper class can also be serialized. We will also apply the same principle and pattern to cache objects and viewstate objects. Viewstate works basically the same as cache, just change this line and that line and there you go. We will be using Visual Studio 2005 and C#.
|
|
|
|
|
|
|
|
|
|
20 August, 2008
|
|
|
| |
|
|