This is awesome - it's always great to find/discover tools out on the web.  Even ones that have been out there for years and you just never knew about 'em.  This is one of those cases for me.

ColorBlender is a free online tool that will automatically create palettes of matching/coordinated colors (a blend).  You can save your blends, download them in an .ACT file for Photoshop (awesome...I'll be using this all the time), an .EPS file (same for Illustrator), do PANTONE matching, etc.

It has a great UI for managing the RGB values of your color via sliders and provides some slight variations on your color.

For all those out there that are color-scheme challenged, this site should be on your 'do-not-misplace-this-site' list.  Very cool.

Today we had the front door on the house replaced - a much desired improvement on the home.  I've added these before and after pictures to the House Projects gallery (before, after)  The next step is to get shutters on the house to match.  Then redo the flooring in the house.  We're going to tear up the carpet and put hardwood throughout the first floor entry, kitchen, and living room; but some of these projects will have to wait until the summer...or next...or the one after that.

I was working with a customer today on an issue.  The customer had a custom VS project that he had inherited from another developer who had since left the company on other pursuits.  While the original developer could work in the solution just fine, the new developer was receiving the following error message:

Visual Studio .NET cannot create or open the application.  The likeliest problem is that required components are not installed on the local web server.  Run Visual Studio .NET setup and add the web development component.

Naturally the first thing I tried was to repair IIS with the following commandlines:

cd %windir%\Microsoft.NET\Framework\v1.1.4322
aspnet_regiis -i

That didn't fix the error, though I didn't really expect it to - the .NET extensions were all already properly mapped in IIS.  The solution was (unlike all of the recommendations that I found online to run the aspnet_regiis utility) to fallback to the same solution that had solved another issue a long time ago:  to delete the VSWebCache folder.

The VSWebCache folder is created automatically by Visual Studio when you open/create a web project and can be found in <root>\Documents and Settings\<user>\VSWebCache\<machinename>.  Simply delete this folder and VS will recreate it when you attempt (now successfully) to open the web project.

DevUtah is pleased to announce the 2nd Utah Geek Dinner.  We held last month's inaugural meeting at Los Hermanos in Lindon, Utah to great success and turnout.  This time around we're keeping with the Mexican food theme (only coincidentally).

The 2nd Utah Geek Dinner is to be held on December 20th at the Mayan Restaurant in Sandy, Utah.  Hopefully this will cater more to the SL County residents but not dissuade those of Utah County or even further north from coming.

While the event is free and open to all, each attendee is responsible for his/her own meal (about $12:95).  A final head count needs to be given to the Mayan by 5:00 PM on Monday, December 19th.  Therefore, registration is open until 4:30 PM on Dec 19th, at which point registration will close.

Please indicate on your registration how many will be attending (if you're bringing your spouse).

Here are some helpful links for the event:

DevUtah's Website
The Mayan Restaurant (map to the restaurant)
RegistrationWIKI

See you there!  Should be a blast!

I've been recently dabbling with the DotNetNuke version 4.0.  I'm completely new to it, and wanting to experiment with it having created many web applications myself I wanted to see what it's like - I hear great things.

Any who follows this blog is very aware that I don't run under an administrative account, preferring instead to always run as a low privileged account.  Well, most of the web applications that I have on my laptop target the .NET 1.1 framework.  All of the .NET 2.0 web applications have run under Cassini and are file-based rather than installed as a virtual directory in IIS, therefore some things had not been configured to run properly using .NET 2.0 and IIS.

Upon setting up DNN and attempting to run it I ran into the 'Server Application Unavailable' error message.  I examined the event log and saw the following error message:

Failed to execute the request because the ASP.NET process identity does not have read permissions to the global assembly cache. Error: 0x80070005 Access is denied.

Ok, well doesn't mean that *I* don't have read access to the GAC (which I do)...it's indicating that the account associated with ASP.NET 2.0 applications doesn't have permissions to the GAC.  In this case that's MACHINENAME\ASPNET.  You might be tempted to open up Windows Explorer, navigate to the %WINDIR%\assembly folder (for that's the location for the GAC), right click it, and change security settings.  As it turns out, however, Windows virtualizes this folder and its contents into an aggregated view of the GAC contents rather than actual directories.  That option is out.

How then do we grant permissions on the GAC?  The answer is pretty easy actually: we use a commandline utility called CACLS.  Open up a command window and run the following command (or something similar to it):

CACLS %WINDIR%\assembly /e /t /p [DOMAIN|MACHINENAME]\useraccount:R

Substituting either your domain name (for a domain account) or machine name (for a local account) as appropriate.  The command line grants Read permission to the specified account to all files and folders in the specified folder.

You might also need to do something similar to your application's directory.

As it turns out, however, I don't want my web applications to run under ASPNET.  Instead I prefer to run them as my personal account so I can debug the applications (being that I'm not an administrator).  I had already used the aspnet_setreg utility to encrypt my credentials in the registry.  I then simply needed to update the <processModel /> element in the %WINDIR%\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config file to resemble the following:

<processModel
   autoConfig="true"
   userName="registry:HKLM\Software\ASPNET\Identity\ASPNET_SETREG,userName"
   password="registry:HKLM\Software\ASPNET\Identity\ASPNET_SETREG,password"
/>

By doing this, I don't have to worry about granting the ASPNET account read access to the GAC (which I did anyway) and I ensure that ASP.NET 2.0 applications run under my local account (giving me all the access I need to run and debug them).

We went out and splurged a few days ago, getting some toys.  We felt it appropriate to get them now and use them rather than get them and wait until Christmas.  It's long overdue, and we've been wanting/needing something for a long time, so we went ahead and bit the bullet.  I think we made the right decision.

First toy: Nikon D50 digital SLR camera.  We've had an Olympus E10 camera for several years, and it's been pretty good (unless someone moves during a shot...terrible shutter speed).  The Nikon is pure joy to work with.  I would have loved to get the new D200, but the price was prohibitive...though I'm sure in a few years it'll be in the budget range.

Second toy:  Sony Handycam 301.  This is something that we've been wanting for a long time.  In addition to fun family videos and what not, I'll also be using this at the .NET User Group to film the presentations.  It records right to DVD.  That, coupled with Camtasia (which is a fantastic screen recording/capturing application), we should be able to do some really great things.  (and yes, I altered the picture to show the Incredibles...it just makes more sense that way).

It's going to be a fun!

Tonight, for those that can make it, Kathleen Dollard is presenting on WinForms Databinding with the Utah County .NET User's Group.  It should be a fun time.  For those that might not be aware, they meet down on the UVSC campus in room CS512 at 6:00 PM.

If I'm not mistaken this month's meeting marks the 1 year anniversary of the UCNUG, which is pretty exciting!

Hehe, I looked at Kathleen's blog (which, btw, doesn't have any activity since April 2005) and was amazed at her stats: 57 posts, 21148 comments!  Holy cow, must be incredibly insightful.  But then I saw that 99% are spam...which is unfortunate.

This is pretty cool - I downloaded it, installed it, played it, was impressed, and promptly died.  I gotta get used to the controls but they guys that worked on this (Dobermann, Chainsaw, et al) did a fantastic job...looks like lots of fun and it's very well done.

If you're a fan of the original XBox Halo (by Bungie), you gotta check out this Halo side scroller called HaloZero.

Spider-man has been a favorite of mine for a long time, so I kinda like the results.

Spider-Man 75% The Flash 75% Green Lantern 70% Robin 67% Superman 65% Hulk 60% Iron Man 60% Catwoman 50% Supergirl 48% Batman 45% Wonder Woman 38%

You are intelligent, witty, a bit geeky and have great power and responsibility.

Recently I've had the need to serialize an object using the XmlSerializer.  By default, when you serialize an object it will automatically add the default xmlns:xsd="..." and xmlns:xsi="..." namespaces to the root element of the xml document.  In my particular case this was not desirable, but there wasn't any obvious way to remove them.  As it turns out, there really is, but it's semi-obscure.

As it turns out, I did this a few years ago back in my .NET 1.0 days, but it had since evaporated from my memory, but I found a nice little blog post that jogged my memory.  All you have to do is use an XmlSerializerNamespaces object with an empty namespace.  The .NET framework will inspect this object for any namespaces.  A null reference or zero entries will cause the serializer to include the defaults.  Any namespaces (even empty ones) override the default behavior, thereby not including the default.  A simple example might resemble the following:

internal string SerializeCustomer(Customer cust) {
   using ( StringWriter writer = new StringWriter(CultureInfo.InvariantCulture) ) {
      XmlSerializer ser = new XmlSerializer(typeof(Customer));
      // remove the xsd and xsi namespaces from the serialization output by
      // appending a blank namespace
      XmlSerializerNamespaces xsn = new XmlSerializerNamespaces();
      xsn.Add(string.Empty, string.Empty);
      // serialize the object and extract the result from the writer
      ser.Serialize(writer, cust, xsn);
      return writer.ToString();
   }
}

This is pretty exciting.  Today Phil and I (collectively DevUtah) announced the second of many Geek Dinners to come.  The first one was a smashing success and we hope this one can be a great event as well - hopefully with a little more coordination.  Put it on your calendar and register on the RSVP list for December 20th, 2005 at 6:00 PM.  The location has yet to be determined but once we have that secured we'll post that as well.

Invite your friends and colleagues.  I know of several people that couldn't make the last one for one reason or another; hopefully we'll have all the gang out with many new faces as well.  Let's build the community!

Tonight I'm very excited to announce that Ted Neward is going to grace us of the Utah .NET User Group with his presence in an INETA sponsored event.  He's going to be addressing the topic of Indigo (now formally known as the Windows Communication Foundation Services).  The meeting is open to all and all are welcome.

As usual we meet at 6:00 PM and Neumont University (10701 W. River Front Parkway, South Jordan, Utah) is kind enough to provide us with space to meet.  If you are planning on coming, please RSVP.  We've received a VERY limited number of RSVP's (which has me a little concerned).  We want to make sure that we don't over- or under-purchase refreshments.

Anyway, we'll see you there...it should be a great time!