The Bright Lights

Twitterlight updated to Silverlight RTW

sholstad — Sun, 26 Oct 2008 21:20:00 GMT

Twitterlight, THE browser-based Silverlight Twitter client, has been updated from Beta 2 to the official Silverlight 2.0 RTW. http://www.twitterlight.com...(read more)

WhereTheEL: Tracking the Chicago CTA "El" System

sholstad — Tue, 22 Jul 2008 18:24:00 GMT

Try the WhereTheEL alpha The past few weeks I have been spending some of my days creating a project we have discussed here at Clarity for quite some time: live tracking the trains of the Chicago "EL" system. Currently GPS data is not yet available...(read more)

Twitterlight updated with animating wrap panel

sholstad — Thu, 01 May 2008 17:33:00 GMT

Twitterlight has been updated with some new features that really up the usability of the app. http://www.twitterlight.com Defaulted the view to Public, so non-Twitter users can see data on page load Added profile pics back in Added link to Twitter page...(read more)

Twitterlight to Silverlight 2.0 Beta 1

sholstad — Wed, 02 Apr 2008 02:18:19 GMT

Ok ok, I've bitten the bullet and upgraded the Twitterlight Silverlight Twitter client to Silverlight 2.0 Beta 1. The Coding4Fun article has been updated with the latest source.

The client is live at twitterlight.com.

The major updates involved changing how some of the synchronous web service calls (authenticate, create TinyUrl) work within the app, now that all web references (woops, "service references" now) are asynchronous. Some XAML tweaks and minor code changes, and we're good to go.

View the initial post describing the article.

Facebook Developer Toolkit 1.6 Released on CodePlex

sholstad — Tue, 15 Jan 2008 17:40:13 GMT

We've released the latest version of the Facebook Developer Toolkit on CodePlex.

This release addresses a change to the Profile.SetFBML() method within the Facebook API. As of Thursday, Jan 17, 2008, Facebook will no longer accept the legacy version of this method, which allowed three versions of Facebook Markup Language (FBML) within the same parameter. The updated version of the Profile.SetFBML method will accept three separate parameters to limit unnecessary parsing, which will ease profile load times.

Using the Facebook Developer Toolkit, the previous call of

FBService.SetFBML(generalFBML, FBService.UserId);

now becomes

FBService.SetFBML(profileFBML, profileActionFBML, mobileProfileFBML, FBService.UserId);

A full example to test setting the profile FBML would look like:

    new protected void Page_Load(object sender, EventArgs e)
    {
        base.Api = FACEBOOK_API_KEY;
        base.Secret = FACEBOOK_SECRET;
        base.Page_Load(sender, e);

        if (!IsPostBack)
        {
            try
            {
                // Use the FacebookService Component to populate Friends
                Facebook.Entity.User u = FBService.GetUserInfo();
                Collection<Facebook.Entity.User> f = FBService.GetFriends();

                //Test Get/Set FBML (Profile parameter)
                string userMessage = string.Format("Hello, {0}, you have {1} friends!", u.Name, f.Count);
                FBService.SetFBML(userMessage, null, null, FBService.UserId);
                lblHelloWorld.Text = FBService.GetFBML(FBService.UserId);
            }
            catch (Exception)
            {
                // do error handling
            }
        }

This is a breaking change for existing code, which we felt was more logical than throwing a runtime exception. Post comments to the CodePlex site's discussion board if you have questions or comments.

Twitterlight: Silverlight 2.0 (Alpha) Twitter Mashup

sholstad — Tue, 08 Jan 2008 22:52:00 GMT

The Twitterlight Coding4Fun article has been published. I've added some updates, including url link support. Check it out!

All the source code is available, just make sure you add in references to the C1.Silverlight.dll.

Enjoy. - steve

=======================================================================

I ended up with a bit of bench time this week, so I've been working on two projects here at Clarity: Eating Jimmy Johns like it's going out of style, and immersing myself in Silverlight 1.1/2.0 and the accompanying control toolsets. Also my foos skills apparently never left.

Lately I've become a regular Twitter user (everyone: "hello, steve"), and was itching to play with the Twitter API, so I set out to create a Silverlight 1.1 mashup. I also wanted an auto-updating page to use for viewing my tweets, without having to install a desktop app.

Visit the Twitterlight Alpha.

My goals here were:

Experience the joy of working around Silverlight cross-domain call prevention. Btw, different ports in VS count as cross-domain too. This is achieved by hosting a local web service within your web project, which can in turn call external web services to marshal your Silverlight app its data. I'm not going to step through how to do this, as tutorials are popping up like crazy on this... although most refer to the "Add Silverlight Link" step as "magic". This goal was job one for me, because, while it's easy to see the initial draw to the beautiful designs created via XAML/Blend, unless true functionality can be added to these apps, this technology won't spread at the speed I'm hoping it will.

Test drive some emerging control sets. For starters, I've used ComponentOne's Sapphire Toolset Alpha. My cube neighbors can vouch for a bit of the learning curve you may experience tackling an alpha release component suite, but all in all I think C1 is doing a really nice job with their controls. Documentation and forum support are not great, but will come in time; and the coming of Blend support will only make using these controls easier. For now, I pretty much stuck with creating all C1 controls via C#, as Intellisense helps discover what's available for use.

Deploy a Silverlight app. Done and done. The apprehension I felt regarding moving away from good old "localhost" was unnecessary... The only major change required by my solution was to select the Silverlight project's Web Reference to the local web service, and change the "Web Reference URL" property to the new, deployed web service location. Copy, paste, deploy, foos.

You will need to install the Silverlight 1.1 Alpha September Refresh before running this... browser-wise I've tested in IE7 and Firefox 2.0. And of course, you'll need a Twitter account! I'll post the code in the near future for this app, in the meantime I plan to try some other toolsets.

Email me at sholstad@claritycon.com with feedback. I'm available on Twitter at http://twitter.com/steveholstad.

Upcoming additions:
  - TinyUrl and hyperlink support
  - Resize to full browser size
  - Search for and follow other Twitterers

Some Silverlight 1.1 / ComponentOne Sapphire Gotchas: (Updating as I go)
  - Textboxes would not accept text(!) unless FocusManager.Initialize(this) is called on page load.
  - Tab does not move focus to next control, it moves focus back to the browser (enhanced silverlight keyboard support is on the way)
  - Cannot create password-masked TextBox, and even the workaround posted cannot work due to an alpha bug in C1 control... this explains why I have the horrendous white background/white foreground password textbox in this demo...
  - C1 controls are not functioning as expected in Safari
  - Have heard reports that Vista x64 users can't view Silverlight content

Ding Ding! Sandcastle Oct CTP and the Sandcastle Help File Builder

sholstad — Tue, 27 Nov 2007 23:58:00 GMT

About a month ago, I began using the October 2007 CTP release of Sandcastle, Microsoft's offering for generating code documentation files from existing .NET 2.0 assemblies. The product will no doubt become the standard for generating your project's docs, replacing the previously ubiquitous NDoc (which is no longer supported, partly due to personal attacks directed towards chief dev Kevin Downs. What a nice way to support his volunteer efforts, huh?). Along the way I'll try to absolutely mangle a boxing metaphor... Here we go:

Round One: Me vs. The 'Castle Command Line

Carmen my love.. I dance so sweet for you!

My first encounter with Sandcastle was a knockdown, drag out tussle with lack of documentation and the joys of the command line, but I stuck it out in honor of our comrades from the 1980's and beyond... sarcasm aside, I was pleasantly surprised by the output of the tool. The docs were professional looking, and with some love could have been presentable to our clients if needed. (I was only looking to generate some docs to give our dev team an easy to way see how our previous committment to full code documentation was shaping up)

Decision: It was easy to tell this was going to become a powerful tool in the near future, but was still on the undercard with the hairy 300lb guy they pulled out of a bar... or maybe that's just the Cedar Rapids circuit?

Round Two: Introducing the Sandcastle Help File Builder

Would you like some punch to drink? Ha Ha Ha!

Once my team decided we needed a complete snapshot of our code-level XML documentation, I was thinking of the best way to create one help file for all assemblies, that included our custom comments and offered the functionality and usability NDoc had provided for so long, all without the painful command line monotony I envisioned. Lo and behold, Eric Woodruff's NDoc-style GUI appeared. Yes, I see the irony of Microsoft trumping an open source project with it's own offering, only to have a UI created that is a mimic of the original.... but hey, what works, lives.

The GUI tool relies on the Sandcastle 2007 October CTP, the HTML Help Workshop for building HTML help files, and the HTML Help 2.0 compiler just as the command line utilities do, but wraps all this in a clean, intuitive interface. I simple enabled our projects to produce XML document outputs (via the Project Property --> Build tab), and referenced these output files using the UI tool. It took about 40 minutes for the help documents to compile, but afterwards we had a web site and generated help docs for our team to review for missing comments. The web site is slow and clunky, but I've got a little man-crush going with the .chm. Puppy love I guess. And imagine the help a full .chm file could be to an incoming team member. At some point this will become a client-worthy offering that a lot of consultants may not take the time to produce, so this tool has become a nice value-add in my .NET toolbelt.

Decision: Sancastle with the CodePlex GUI are prepped for the spotlight, stay tuned to see how these products evolve.

Round Three: Gratuitous Bald Bull

My barber didn't know when to quit... Do you?

Okay, okay, I'm done... calm down.

Must-have Mike Tyson Punch Out references: http://en.wikipedia.org/wiki/Little_Mac#Little_Mac

OpenSocial Google API Release taking on Facebook

sholstad — Thu, 01 Nov 2007 12:34:00 GMT

Today is the target launch date for Google's OpenSocial, a programming API targeting social networks such as Orkut, LinkedIn, Friendster, Plazo & more. This move is intended to challenge the stranglehold Facebook currently is developing with social network programmers. I'm not much of a Facebook fan; nothing against the site itself, I just don't have the energy anymore to constantly monitor that type of site... I did check out Orkut, which seems to be wildly popular in Brazil & Asia, but much like David Hasselhof's singing career, totally missed the boat in the states.

Normally I don't post a lot of current event type news, but since Clarity has done so much to aid in Facebook development, thought that I'd put this out there to see if any of the Facebook developers would take a look at OpenSocial and see how it stacks up.

Right now I have the feeling that:

- Trying to develop on a standard platform for multiple proprietary network sites will be frustrating

- If the target sites themselves aren't taking off, then why would devs commit to developing for them?

If anyone checks it out, post a quick review here.

Google's OpenSocial

TechCrunch breaks the news

NY Times

Coding4Fun: YeahTrivia client & server using WCF & WPF

sholstad — Mon, 29 Oct 2007 23:43:00 GMT

I spent the last couple of weeks creating a posting for Coding4Fun's blog site, called YeahTrivia. The demo consists of a WCF client & server communicating via the wsDualHttpBinding channel. I used the article to learn quite a bit about implementing WCF to abstract service communication outside of an app's core code. Learning this new design pattern is a bit intimidating: I find that the hardest part in shifting your thought process is to take the first step... awhile back I attended Juval Lowy's WCF class, but until now haven't had time to apply it.

I'll be posting some of my favorite features of WCF and WPF as I continue to dive in. Be sure to check out the demo and tell me what you think.

To start, here are the config files of the client and server I used to create a wsDualHttpBinding communication channel:

Server:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <appSettings>
    <add key="BaseURI" value="http://localhost:8088/Trivia"/>
    <add key="QuestionLoadDelay" value="4000"/>
    <add key="QuestionTime" value="11000"/>
  </appSettings>

  <system.serviceModel>
    <services>
      <service name="Trivia.Server.GameServer" behaviorConfiguration="MyServiceTypeBehaviors">
        <endpoint address="http://localhost:8088/Trivia"
                  binding="wsDualHttpBinding"
                  contract="Trivia.Common.ITrivia" />
            <endpoint contract="IMetadataExchange" binding="mexHttpBinding" address="mex" />
        </service>
    </services>
      <behaviors>
          <serviceBehaviors>
              <behavior name="MyServiceTypeBehaviors" >
                  <serviceMetadata httpGetEnabled="true" />
              </behavior>
          </serviceBehaviors>
      </behaviors>
  </system.serviceModel>
</configuration>

Client:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <system.serviceModel>
        <bindings>
            <wsDualHttpBinding>
                <binding name="WSDualHttpBinding_ITrivia"
                         clientBaseAddress="http://localhost:8082/Trivia/"
                         closeTimeout="00:01:00"
                         openTimeout="00:01:00"
                         receiveTimeout="00:10:00"
                         sendTimeout="00:01:00"
                         bypassProxyOnLocal="false"
                         transactionFlow="false"
                         hostNameComparisonMode="StrongWildcard"
                         maxBufferPoolSize="524288"
                         maxReceivedMessageSize="65536"
                         messageEncoding="Text"
                         textEncoding="utf-8"
                         useDefaultWebProxy="true">
                    <readerQuotas maxDepth="32"
                                  maxStringContentLength="8192" maxArrayLength="16384"
                        maxBytesPerRead="4096" maxNameTableCharCount="16384" />
                    <reliableSession ordered="true" inactivityTimeout="00:10:00" />
                    <security mode="Message">
                        <message clientCredentialType="Windows" negotiateServiceCredential="true"
                            algorithmSuite="Default" />
                    </security>
                </binding>
            </wsDualHttpBinding>
        </bindings>
        <client>
            <endpoint address="http://localhost:8088/Trivia" binding="wsDualHttpBinding"
                bindingConfiguration="WSDualHttpBinding_ITrivia" contract="Trivia.Common.ITrivia"
                name="WSDualHttpBinding_ITrivia">
            </endpoint>
        </client>
    </system.serviceModel>
</configuration>

The client config contains some extra binding attributes that are optional, but I wanted to show you the exact files that were generated using the Svcutil utility. Use Svcutil.exe to generate a proxy class which, when created and added to your client project, is used to marshal calls via WCF to the service. To generate my client class, I started my service and ran the following at the command line:

svcutil /language:cs /out:ServerProxy.cs http://localhost:8088/Trivia

Not a complete solution, but should get you started in the right direction. For a working example, check out the article and let me know if you have any questions.

Apple to provide SDK & allow 3rd party apps on iPhone

sholstad — Thu, 18 Oct 2007 14:41:00 GMT

Wow, it's been awhile, and I apologize for the delay in posts. I took some time off to get married and head off to Greece... amazing times.

Now that I'm back, I thought I'd take a moment to pass on some interesting news: Apple is releasing a first SDK in February that will allow developers to create and install 3rd party applications onto the iPhone. This means some exciting times for you pretty Mac devs out there...

CNN's report makes a good point: that this is most likely a reactionary move to stop the bad publicity they've received from scores of iPhone owners looking for a more customized experience.

As some of you may know, I've been a late-adopter to many things Apple, but this is one more piece that may have me carrying an iPhone sooner than later (at least once an faster network is supported).

Comments welcome!

steve

Apple

iPhone

Mobile

WhatWG, W3C and HTML 5.0

sholstad — Thu, 16 Aug 2007 03:33:00 GMT

It's an interesting exercise every once in a while to take a look at the technologies we use in everyday development, and how they evolve over time. I started out writing HTML 4.0 & ASP 3.0 apps in high school, then watched as .NET 1.0, 1.1 and 2.0 became entwined in our vocabulary. Sitting here tonight, I'm writing some test apps using VS 2008 Orcas and HTML 4.0. Wait a tic, what happened with HTML's progression? Think of all the incredible web technology that has sprouted in the last 10 years: it's all been so exciting and glittery that everyone was deked into advancing other areas like scripting, AJAX & CSS. The last release of an HTML spec was released in July 1997. I'm not here to trash a standard we've all learned to love, but everyone who's ever programmed a web page can see some improvements could be made: think "DIVitis", for one. Surprised it took this long? Me too.

The cavalry is coming. The WhatWG (Web Hypertext Application Technology Working Group) was formed by an association of Apple, Opera & Mozilla browser vendors and independent web developers, with a goal of updating the hypertext markup language specs to support some much needed updates. The group formed in 2004 after they became concerned about the W3C's lack of direction and support for the everyday developer. A major concern for me is the fourth name you don't see as a founder of the WhatWG group. Microsoft IE definitely is the elephant in the room when we're talking about upgrades and standardization. The good news is that the W3C has picked up the call, and the WhatWG and W3C working drafts of HTML 5 are now advancing in tandem. Still, the WhatWG blogs state that the spec is being developed with IE compatibility in mind, and that many features can be supported in IE using JavaScript workarounds...what a potentially painful annoyance for developers. Standardization: so close, yet so far away.

On a quick side note: Some writers have pointed out that until the next generation of browsers update their HTML rendering engines, any upgrades to the spec are useless; It's pretty obvious to me that this is a classic "cart before the horse" worry... how are vendors supposed to support a format that is not yet formalized? Plus, being that three of the big four browser vendors founded the group is a clear sign that they are preparing to make upcoming browsers support the latest HTML.

The HTML 5.0 spec is being developed using a three-pronged approach. WhatWG sums the branches up nicely:

The work is currently split between three specifications.

Web Forms 2.0 is targeted to the common needs of web authors. Advanced widgets like RTF controls, menus and toolbars are the domain of Web Applications 1.0. These drafts are in active development. Web Forms 2 is nearing maturity; proposals are currently being discussed and specified for Web Applications 1.

Web Controls 1.0 is intended to add functionality to Javascript and CSS that aid the creation of custom widgets. However, this will be influenced by the design and implementations of XBL2, and so will not be available in the near future.

I'm not diving into a code sample here, because A) the constructs are still changing frequently, b) c'mon, I'm planning a wedding here, and c) Elliotte Harold does a really nice job of it here.

You can start developing sites using these standards once browsers begin to support them, even though the final recommendation won't come until the implementation is complete; be wary of changes until then. Keep an eye out for browser betas that allow testing of these new capabilities. The spec is fully backward compatible, so old browsers will continue to display content as expected.

Some references:
Elliotte Harold's review of HTML 5.0
WhatWG's FAQ Blog
WhatWG's working spec
W3C's working spec

HTML HTML 5.0 W3C WhatWG Web Programming ASP

Using AppDomain to Load and Unload Dynamic Assemblies

sholstad — Thu, 28 Jun 2007 23:56:00 GMT

Recently a project I was working on required us to dynamically load an assembly at runtime, and invoke a method on the newly loaded assembly. After we had this working, I noticed that when we tried to then load a newer version of the dynamic assembly, the newer bits weren't being picked up, and old code was executing. Time to investigate a bit further:

I came across a great article by Jon Shemitz that pointed me in the right direction. AppDomains are a powerful concept in .NET, however as most applications you write live within a single AppDomain, you may not have noticed them before. My problem was that in .NET, you cannot simply unload an assembly directly. However, if we were to create a new AppDomain, load our dynamic assembly within it, call the methods needed, and then unload the AppDomain, we could load, unload, update versions and reload until our hearts content. The final piece of our puzzle (that we already had in place) is to use an interface to allow us the ability to invoke methods on the loaded assembly from our manager executable.

The solution I've created to demonstrate this concept uses four projects:

AppDomainLoad: A basic console application that simply news up an instance of the Manager class and calls the entry method.

WorkerShared: This project holds any objects that will be used by both the Manager and Worker classes. This is the only assembly that will be loaded by both AppDomains. Our shared interface, IWorker, lives in this project. A utility class calls AppDomain.CurrentDomain.GetAssemblies() to let us know what really is being loaded at runtime. This is a handy method to use, even in standard single AppDomain applications, to ensure you only load what you need.

WorkerManager: The .dll that creates a separate AppDomain, loads an instance of the dynamic assembly, and casts this instance to the IWorker interface. After all this, the Manager simply calls a method available from the interface. Once the work is complete, the AppDomain is unloaded, which drops any assemblies loaded within the worker domain.

DisconnectedWorker: Where the rubber hits the road, this project executes the actual work. The worker class a) implements the IWorker interface b) derives from MarshalByRefObject, which allows access to objects across domain boundaries (because these interactions are basically remoting under the covers), and c) is marked as Serializable.

One final note, after building the projects, I placed the WorkerShared.dll and DisconnectedWorker.dll bits into the C:\BlogProjects\AssemblyPool directory. This is only to simplify the project code; your project can locate these assemblies however you need. For this example, create the directory and drop the assemblies.

Here's the example code. The key classes' code is shown below. Let me know if you have any questions.

IWorker interface

namespace WorkerShared
{
    public interface IWorker
    {
        // Define required methods:
        void DoWork();
    }
}

WorkerManager

using System;
using WorkerShared;

namespace WorkerManager
{
    public class Manager
    {
        private const string CONFIG_ASSEMBLY_POOL = @"C:\BlogProjects\AssemblyPool";
        private const string CONFIG_DYNAMIC_ASSEMBLY_PROJECT = "DisconnectedWorker";
        private const string CONFIG_DYNAMIC_ASSEMBLY_FULLY_QUALIFIED_NAME = "DisconnectedWorker.Worker";

        private const string FORMAT_WORKER_DOMAIN_FRIENDLY_NAME = "Dynamic Worker Domain";
        private const string FORMAT_WORKER_DOMAIN_CREATED = "Created '{0}' AppDomain";
        private const string FORMAT_WORKER_DOMAIN_UNLOADED = "Unloaded '{0}' AppDomain";
        private const string FORMAT_WORK_COMPLETE = "All work complete.";
        private const string FORMAT_START_ASSEMBLIES = "Starting Assemblies Loaded:";
        private const string FORMAT_END_ASSEMBLIES = "Post-unload Assemblies Loaded:";

        public void RunAppDomainExample()
        {
            // Show current assemblies before we start:
            Console.WriteLine(FORMAT_START_ASSEMBLIES);
            Utilities.WriteCurrentLoadedAssemblies();

            // create display name for appDomain
            string workerName = string.Format(FORMAT_WORKER_DOMAIN_FRIENDLY_NAME);

            // Construct and setup appDomain settings:
            AppDomainSetup ads = new AppDomainSetup();

            ads.ApplicationBase = CONFIG_ASSEMBLY_POOL;
            ads.DisallowBindingRedirects = false;
            ads.DisallowCodeDownload = true;
            ads.ConfigurationFile = AppDomain.CurrentDomain.SetupInformation.ConfigurationFile;

            // Create domain
            Console.WriteLine();
            AppDomain workerAppDomain = AppDomain.CreateDomain(workerName, null, ads);
            Console.WriteLine(FORMAT_WORKER_DOMAIN_CREATED, workerName) ;

            // do work on proxy
            IWorker workerInstance =
                (IWorker)
                workerAppDomain.CreateInstanceAndUnwrap(CONFIG_DYNAMIC_ASSEMBLY_PROJECT,
                            &nbs p;                           CONFIG_D YNAMIC_ASSEMBLY_FULLY_QUALIFIED_NAME);

            // Execute the task by invoking method on the interface instance
            workerInstance.DoWork();

            // Unload worker appDomain
            AppDomain.Unload(workerAppDomain);
            Console.WriteLine(FORMAT_WORKER_DOMAIN_UNLOADED, workerName) ;
            Console.WriteLine();

            // Show current assemblies before we start:
            Console.WriteLine(FORMAT_END_ASSEMBLIES);
            Utilities.WriteCurrentLoadedAssemblies();

            Console.WriteLine(FORMAT_WORK_COMPLETE);
            Console.ReadLine();
        }
    }
}

DisconnectedWorker

using System;
using WorkerShared;

namespace DisconnectedWorker
{
    [Serializable]
    public class Worker : MarshalByRefObject, IWorker
    {
        public void DoWork()
        {
            // Show the assemblies loaded in this appDomain
            Utilities.WriteCurrentLoadedAssemblies();
        }
    }
}

Utilities

using System;
using System.Reflection;

namespace WorkerShared
{
    public static class Utilities
    {
        public static void WriteCurrentLoadedAssemblies()
        {
            Assembly[] assemblies = AppDomain.CurrentDomain.GetAssemblies();

            foreach (Assembly assembly in assemblies)
            {
                Console.WriteLine("Loaded: {0}.", assembly.ManifestModule.Name);
            }
        }
    }
}

Payday: The Project Output

Starting Assemblies Loaded:
Loaded: mscorlib.dll.
Loaded: Microsoft.VisualStudio.HostingProcess.Utilities.dll.
Loaded: System.Windows.Forms.dll.
Loaded: System.dll.
Loaded: System.Drawing.dll.
Loaded: Microsoft.VisualStudio.HostingProcess.Utilities.Sync.dll.
Loaded: AppDomainLoad.vshost.exe.
Loaded: System.Data.dll.
Loaded: System.Xml.dll.
Loaded: AppDomainLoad.exe.
Loaded: WorkerManager.dll.
Loaded: WorkerShared.dll.

Created 'Dynamic Worker Domain' AppDomain
Loaded: mscorlib.dll.
Loaded: Microsoft.VisualStudio.HostingProcess.Utilities.dll.
Loaded: DisconnectedWorker.dll.
Loaded: WorkerShared.dll.
Unloaded 'Dynamic Worker Domain' AppDomain

Post-unload Assemblies Loaded:
Loaded: mscorlib.dll.
Loaded: Microsoft.VisualStudio.HostingProcess.Utilities.dll.
Loaded: System.Windows.Forms.dll.
Loaded: System.dll.
Loaded: System.Drawing.dll.
Loaded: Microsoft.VisualStudio.HostingProcess.Utilities.Sync.dll.
Loaded: AppDomainLoad.vshost.exe.
Loaded: System.Data.dll.
Loaded: System.Xml.dll.
Loaded: AppDomainLoad.exe.
Loaded: WorkerManager.dll.
Loaded: WorkerShared.dll.
All work complete.

Good old blurry pics

sholstad — Wed, 02 May 2007 01:01:00 GMT

Well, that pretty much wraps up MIX 2007. What a great showing by Microsoft. Keeping with Clarity tradition, thought I should throw up a few fuzzy pics:

Keynote conference layout

Guitar Hero and Gears of War got a LOT of attention. Is this the defining geek image of our generation?

This is your shirt. This is your shirt when you fly Southwest. Any questions?

MIX07