There's the VS2005 Create Guid tool:

But you have to click New GUID, then Copy, the Exit. That's not very fast (even if you learn the keyboard accelerators, which I always do). Also, in VS2008 it didn't come configured out of the box. So I tried the following alternative which turned out to be better:

Go to the External Tools menu shown above, and add the following:

 

The uuidgen.exe tool lives in the VS installation folder, under Common7\Tools, and is a command-line utility that just creates a new guid. Note the "Use Output window" option, which basically leaves the generated Guid in your VS output window....

Read full article

I like Firefox. I think, that Firefox is one of the best browsers, i ever used. As web programmer, i used it alot. Well, after researching SubSonic project, Vista starting to work very slow. After fighting my way to the Task manager, i allmost fall from my chair. Firefox used 1.4GB of RAM. WTF? I was so suprised, i allmost spilled my drink. I thought, that ammount of memory is controlled (both Vista and Firefox). The same thing happend with ReSharper, but R# dont go over 0.5 GB speed limit. I had no choice left. I killed the Process.

I had only one Problem with Firefox on Windows Vista, when it flickerd. Then after a while ( and alot of headack ), i find out, that one bookmark must be in toolbar, and everything was back to normal.

Guess, it was just a bug, that i will report to the Firefox and Vista team. They will know, what to do with the Information.

Picture:

The LOLCAT is mildly amusing, but what I find really amazing is that someone actually took the time to write an implementation LOLCODE for the DLR. 

Imagine that, instead of writing boring old C# code, you wrote something like this:

HAI
CAN HAS STDIO?
I HAS A FISH ITZ "Yummy"
VISIBLE FISH
VISIBLE "HAI WORLD!"

I HAS A FIB
I HAS A A ITZ 1
I HAS A B ITZ 0

GIMMEH FIB

IM IN YR LOOP
  VISIBLE B

  IZ FIB SMALR 1?
  YARLY
    GTFO
  NOWAI
    VISIBLE "NOWAI"
  KTHX

  I HAS A TEMP ITZ A UP B
  LOL A R B
  LOL B R TEMP

  NERFZ FIB!!
KTHX

KTHXBYE

Incredible. As John said, though, if nothing else it's a great example of how to implement a simple language on the DLR.

If you've ever placed a Virtual Earth map or Google map on an HTTPS page then you're probably familiar with the mixed content message that appears when the page loads:

While there are workarounds for this in the browser settings, the solution isn't really scalable. The good news it that Virtual Earth 6 now offers support for SSL pages. All that we have to do is update the script reference like so:

<script type="text/javascript" 

  src="https://dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=6&s=1">

</script> 

Notice how the source path now begins with https and the version is set to 6. Also, there is the additional parameter at the end, s=1; that flags the request accordingly.

If you're using ASP.NET AJAX and have a ScriptManager on the page, then your reference can look something like this:

<asp:ScriptManager ID="ScriptManager1" runat="server">

  <Scripts>

    <asp:ScriptReference Path="https://dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=6&s=1" />

  </Scripts>

</asp:ScriptManager>

This seems like a subtle change, but both Google and Virtual Earth have lacked this type of support for years. For anyone building enterprise applications that require HTTPS, this is something we've been asking and waiting for, for quite some time.

Now that I'm happily living in the exciting, fast paced world of Greater London you'd think my weekends would be spent enjoying the active nightlife or soaking in the culture and history all around me.  But you'd be wrong.  I'm a nerd and so I spent my weekend in nerd bliss, a.k.a. getting reacquainted with my old friend WCF.  Sorry ladies, I'm taken.

I had reason to look at building a RSS service with WCF and ran across the WCF RSS Toolkit.  This is a very cool sample app written I believe by Clemens Vasters which allows developers to build services that expose endpoints encoded for RSS or ATOM.  The implementation is pretty slick in that it checks the QueryString for operations and routes the calls accordingly.  It also formats the feeds dynamically to RSS or ATOM using XSLT transforms before unwrapping the message from SOAP using a custom POX Encoder.

While this is all extreme coolness, and I take absolutely no credit for any of it, it did have one major problem.  It was built quite some time ago and uses the CTP version of WCF.  I assumed that somebody must have a more up-to-date version or a better way to generically build an RSS/ATOM service but after looking around for several hours I couldn't find much.  And so with a weekend to kill and my nerd gene complelling me I dug into the code and started migrating it to Visual Studio 2008 and .NET 3.5. 

There were several small changes that needed to be made to update some class names that were different between RTM and the CTP version and also a few abstract method implementation changes.  A more significant change was that the POX Encoder functionality wasn't really necessary anymore since WCF will send POX messages if you specify a MessageVersion of type "None".  After making these changes I loaded up the samples and confirmed that they all worked.

So here then is the updated version.  I've posted an item on WCF.NetFX3.com as well.  If there's anything I missed please let me know.  Also, if there is a newer/better way to implement RSS/ATOM services in WCF feel free to comment to this post as my search wasn't necessarily exhaustive.

<summary>
GhostDoc is a free add-in for Visual Studio that automatically generates XML
documentation comments for C#. Either by using existing documentation inherited
from base classes or implemented interfaces, or by deducing comments from
name and type of e.g. methods, properties or parameters.
</summary>

Quick Facts

• Bugfix release
• Download on the GhostDoc Website
• Users of earlier versions: Please read the ReadMe on upgrading!

About this Release

Version 2.1.2 fixes a problem with side-by-side installations of GhostDoc versions for Visual Studio 2005 and 2008.

What’s New in GhostDoc 2.1.2:

• Fixed: GhostDoc versions for Visual Studio 2005 and Visual Studio 2008 interfering when installed side-by-side.
• Changed: An upgrade installation by starting the MSI file while an older version is installed is no longer supported, i.e. you have to uninstall GhostDoc before running the new setup. Note that this does not affect an upgrade of the configuration of earlier versions: the configuration file is not removed during uninstallation of the GhostDoc add-in, so you'll still be offered to upgrade your configuration when installing the new version. For detailed installation instructions, please take a look at the ReadMe in the ZIP file.
• Added: A few special words for ("of the" trigger and prefix words, "no the" words).

Note that VB.Net support is turned off by default and has to be turned on in the configuration dialog.

Everyone has a certain set of tasks that they simply do not want to perform.

Even if it seems like the sort of thing that others might (right or wrong) expect them to do as a part of their job.

Like some housekeepers don't do windows.

And some secretaries don't get coffee.

And I don't do dishes.

And GDI on Windows doesn't do supplementary characters.

Over in the microsoft.public.win32.programmer.international newsgroup, semi-regular reader Christian Kaiser asked:

Possibly I'm missing something, but I did not find any documentation on how to use GetCharABCWidths() with UTF16 surrogate pairs (additional planes).
Is there any way to use that API (or the like)? The API gets UINT instead of TCHAR, so maybe by shifting the high surrogate and 'or'ing with the low one?

Christian

But Christian isn't missing anything here -- the only way that GDI can ever handle supplementary characters is as glyph ID values; it cannot handle either surrogate pairs or UTF-32 encoded Unicode Scalar Values.

Kind of unfortunate for the whole family of GDI functions like GetCharABCWidths, since only some of them will also take glyph ID values. And although all supplementary character processing does through Uniscribe, there are many pieces of the supplementary ranges that do not require any complex script processing other than this particular requirement, which just means that some functions have no supplementary equivalent.

Because GDI wouldn't know a supplementary character if that character walked up and bit it in the ass (thus inspiring the post's sponsor)....

This post brought to you by 𝌽 (U+1d33d, aka U+d834 U+df3d, aka TETRAGRAM FOR CLOSED MOUTH)