Request a topic or
contact an Arke consultant
May 2008

Arke Systems Blog

Useful technical and business information straight from Arke.

About the author

Author Name is someone.
E-mail me Send mail

Recent comments




The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2023

Windows Live OneCare 2.5 in Beta

OneCare Connect Survey and Download


The new version of OneCare is now released for public beta.  OneCare now runs on Windows Server 2008!

Posted by trenton adams on Sunday, May 25, 2008 6:40 PM
Permalink | Comments (0) | Post RSSRSS comment feed

To display an assembly in the Add Reference dialog box


  • Move or copy the assembly to one of the following locations:

    • The current project directory. (You can find these assemblies by using the Browse tab.)

    • Other project directories in the same solution. (You can find these assemblies by using the Projects tab.)

    • The Public Assemblies folder: Program Files\Microsoft Visual Studio 9.0\Common7\IDE\Public Assemblies. (You can find these assemblies on the .NET tab.)

  • Set a reference path to the directory that contains the assembly by using the Reference Paths Dialog Box (Visual Basic) or the Reference Paths Page, Project Designer (C#).

  • Set a registry key that specifies the location of assemblies to display:

    Add one of the following registry keys, where <AssemblyLocation> is the directory of the assemblies that you want to appear in the Add Reference dialog box, for example, C:\MyAssemblies\.




    Creating the registry key under the HKEY_LOCAL_MACHINE node allows all users to see the assemblies in the specified location in the Add Reference dialog box. Creating the registry key under the HKEY_CURRENT_USER node affects only the setting for the current user.

    Invoke the Add Reference dialog box again; the assemblies should appear on the .NET tab. If they do not, ensure that the assemblies are located in the specified <AssemblyLocation> directory, restart Visual Studio, and try again.

Posted by trenton adams on Friday, May 9, 2008 3:25 PM
Permalink | Comments (0) | Post RSSRSS comment feed

Strong Names on Third Party Assemblies

I need to strong name a few third party assemblies so that I could include them in a compile of a strongly named assembly that I was creating.  I found this site that did a great step by step on getting this working.



  1. c:\>ildasm providedAssembly.dll /
  2. Rename/move the original assembly
  3. c:\>ilasm /dll /key=keypair001.snk

Posted by trenton adams on Thursday, May 8, 2008 4:27 PM
Permalink | Comments (0) | Post RSSRSS comment feed

Windows XP SP3 Released

You can now download Windows XP SP3 from  The last service pack released for XP was 3 years ago and since then Microsoft has released hundreds of hot fixes.  SP3 wraps all of those fixes together and introduces a couple new features that will improve Windows Server 2008 compatibility.  SP3 will be available on Windows Update shortly but in the meantime, you can download it directly from TechNet.

Windows® XP Service Pack 3 (SP3) includes all previously released updates for the operating system. This update also includes a small number of new functionalities, which do not significantly change customers’ experience with the operating system. This white paper summarizes what is new in Windows XP SP3.

Posted by eric stoll on Sunday, May 4, 2008 5:00 PM
Permalink | Comments (0) | Post RSSRSS comment feed

FCKEditor 404

I'm using the FCKEditor ASP.NET control on a web application that's deployed to a virtual directory.  When my app is deployed to the root of a web site, FCKEditor works great.  When I'm deployed in a virtual directory, I get an HTTP 404 error in the FCKEditor IFRAME.  One quick look at the IFRAME properties shows that the URL is missing the virtual directory path.  All prepared to hack on the FCKEditor.cs file, I discovered that some one else already thought of this scenario.  I either overlooked a step in the documentation or this is an undocumented feature.  Regardless, here is a universal solution to the problem...  Just add the following key to the appSettings section of your web.config...

<add key="FCKeditor:BasePath" value="~/fckeditor/"/>

That's it!  By default, FCKEditor uses /fckeditor/ and doesn't try to ResolveUrl to discover your virtual directory scenario.  Only when you add this to your appSettings will FCKEditor look for the ~ and upon finding that will it run the path through ResolveUrl.  That said, adding the above key to your appSettings should solve this problem for 99% of the people dealing with this issue.

Posted by eric stoll on Saturday, May 3, 2008 5:44 PM
Permalink | Comments (0) | Post RSSRSS comment feed