John Watson

Typemock are offering their new product for unit testing SharePoint called Isolator For SharePoint, for a special introduction price. it is the only tool that allows you to unit test SharePoint without a SharePoint server. To learn more click here.

The first 50 bloggers who blog this text in their blog and tell us about it, will get a Full Isolator license, Free. for rules and info click here.

I noticed this post on the GWB main feed regarding one person's complaints with health insurance in Arizona. I'm facing similar issues and I'm going to name the culprits.

For several years (2000-2007) I was co-owner of a small, regional consulting firm which at our peak had 10 full-time and 1 part-time employees on the payroll. We peaked out paying over 10K per month for health through Anthem BCBS in NH for a PPO plan and dental through Northeast Delta Dental, also in NH. A family health plan cost around $850/month for each employee. I used to call that the "hidden" extra employee - that's how much it cost in benefits annually. Over the last few years we operated, that cost rose to over $1000/month. Towards the end before we dissolved the company I was paying $1300/month from my own pocket for our family plan. This was a "middle of the road" plan - not the best and not the worst.

When the company was rolled into a larger software company we all went on Anthem BCBS/CA and began paying the employee-portion which was just under $500/month. I stuck it out the year that I said I would and when I left this summer the cost of COBRA for health, dental, and the VSP vision plan was up to $1700/month. That's just over 20K for a family plan insurance per year.

Figuring that it must be really high in California, I went shopping for health insurance in NH and for a comparable health plan (health only) it was nearly the same as the full package. For the time being, I'm just paying the COBRA and hating it.

In addition to the doubling of costs is the reduction in benefits. We can't go to any type of doctor visit or treatment where it's "just covered" - the billing costs are always high and we end up paying the difference out of pocket. Thank God we're all in good health with no issues - I can see a family going bankrupt if something bad happens.

The real kicker is that HEALTH INSURANCE COSTS MORE EACH MONTH THAN THE MORTGAGE ON A 4 BEDROOM HOME WITH 3+ ACRES OF LAND!!!

After setting up my Dell PowerEdge 2900 with Windows Server 2008 x64 and Hyper-V, I began the steps of creating virtual environments for things I work on. I already had a virtual SQL Server 2005 which was underutilized - 768 MB allocated RAM and one processor for my various development projects.

I wanted to set up Microsoft Office SharePoint Server (MOSS) as a "mostly" single server install with the exception that I wanted to use the existing SQL Server 2005 installation instead of the embedded SQL Express Edition. To prepare for this, I added a second named instance to the SQL machine so that all MOSS traffic would be isolated and separately configurable.

The steps I took were to use Hyper-V manager to add a second processor and bump the allocated RAM up to 1 GB. After rebooting the VM, I went into Add/Remove Programs, selected the existing "Microsoft SQL Server 2005" entry and clicked "Change". On the "Microsoft SQL Server 2005 Maintenance" dialog, click the blue hyperlink above the list box for "To install a new component, click here". Browse for the install media and work your way through to the SQL database engine and choose it to add another one. Give this one a name (e.g. SQLMOSS) and continue through. When finished, be sure to use the Surface Area Configuration Tool to enable remote TCP/IP connections.

In my case, I decided to partition out the virtual as follows:

• 1/2 the memory (512 MB) maximum allocated to the SQLMOSS instance
• 1/2 of remainder (256 MB) for the development/play default instance
• other 1/2 of remainder left for the OS (Windows 2003 R2)

Here's a screen-shot of task manager running inside the Hyper-V remote console window:

Note that this was taken after configuration but before installing MOSS 2007.

The beauty of this virtualized approach is that I can add (or remove) processors and RAM depending on usage patterns and bottlenecks.

If you have an existing Subversion tree on disk somewhere and you wish to move it to another machine, here's a quick 'n dirty way to do it. I'm pretty sure I read this before somewhere but couldn't find it however I decided to try it anyway. Basically, you install the same version of Subversion onto the new server, create an identically named repository ("svnadmin create foo" - assuming "foo" is the name of the new repo), replace the contents of the "foo" directory from the original machine and voila.

Of course, this is no doubt unsupported - the proper way to move a repository to another location is documented here.

I learned a few things the hard way and thought I'd pass them along in case it helps someone else. I bought a PowerEdge 2900 last winter planning on consolidating my five machines onto a single virtualized server. The PE 2900 has a pair of quad Xeons, supports up to 48 GB of RAM and 10 SCSI/SATA drives. Plenty of room for growth to support Windows Server 2008 and Hyper-V.

Doing my homework, I downloaded and burned the System Management Tools v. 5.5.0, A00 (5.4+ needed for Windows Server 2008 support) to have ready. I also upgraded my firmware to 2.4.3, rebooted, enabled Virtualization Technology in the BIOS and rebooted again.

I first tried running the upgrade from within Windows Server 2003 R2 SP1 x64 but kept finding that it was disabled. Since the PE was just a host for virtuals, I decided to try the System Build and Update Utility approach. Note that using this tool will reformat the boot partition and prepare it for the new OS. After choosing Windows Server 2008 Standard x64, SBUU prepared the installation and rebooted.

At this point you have to provide your own Windows installation DVD so I popped in my MAPS (Microsoft Action Pack Subscription) disc and good ol' Dell told me it wasn't valid. I didn't save the link but I found one post in the Dell support forums stating that their utility wouldn't recognize non-Retail discs. I "confirmed" this by trying an MSDN version that I downloaded with the same result. It would've been heIpful if Dell splashed this information all over the utility and documentation so customers would know! I then downloaded a trial edition ISO, burned it and tried it next...bingo!

Hope this helps!!

Just about a year ago I blogged that I had made some big changes professionally. Specifically that I and my business partner had negotiated the absorption our our small consultancy into a much larger software company. My partner had already been off "doing his own thing" with his own contract for 2+ years so it was a logical and smart way to unwind things and give everyone a home. Last July 1st I and five engineers joined another company. At the time I agreed to stay on for a year and...guess what? The time is up. July 31st is my last day as an employee and for the moment I am unemployed and completely free of all professional attachments for the first time in a quarter of a century.

What does a person do on their first official day off? My wife and I are heading to the beach to enjoy a fun, relaxing summer day. What are the plans beyond that? I'm going to take August off and enjoy the summer - in four weeks we help our oldest daughter move into a college dorm for her first year away from home. Not a huge shock because we've been through this once before with my son. But not only is she off to college but her sister (a.k.a. the "baby") is right behind - a junior in high school and already driving. Sigh.

Once fall kicks in after labor day I'll be looking for contract work for the time being - no doubt starting to line something up beforehand. Until then, I'm going to enjoy the remainder of the (short) summer here in NH and catch up on several home projects I've been putting off.

This post is part of a series which discusses the journey I took building a smart client membership application using Microsoft's Smart Client Software Factory (SCSF). You can navigate the entire series from here.

Views are probably the easiest artifact for smart client developers to understand and build. The fact that views are implemented as user controls and that there are recipes for generating them only lend to their ease of use. Finally, there is a lot of documentation and good diagrams about views to peruse. Even the model-view-presenter (MVP) paradigm is pretty well known or at least accessible with all the information available. What is perhaps a bit trickier is how to make multiple views work in concert within the SCSF architecture of shells, work items, and controllers.

Read the full article...

This post is part of a series which discusses the journey I took building a smart client membership application using Microsoft's Smart Client Software Factory (SCSF). You can navigate the entire series from here.

Work Items are one of the SCSF/CAB artifacts that causes angst amongst smart client developers. Part of the problem lies with the early whitepaper Architecting Composite Smart Clients Using CAB and SCSF and the early CAB examples reflecting the thinking of the p&p team at that time. The section entitled Use-Case-Driven-Strategy would have you create work items based upon each use case. In the banking case study, there would be 17 work items created! After pages and pages of details and diagrams on turning use cases into work items there's about half a page of text following that almost casually mentions another approach- mapping work items to business entities.

Read the full article...

I was setting up a new DNN installation at WH4L and received this error while running the installation wizard. I first tried manually cleaning things out and doing it again only to receive the same error. Turns out the trick is the file permissions on the newly installed modules under \DesktopModules aren't correct. When you receive the errors, simply open a new browser window, login to WH4L control panel, go to Security | File Permission and reset permissions for NETWORK SERVICE with the box check for subfolders. When that's finished, switch back to the installer wizard with the errors still showing and you can now click Next to continue and finish the installation.

This post is part of a series which discusses the journey I took building a smart client membership application using Microsoft's Smart Client Software Factory (SCSF). You can navigate the entire series from here.

The Members module is typical of SCSF business modules - it encapsulates the presentation and UI logic of a related set of business functionality. For the membership application I'm building this means:

• People
• Households
• Contact Info (phone, email, etc.)
• Addresses
• Relationships between all of the above

Read the full article...

This post is part of a series which discusses the journey I took building a smart client membership application using Microsoft's Smart Client Software Factory (SCSF). You can navigate the entire series from here.

Several years ago I developed a .NET code generation tool based on XSLT. It evolved over time and even had a front-end GUI to enable selection of various templates as well as database schema browsing. I had to hack my way through the INFORMATION_SCHEMA output of databases and developed an XML schema representation of the data model to drive the XSL templates. Of course, about six months after I had a working version Kathleen Dollard published her book Code Generation in Microsoft .NET and I could've saved myself a lot of effort if I'd just waited.

Read the full article...

This post is part of a series which discusses the journey I took building a smart client membership application using Microsoft's Smart Client Software Factory (SCSF). You can navigate the entire series from here.

The membership application is primarily about tracking and managing memberships in an organization such as a church or synagogue, small club or user group, sports team or league, etc. In the case of our church we need to track both individual persons and households. People may give us cell phone as well as home phone numbers and we mail our weekly newsletter to people who couldn't attend worship. Thus phone numbers can be associated with an individual person or a household and, of course, households have physical addresses for mailing purposes - we wouldn't mail two copies of a newsletter to a couple but rather one copy to their household address.

Read the full article...

This post is part of a series which discusses the journey I took building a smart client membership application using Microsoft's Smart Client Software Factory (SCSF). You can navigate the entire series from here.

My first approach was to fire up trusty old MS Access to build a single database even though I knew that sharing information wouldn't be easy yet is possible. I've used Access off and on since it was first introduced and even resurrected some screen shots (here, here, and here) using Virtual PC to run Windows for Workgroups 3.11.

Read the full article...

I am building a smart client application using free tools from Microsoft's patterns & practices team. The primary toolset is the Smart Client Software Factory, referred to as "SCSF", which is an integrated set of architecture guidance, templates and Visual Studio 2005 "recipes" that both makes the job easier (perhaps an oxymoron as you'll see) and gives you a solid framework to build a robust, scalable, professional-quality application. My aim is to document and share key points along the way.

The application I'm building is a membership system used to manage and engage members of a group or organization. Key features it has are:

• Flexible design enabling use by a variety of audiences.
• Easy to use, familiar user interface.
• Enable distributed management of data.
• Enough features to provide a compelling reason to use it.

I am doing this for two reasons - to build a low cost (free) application that my church can use to manage its membership and to satisfy my geek nature by building a serious application that others can use.

My wife is the administrative assistant for our church and when she took over the position she inherited a variety of "data sources" - a church directory consisting of names, addresses, telephone numbers and email addresses in an MS Word document, other assorted membership lists in their own MS Word documents, Excel spreadsheets used to track attendance and an Outlook Express address book used for email communication. Our situation is more common than you may realize even in today's electronic age. Non-profits operate on very low (or no!) budgets and volunteers who donate some time and effort. What started out for us as small organized lists has grown over time to become unmanageable and even outdated. Information has to be manually synchronized across multiple documents and inevitably things get missed and forgotten.

Here are the posts which document this journey:

1. Introduction (this post)
2. Background
3. Overall Design
4. Data Layer
5. Business Module
6. Work Items
7. Views
8. Services
9. Deployment Packaging

In the last eight months I have...

• Gone on a 2nd annual mission trip to western Louisiana with my two daughters to build a new home for a family of six who lost everything in Hurricane Rita 18 months before. [Editorial tirade: Funny how the media jackals are off to find fresh meat and nothing is mentioned about the people still struggling. If it is mentioned, it's always a brief aside about New Orleans and Hurricane Katrina and that's it. I guess Paris Hilton, Britney Spears, Lindsay Lohan, Nicole Richie, and God forbid, let's not forget about poor Anna Nicole are far more important headlines. Gimme a break!]
• Navigated the sale, along with my business partner, of our small consulting business to a software company. I along with 5 employees converted to full time employees joining the new company. For me, it's a change from being your own boss, a.k.a. "the boss" to being in an organizational chart that's 25 times larger.
• Re-doubled efforts to build a membership system for our local church, on the side (several more posts coming from this effort).