That's probably why the Convert class exists. Call Convert.ToByte(object), and it should work even if the object is a boxed Int32. And it's not that confusing. (Actually, the cast thing isn't confusing either - it's just not obvious that cast syntax not necessarily performs a cast :-D ).

Doesn't crash in Visual Studio 2008 SP1.

The funny thing is that the article says that a stripped-down Linux will be available in 30 seconds. Microsoft claims Windows 7 to boot in 22 seconds.

It's funny if it's a joke - but it seems they really proposed this seriously... I specifically like this: "From now on, padded bras will be best-sellers," said Bo Cu Hung, a popular Ho Chi Minh City blogger. Maybe the proposal is from the bra manufacturing lobby :)

The Ghost and the Darkness.

While VMWare sure has its issues, it is very easy to configure and to use, and I like it especially for the following mature features: - Drag&Drop from the host to the guest and vice versa. - Very powerful snapshot manager (only available in the paid version, IIRC) - USB support (works especially well if you have to switch USB devices often, e.g. USB dongles or network service devices) - Automatic resolution adaption to the window size (it's such a PITA having to switch resolution by hand) At least the first three of these are in my opinion essential. And then there's debugging with the Debugger running on the host and the debuggee running on the guest, which I didn't use myself, but is another feature some people would miss and that's only available with the expensive version.

I always see people here with their "large" 24" monitor fighting against the debugger, Visual Studio's many tool windows, documentation and instant messenger. I simply cannot understand what the advantage of using only a single monitor is, even if it is 24". I'm running fine with two 22" wide screens. Enough space to have many tool windows open, the side bar with useful plugins, a browser or documentation and when I am debugging something, the debuggee does not hide the debugger because it is on the other monitor. While it is possible to debug with one monitor, it's very inefficient and if you're debugging painting routines or full screen applications, it's a pain. Guess that's why it's called PAINting. Unfortunately, my system at work does not have a second PCIx16 slot. My home system does, though I also have only two monitors there and will most likely buy a cheap second graphics card with HDMI to have Windows Media Center on my HDTV.

Doesn't Windows Movie Maker from Windows XP (or Windows DVD Maker, included in Vista) fit your needs? When I used it the last time, I wasn't about to create a DVD, but cutting some home-made movies was easy with it.

Hi everybody, consider the following: I have a full report that includes a common header/footer and a number of subreports. The subreports can be enabled or disabled with parameters and all show different data sets. Now I want to display the subreport title (or a parameter or textbox value, for that matter) in the parent report header (since subreport headers are not rendered). I couldn't get this to work. I tried different approaches, including a headline on the subreport set to RepeatWith the table, but it is not repeated. What can I do? It's ok if I have to completely restructure the report. I just don't know how. Thanks in Advance, OregonGhost

It's actually very easy, because recursive properties are perfectly legal. And Refactoring doesn't do anything about it, because you have to invoke it manually for a specific Refactoring case. While this is definitely a subtile bug, it is a pretty common one if you are following the basic .NET Framework Naming convention to use PascalCasing for the public property and camelCasing for the private field. Intellisense can even help you to make it wrong, depending on your exact settings and what you typed before. If you put an underscore in front of the field name, it can't happen (or is at least easy to spot).

Of course int test = 1 + 2 + 3; equals 6. +2 + 3 +4; is a seperate expression. Remove the first semicolon if you want to connect the two expressions. int test = 1 + 2 + 3 +2 + 3 +4; will result in test == 15.

To me as a German native speaker, to have a doubt sounds pretty natural as it's the same in German (or, to be precisely, it's plural in German, i.e. having doubts). However, reading through this posts I read something like "Does that make sense?" a few times. This is used in German very often, but "to make sense" is wrong language, it's just directly translated from English, pretty much the same as to have a doubt is in English :)