When I was at Lucent, everybody on the project was colocated in New Jersey, except one guy who was out in the Chicago area.  But he was the most important guy on the project!  We made this work, and one of the reasons was NetMeeting.  But Microsoft can't leave well enough alone.  NetMeeting has been superceded by Windows Meeting Space.  That's great except that Windows Meeting Space is available for Windows Vista only and there is no NetMeeting for Windows Vista.  In other words, if you want to do peer to peer collaboration with a mix of client operating systems, you're out of luck with these 2 programs.

Fortunately, Microsoft has quietly released Microsoft SharedView.  For some oddball reason, this is considered a component of the Microsoft Connect program.  But SharedView isn't in any specific to Microsoft Connect.  Instead, it is a collaboration program similar to NetMeeting and Windows Meeting Space and it runs on both Windows XP and Windows Vista.

SharedView has all the collaboration basics:

• create a meeting (requires a Windows Live ID)
• invite others (using any e-mail address)
• join a meeting
• share handouts
• share windows (including the desktop)
• take control of shared windows
• chat

Missing in all this is the whiteboard, video, and audio.  I'm not fond of how the handouts work.  When somebody shares a handout, all you can do with it is save it locally.  Things would be much easier if the handout was downloaded and launched using the associated program.

Ever since the new ASP.NET MVC framework was announced in October, posts about it have spread about it like wildfire through the .NET blogosphere.  There's usually at least 2-3 MVC stories a day that show up on DotNetKicks.

At the last Philly.NET code camp in January, there was standing room only for the ASP.NET MVC talk (see photo to the right).  Similar crowds have shown up at the HLS DevCon in Atlantic City, Central Jersey .NET & Fairfield/Westchester .NET user groups to hear about it.

With all the buzz going on about the new ASP.NET MVC Framework, I'm happy to announce a one day Firestarter event in NYC covering it on Saturday, June 7th!  Join us for a day in New York City to learn more about the ASP.NET MVC framework and see what everyone is all excited about.

At the ASP.NET MVC Firestarter, we’ll give you a quick tour of the framework, then peel back the layers and dive deeper into how it works.   As part of that, we’ll spend time discussing the design and development practices that lead to the creation of the MVC framework.  By the time you leave, you’ll have enough knowledge to get fired up and start building web applications with it.

More Info

When it comes to design patterns, the MVC is the granddaddy of them all.  First described in the late 70s, the MVC pattern remains very popular in the world of web applications today.  

ASP.NET MVC provides a framework that enables you to easily implement the model-view-controller (MVC) pattern for Web applications. This pattern lets you separate applications into loosely coupled, pluggable components for application design, processing logic, and display.
ASP.NET MVC is not a replacement for Webforms. It provides an alternative choice when designing a Web application. Using ASP.NET MVC offers the following advantages:

• It enables you to achieve and maintain a clear separation of concerns
• It facilitates test driven development (TDD)
• It provides more control over the URLs you publish in the application and over the HTML that is emitted by the application

Registration is now open. Don't wait as this will likely fill to capacity quickly:

Register Here!

Lunch will be provided.

Agenda:

· Intro to ASP.NET MVC & .NET 3.0/3.5   9:00-10:30

· Intro to MVC/MVP patterns   10:30-11:30

Lunch 11:30-12

· Intro to Test Driven Development 12:00-1:00

· Routing  1:00-1:30

· Controllers  1:30-2:30

· Break 2:30-2:45

· Views  2:45-4:00

• Strongly- vs. Weakly-Typed
• What’s the difference?
• Why would you choose one over the other
• Ways to effectively use Weakly-typed
• UI Helpers
• Overview of framework helpers
• Rolling your own
• View Engines
• Overview of WebForms ViewEngine
• File location/mappings
• Using “standard” ASP.NET stuff:  ASPX, ASCX, Master
• REST & AJAX – WCF, Dynamic Data, MVC AJAX  4:00-5:00

Here's what I've learned in a recent fight with a nasty object disposal bug.

Every .NET developer needs to understand object disposal.  Start with DG Update: Dispose, Finalization, and Resource Management for a complete discussion of the topic.

Carefully implement the pattern.  Here's the bug I had to deal with:

protected virtual void Dispose(bool disposing) {
    if (!disposed) {
        if (disposing) {
            // dispose of managed objects
            // dispose of unmanaged resources
        }
        disposed = true;
    }
}

Both the managed objects and unmanaged resources were being disposed of only when disposing was true.  The code should have been:

protected virtual void Dispose(bool disposing) {
    if (!disposed) {
        if (disposing) {
            // dispose of managed objects
        }
        // dispose of unmanaged resources
        disposed = true;
    }
}

What this bug does is interfere with finalization.  All of an object's resources that haven't already been released should be during finalization.  But, because the unmanaged resources were disposed of only when disposing was true, nothing was disposed of during finalization.

What's unusual about this bug is that you may never notice it or it may cause you to exhaust a resource and prevent your application from running.  If every disposable object is disposed of, then it doesn't matter that finalization doesn't do anything because there wouldn't be anything to do.  But what if you forget to call Dispose?  In that case the unmanaged resources will never be disposed of and you'll have a classic C++ style leak on your hands.

Whenever possible, use a using statement to ensure object disposal.

Note that there was a huge change between Visual C++ 2003 and Visual C++ 2005 regarding object disposal.  See Changes in Destructor Semantics for details.

I ran the Vista SP1 upgrade on an Asus V1S running Vista Business.  I was having no issues before the upgrade and haven't found any post upgrade.

Microsoft has bid $44.6 billion for Yahoo.  This is not a good idea because:

1. Microsoft and Yahoo are both struggling in search because their products are inferior to Google's.  Combining the two companies won't fix this.  Actually, Google is in a very dangerous position.  All Microsoft has to do is come out with a superior product.  Thanks to the zero cost of switching  search providers, Google could face an exodus.  While not an easy task, Microsoft has the resources to make this happen.
2. Yahoo is not a mining company.  When you buy a company like Yahoo you're mostly buying the workforce.  The only reasonable assumption is that the technical staff is highly anti-Microsoft.  Even with a retention program, people will leave in droves.  Your best people leave (because it's easy for them) while your weak people stay (for the opposite reason).
3. What is Microsoft going to do with all that non Microsoft technology at Yahoo?  If this comes to pass, hopefully they'll be sensible about this and maximize the return on prior investments.
4. Microsoft is highly profitable thanks, in large part, to its corporate customers.  Will Yahoo become such a distraction that they'll take their eye off the ball?  Windows, Office, the development tools, and the server products such as SQL Server are all in a strong position; the last thing Microsoft needs is to start losing momentum in those areas.
5. Microsoft is paying an approximately one third premium for Yahoo based on market pricing.  That's an extra $15 billion for a company in layoff mode.  Even for Microsoft that's real money.  Does that make sense?

Corporate mergers, especially big ones, have a long history not working out the way the suits plan.  Will Microsoft go from powerhouse to lost in the woods?

I put together a WCF REST over HTTP service and learned a few things along the way.

Sample Project

The best way to learn about WCF REST is to examine the sample project supplied by Microsoft.  This is available at Windows Communication Foundation (WCF) and Windows CardSpace Samples.  Once you unzip the download you'll find C# and VB sample projects at TechnologySamples\Scenario\PoxMessaging.  These simple projects demonstrate everything you need to know.

Creating Your Own Project

The Visual Studio project template for creating a service hosted by IIS isn't grouped with the WCF projects but is with the ASP.NET projects:

Once you have a project created, just follow the pattern in the sample and you'll quickly be ready to test.

Testing Your Project

The easiest way to test your project is to use Fiddler 2.  Fiddler 2 includes a tab that lets you form and send HTTP requests:

Just select your verb (GET, PUT, etc.), enter the service URL, enter your HTTP headers, paste your XML into Request Body, and press Execute!  Content-Type should be text/xml; Fiddler 2 will automatically calculate the Content-Length header for you.  The result will appear in the left pane; you can double click on the line and get a detailed look at the request and response using the Session Inspector.

HTTP Status Code 415 Unsupported Media Type

If you've been following along exactly, your service should be returning a HTTP Status Code 415 Unsupported Media Type.  This is because when the project was created in Visual Studio there was an assumption that SOAP would be used.  Switching to REST means changing the binding in the web.config file:

 <system.serviceModel>
  <services>
   <service name="MyService.Service" behaviorConfiguration="MyService.Service1Behavior">
    <!-- Service Endpoints -->
    <!-- use webHttpBinding for REST instead of wsHttpBinding -->
    <endpoint address="" binding="webHttpBinding" contract="MyService.IService">

Note that this page, which is supposed to list all the System-Provided bindings, doesn't mention webHttpBinding.

What happens if you drop a user's default database in SQL Server 2005 and the user then tries to use SQL Server Management Studio?  You get this crystal clear error message:

What to do?  If you have another working administrative login, then you simply need to use that to update the properties of the user that can't connect:

But what if the user that can't connect is the only administrative user?  In that case, you need to tell SQL Server Management Studio to connect to a different database on startup, which is done using command line options:

"C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe" -S SQLSERVER2005 -d master -E

Here's all the command line options:

After executing the above command, SQL Server Management Studio will come up without the object explorer (the tree view on the left) open.  But, it will be connected to the master database and will allow you to run queries.  To fix the user login so that the object explorer can be opened, simply run a query to change the user's default database:

sp_defaultdb 'SQLSERVER2005\dbuser', master

You will be then be able to open the object explorer by using File -> Connect Object Explorer...

Appendix - exact message (for search engines):

A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)

I set my laptop to dual boot Vista and discovered a some interesting things when I was done:

• The new operating systems was the default, when I wanted the original operating systems to be the default
• I had 2 operating systems with the exact same description (Microsoft Windows Vista)
• The selection timeout was 30 seconds
• My old friends boot.ini and bootcfg are history!

In Vista, BCDEdit replaces bootcfg.  I can list my operating systems simply by running BCDEdit in the shell:

C:\Users\Dave>bcdedit

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=C:
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
resumeobject            {7caf94b7-f303-11db-8342-fd19a316638c}
displayorder            {default}
                        {current}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=G:
path                    \Windows\system32\winload.exe
description             Microsoft Windows Vista
locale                  en-US
inherit                 {bootloadersettings}
osdevice                partition=G:
systemroot              \Windows
resumeobject            {94cd4dd2-a14c-11dc-b2fb-d72bdf6fa59c}
nx                      OptIn

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Microsoft Windows Vista
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {572bcd56-ffa7-11d9-aae0-0007e994107d}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {7caf94b7-f303-11db-8342-fd19a316638c}
nx                      OptIn

Because I booted the non default operating system, each operating system could be assigned a logical identifier (default, current).  Had I booted the default operating system, then the one know as current above would have a GUID as an identifier.

To change the boot order:

bcdedit /default {current}

This doesn't change the order the operating systems are listed in, it simply sets the default operating system to boot.

To change the description of an operating system:

bcdedit /set {94cd4dd1-a14c-11dc-b2fb-d72bdf6fa59c} description "Vista with Virtual Server"

Finally, to bring the timeout down something acceptable for Type A people:

bcdedit /timeout 5

The TechNet page referenced above isn't much more than the basic help you get with "bcdedit /?".  See the MSDN documentation at Boot Options for Driver Testing and Debugging for a tutorial.

This just in!  I stumbled across a really detailed BCDEdit Reference document from Microsoft.

The following code doesn't work; the exception message reads "Root element is missing.":

MemoryStream transformed = new MemoryStream();
XmlDocument doc = new XmlDocument();
XmlReader input = null;
XslCompiledTransform xslt = new XslCompiledTransform();

input = XmlReader.Create("Example.xml");
xslt.Load("Example.xslt");
xslt.Transform(input, new XsltArgumentList(), transformed);

try {
    doc.Load(transformed);
} catch (Exception ex) {
    Console.WriteLine("XmlDocument.Load failed: {0}", ex.Message);
}

Console.ReadLine();

It isn't a problem with the input file or the transform script.  The problem is that the XslCompiledTransform.Transform function leaves the stream position set to the end of the stream.  There's no root element because the XmlDocument.Load function thinks the stream has a 0 byte length.  The fix is to simply set the position to 0:

MemoryStream transformed = new MemoryStream();
XmlDocument doc = new XmlDocument();
XmlReader input = null;
XslCompiledTransform xslt = new XslCompiledTransform();

input = XmlReader.Create("Example.xml");
xslt.Load("Example.xslt");
xslt.Transform(input, new XsltArgumentList(), transformed);

// THE FIX
transformed.Position = 0;

try {
    doc.Load(transformed);
} catch (Exception ex) {
    Console.WriteLine("XmlDocument.Load failed: {0}", ex.Message);
}

Console.ReadLine();

The first ever Fairfield / Westchester Code Camp will be held on Saturday, November 10th, at the The University of Connecticut School of Business, Stamford Campus.  I'll be speaking on Debugging Tools for Windows starting at 4:15.  The last I heard, there are still a few seats available.

Hope to see you there!