« December 2005 | Main | February 2006 »

January 16, 2006

Oh, That's what it's for!

IE7 will have a "clear my tracks" feature that will delete the following with one click:

Temporary Internet Files:
Cookies
History
Form Data
Passwords

Why would anyone want a feature like this? Uche Enuha explains, "So you’re trying to buy a gift for your loved one and you know how important it is to keep this mission secret..."

Oh, THAT'S what this feature is really for!

If I ever go to the machine that my 14 year old uses, and his browser history is deleted, his butt's grounded.

I would have expected that Uche Enuha, a self-proclaimed recent college graduate, would know better.

Posted on January 16, 2006 at 12:47 PM | Permalink | Comments (1)

January 13, 2006

Please insert your credit card to complete the Vista upgrade

CRN is reporting that there will be a single bit set for Windows Vista, and that an upgrade will consist of simply obtaining keys to unlock additional features. Upgrades will not require installing a new version over the top of an existing version.

Posted on January 13, 2006 at 07:42 PM | Permalink | Comments (0)

January 10, 2006

MSDN TV - on VB Fusion

Jay Roxe in an MSDN TV episode showing off the VB Fusion technique.

Posted on January 10, 2006 at 03:40 AM | Permalink | Comments (1)

January 09, 2006

Paste As VB.NET

My MSDN article has just hit the shelves. This article shows how to build a Visual Studio 2005 add-in that lets you copy a C# example to your clipboard, and just "Paste as VB" into your code editor. Even if you don't care about learning how to build add-ins, you might want to download the sample just to use the Paste as VB functionality.

Posted on January 9, 2006 at 02:39 PM | Permalink | Comments (1)

Oh, that class?

I think we have that class on aisle 28A, on the right side, about 1/2 way down. If not, check in gardening.

Nice one Billy.

Posted on January 9, 2006 at 12:56 PM | Permalink | Comments (0)

January 03, 2006

Setting the unsettable settings

Visual Studio 2005 gives you a great graphical way to define user and application settings for an application:

Mysettings

You can access these at runtime as simple as "x = My.Settings.MyUserSetting".  The user settings can even be changed at run-time, and the new values automatically saved.

The application settings are a different story.  They're read-only.  If you try to change them, it's a compile error:

Mysettings2

Sometimes, you want to change an application setting at run time.  For example, if you're using the new table adapters, they get their connection string from an application setting.  If you want to change the path to the database, or specify user credentials at run time, you either need to change the setting, or manually attach a new connection to all your adapters.  Changing certain application settings, even if they're not saved on exit, is certainly advantageous.  Luckilly, you can, by using the Item collection:

Mysettings3

For more about doing this specifically with connection strings, also see: Customizing the connection string for TableAdapters.

Posted on January 3, 2006 at 08:30 AM | Permalink | Comments (0)