Tampa C# Meetup on forty-two

Gentle Introduction to MEF–Part Three

david@buksbaum.us (David Buksbaum) — Tue, 22 Nov 2011 18:00:00 -0500

At the Tampa C# Meetup on August 3rd, I presented this Gentle Introduction to MEF using the same project modified over three steps. This is Part Three, where I complete the application created in Part One and modified to use MEF in Part Two. This part will show MEF composing the application from multiple assemblies into one application at run time.

Gentle Introduction to MEF–Part Two

david@buksbaum.us (David Buksbaum) — Mon, 21 Nov 2011 12:00:00 -0500

At the Tampa C# Meetup on August 3rd, I presented this Gentle Introduction to MEF using the same project modified over three steps. This is Part Two, where I show the application created in MEF .

Gentle Introduction to MEF–Part One

david@buksbaum.us (David Buksbaum) — Sat, 20 Aug 2011 17:00:00 -0500

At the Tampa C# Meetup on August 3rd, I presented this Gentle Introduction to MEF using the same project modified over three steps. This is part one, where I show the application without MEF .

Patterns 101 - Factory Pattern

david@buksbaum.us (David Buksbaum) — Wed, 11 May 2011 17:00:00 -0500

Note: This is part of an ongoing series introducing patterns at the Tampa C# Meetup .

Purpose
#

The factory pattern, formally called the Abstract Factory Pattern, abstracts the creation of a concrete class.

factory

Patterns 101 - Observer Pattern

david@buksbaum.us (David Buksbaum) — Wed, 20 Apr 2011 18:00:00 -0500

Note: This is part of an ongoing series introducing patterns at the Tampa C# Meetup .

Introduction
#

No introduction to patterns is complete without the ubiquitous explanation of why we need patterns. Rather then re-invent this wheel, yet again, I will reference others and refer you to a couple books.

Using Code Contracts for Safer Code

david@buksbaum.us (David Buksbaum) — Wed, 20 Apr 2011 06:00:00 -0500

Note: This was presented to the Tampa C# Meetup on April 20th, 2011.

One of the greatest challenges in writing code is that nebulous time when the code is too complex to keep the flow all in your head, and when the debugger gets too much in the way for watching the state of your program as it runs. This is the coding twilight zone in which the quality of the code tends to drop as you add line after line of instrumentation to your code to find that spot where something goes wrong. For most of my code writing career I solved this by littering my code with lines like the following:

Managing Dependencies with NuGet

david@buksbaum.us (David Buksbaum) — Wed, 06 Apr 2011 06:00:00 -0500

Note: This was presented to the Tampa C# Meetup on April 6th, 2011.

Most large .NET projects will use a number of libraries and frameworks. Those dependencies of your project will have their own dependencies. To make it more complex, those libraries may depend on other libraries, and in some cases – on each other.