<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:evnet="http://www.mscommunities.com/rssmodule/"><channel><title>Entries for mstefan</title><atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/niners/mstefan/rss/default.aspx" /><image><url>http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.png</url><title>Entries for mstefan</title><link>http://channel9.msdn.com/Niners/mstefan/</link></image><description>Entries, comments and threads posted by mstefan</description><link>http://channel9.msdn.com/Niners/mstefan/</link><language>en-us</language><pubDate>Mon, 04 Feb 2008 05:46:50 GMT</pubDate><lastBuildDate>Mon, 04 Feb 2008 05:46:50 GMT</lastBuildDate><generator>EvNet (EvNet, Version=1.0.3149.21012, Culture=neutral, PublicKeyToken=null)</generator><item><title>ActiveX Test Container [ActiveX Test Container]</title><description>I just noticed that the ActiveX Test Container (tstcon32.exe) was missing from Visual Studio 2008, and it's not in the latest Windows SDK. Is this an oversight, or does Microsoft just think that no one is building ActiveX controls anymore? :P&lt;br /&gt;&lt;br /&gt;It's not a big deal, since I have a copy of it with Visual Studio 2005, but it is handy for testing them in the debugger, particularly when using scripts.&lt;p&gt;in reply to &lt;a href='http://channel9.msdn.com/forums/TechOff/260742-ActiveX-Test-Container/'&gt;ActiveX Test Container&lt;/a&gt;&lt;/p&gt;&lt;img src="http://channel9.msdn.com/260742/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" /&gt;</description><comments>http://channel9.msdn.com/forums/TechOff/260742-ActiveX-Test-Container/</comments><link>http://channel9.msdn.com/forums/TechOff/260742-ActiveX-Test-Container/</link><pubDate>Mon, 04 Feb 2008 05:46:50 GMT</pubDate><guid isPermaLink="true">http://channel9.msdn.com/forums/TechOff/260742-ActiveX-Test-Container/</guid><evnet:views>1745</evnet:views><evnet:viewtrackingurl>http://channel9.msdn.com/260742/WebViewBug.aspx?EVT=0</evnet:viewtrackingurl><evnet:previewtext>I just noticed that the ActiveX Test Container (tstcon32.exe) was missing from Visual Studio 2008, and it's not in the latest Windows SDK. Is this an oversight, or does Microsoft just think that no one is building ActiveX controls anymore? &lt;img src='/emoticons/C9/emotion-4.gif' alt='Tongue Out' /&gt;&lt;br /&gt;&lt;br /&gt;It's not a big deal, since I have a copy of it with Visual Studio 2005, but it is handy for testing them in the debugger, particularly when using scripts.</evnet:previewtext><dc:creator>mstefan</dc:creator><slash:comments>2</slash:comments><wfw:commentRss>http://channel9.msdn.com/forums/TechOff/260742-ActiveX-Test-Container/RSS/</wfw:commentRss><trackback:ping>http://channel9.msdn.com/260742/Trackback.aspx</trackback:ping></item><item><title>Specifying the runtime version [Specifying the runtime version]</title><description>&lt;p&gt;Is there&amp;nbsp;a command line option (or some other&amp;nbsp;way) to explicitly specify the runtime version for an assembly other than the default (e.g.: "v2.0.50727")? In other words, specify your own value that's returned by Assembly.ImageRuntimeVersion?&lt;br /&gt;&lt;/p&gt;&lt;p&gt;in reply to &lt;a href='http://channel9.msdn.com/forums/TechOff/257249-Specifying-the-runtime-version/'&gt;Specifying the runtime version&lt;/a&gt;&lt;/p&gt;&lt;img src="http://channel9.msdn.com/257249/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" /&gt;</description><comments>http://channel9.msdn.com/forums/TechOff/257249-Specifying-the-runtime-version/</comments><link>http://channel9.msdn.com/forums/TechOff/257249-Specifying-the-runtime-version/</link><pubDate>Mon, 27 Aug 2007 17:42:48 GMT</pubDate><guid isPermaLink="true">http://channel9.msdn.com/forums/TechOff/257249-Specifying-the-runtime-version/</guid><evnet:views>2277</evnet:views><evnet:viewtrackingurl>http://channel9.msdn.com/257249/WebViewBug.aspx?EVT=0</evnet:viewtrackingurl><evnet:previewtext>&lt;p&gt;Is there&amp;nbsp;a command line option (or some other&amp;nbsp;way) to explicitly specify the runtime version for an assembly other than the default (e.g.: "v2.0.50727")? In other words, specify your own value that's returned by Assembly.ImageRuntimeVersion?&lt;br /&gt;&lt;/p&gt;</evnet:previewtext><dc:creator>mstefan</dc:creator><slash:comments>6</slash:comments><wfw:commentRss>http://channel9.msdn.com/forums/TechOff/257249-Specifying-the-runtime-version/RSS/</wfw:commentRss><trackback:ping>http://channel9.msdn.com/257249/Trackback.aspx</trackback:ping></item><item><title>Stop the Ding! [Stop the Ding!]</title><description>&lt;p&gt;One of the most annoying things in Vista is that once you change your system sounds, applications will play the default sound (typically "Windows Ding.wav") every time you select an item in a listview control. Frankly, this was driving me to distraction and so I spent some time digging around and thought I would share here, in case anyone else was annoyed. My apoligies if this has already been posted elsewhere.&lt;br /&gt;&lt;br /&gt;It turns out, it looks there's a bug in the Control Panel applet where you set your sound preferences. Even if you have the "Select" sound set to nothing, it's creating an entry (what is probably a null string) in HKEY_CURRENT_USER\AppEvents\Schemes\Apps\.Default\CCSelect\.Current.&lt;br /&gt;&lt;br /&gt;Because it's not actually a sound file, it reverts to the default sound. And, because the folks at Microsoft apparently want to make this as annoying as possible, if you disable the default sound, then it decides to do you the "favor" of beeping using your system speaker. Everyone on the Vista team should be forced to wear headphones and listen to an endless loop of "Windows Ding.wav" until a fix is published for this. I'm just saying.&lt;br /&gt;&lt;br /&gt;In the meantime, here's a temporary fix in the form of a registry file. Note that you'll need to run this after every time you change your system sounds through the control panel, or the Ding from Hell™ will return:&lt;br /&gt;&lt;br /&gt;Windows Registry Editor Version 5.00&lt;/p&gt;
&lt;p&gt;[HKEY_CURRENT_USER\AppEvents\Schemes\Apps\.Default\CCSelect]&lt;br /&gt;@=""&lt;/p&gt;
&lt;p&gt;[HKEY_CURRENT_USER\AppEvents\Schemes\Apps\.Default\CCSelect\.current]&lt;br /&gt;@=""&lt;/p&gt;
&lt;p&gt;[HKEY_CURRENT_USER\AppEvents\Schemes\Apps\.Default\CCSelect\.Default]&lt;br /&gt;@=""&lt;/p&gt;
&lt;p&gt;[HKEY_CURRENT_USER\AppEvents\Schemes\Apps\.Default\CCSelect\.Modified]&lt;br /&gt;@=""&lt;/p&gt;&lt;p&gt;in reply to &lt;a href='http://channel9.msdn.com/forums/Coffeehouse/256901-Stop-the-Ding/'&gt;Stop the Ding!&lt;/a&gt;&lt;/p&gt;&lt;img src="http://channel9.msdn.com/256901/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" /&gt;</description><comments>http://channel9.msdn.com/forums/Coffeehouse/256901-Stop-the-Ding/</comments><link>http://channel9.msdn.com/forums/Coffeehouse/256901-Stop-the-Ding/</link><pubDate>Thu, 09 Aug 2007 20:28:03 GMT</pubDate><guid isPermaLink="true">http://channel9.msdn.com/forums/Coffeehouse/256901-Stop-the-Ding/</guid><evnet:views>4762</evnet:views><evnet:viewtrackingurl>http://channel9.msdn.com/256901/WebViewBug.aspx?EVT=0</evnet:viewtrackingurl><evnet:previewtext>One of the most annoying things in Vista is that once you change your system sounds, applications will play the default sound (typically "Windows Ding.wav") every time you select an item in a listview control. Frankly, this was driving me to distraction and so I spent some time digging around and thought I would share here, in case anyone else was annoyed. My apoligies if this has already been posted elsewhere.It turns out, it looks there's a bug in the Control Panel applet where you set your sound preferences. Even if you have the "Select" sound set to nothing, it's creating an entry (what is…</evnet:previewtext><dc:creator>mstefan</dc:creator><slash:comments>5</slash:comments><wfw:commentRss>http://channel9.msdn.com/forums/Coffeehouse/256901-Stop-the-Ding/RSS/</wfw:commentRss><trackback:ping>http://channel9.msdn.com/256901/Trackback.aspx</trackback:ping></item><item><title>.NET Framework 3.5 [.NET Framework 3.5]</title><description>For anyone in the know, is the 3.5 framework simply an extension of the 2.0 framework (similar to how 3.0 is)? I notice that in Orcas, even when you tell it to target 3.5, it's pulling in a lot of system classes that are part of the 2.0 framework, so it doesn't seem like it's a complete replacement (as 2.0 was for 1.1).&lt;br /&gt;&lt;br /&gt;What I'm getting at here is, if you build an application that targets 3.5, it seems like it will require both version 2.0 and 3.5 of the framework to be installed on the target system.&lt;br /&gt;&lt;br /&gt;&lt;p&gt;in reply to &lt;a href='http://channel9.msdn.com/forums/TechOff/255666-NET-Framework-35/'&gt;.NET Framework 3.5&lt;/a&gt;&lt;/p&gt;&lt;img src="http://channel9.msdn.com/255666/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" /&gt;</description><comments>http://channel9.msdn.com/forums/TechOff/255666-NET-Framework-35/</comments><link>http://channel9.msdn.com/forums/TechOff/255666-NET-Framework-35/</link><pubDate>Thu, 21 Jun 2007 22:41:25 GMT</pubDate><guid isPermaLink="true">http://channel9.msdn.com/forums/TechOff/255666-NET-Framework-35/</guid><evnet:views>9745</evnet:views><evnet:viewtrackingurl>http://channel9.msdn.com/255666/WebViewBug.aspx?EVT=0</evnet:viewtrackingurl><evnet:previewtext>For anyone in the know, is the 3.5 framework simply an extension of the 2.0 framework (similar to how 3.0 is)? I notice that in Orcas, even when you tell it to target 3.5, it's pulling in a lot of system classes that are part of the 2.0 framework, so it doesn't seem like it's a complete replacement (as 2.0 was for 1.1).&lt;br /&gt;&lt;br /&gt;What I'm getting at here is, if you build an application that targets 3.5, it seems like it will require both version 2.0 and 3.5 of the framework to be installed on the target system.&lt;br /&gt;&lt;br /&gt;</evnet:previewtext><dc:creator>mstefan</dc:creator><slash:comments>13</slash:comments><wfw:commentRss>http://channel9.msdn.com/forums/TechOff/255666-NET-Framework-35/RSS/</wfw:commentRss><trackback:ping>http://channel9.msdn.com/255666/Trackback.aspx</trackback:ping></item><item><title>Question about PowerShell and .NET assemblies [Question about PowerShell and .NET assemblies]</title><description>PowerShell has the ability to load an assembly and create an instance of a class; is there a way for the assembly to know that it has been loaded in PS rather than, for example, as a reference in a Windows Forms based application?&lt;p&gt;in reply to &lt;a href='http://channel9.msdn.com/forums/TechOff/252260-Question-about-PowerShell-and-NET-assemblies/'&gt;Question about PowerShell and .NET assemblies&lt;/a&gt;&lt;/p&gt;&lt;img src="http://channel9.msdn.com/252260/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" /&gt;</description><comments>http://channel9.msdn.com/forums/TechOff/252260-Question-about-PowerShell-and-NET-assemblies/</comments><link>http://channel9.msdn.com/forums/TechOff/252260-Question-about-PowerShell-and-NET-assemblies/</link><pubDate>Sun, 11 Feb 2007 12:16:41 GMT</pubDate><guid isPermaLink="true">http://channel9.msdn.com/forums/TechOff/252260-Question-about-PowerShell-and-NET-assemblies/</guid><evnet:views>4882</evnet:views><evnet:viewtrackingurl>http://channel9.msdn.com/252260/WebViewBug.aspx?EVT=0</evnet:viewtrackingurl><evnet:previewtext>PowerShell has the ability to load an assembly and create an instance of a class; is there a way for the assembly to know that it has been loaded in PS rather than, for example, as a reference in a Windows Forms based application?</evnet:previewtext><dc:creator>mstefan</dc:creator><slash:comments>5</slash:comments><wfw:commentRss>http://channel9.msdn.com/forums/TechOff/252260-Question-about-PowerShell-and-NET-assemblies/RSS/</wfw:commentRss><trackback:ping>http://channel9.msdn.com/252260/Trackback.aspx</trackback:ping></item><item><title>Vista and Speech Recognition [Vista and Speech Recognition]</title><description>Well, I decided to finally replace my aged webcam and microphone for a new setup from Logitech. Remembering the post here a while ago asking about why Microsoft didn't heavily promote speech recognition in Vista, I decided to give it a shot.&lt;br /&gt;&lt;br /&gt;I used the boom microphone that was part of the Logitech headset, not the webcam, since I figured that would give me the best results. I ran through the initial tutorial (which was done very nicely, by the way) and then through three training sessions. At that point, I figured that Vista would be all set and began my adventure.&lt;br /&gt;&lt;br /&gt;Ouch. Well, I found the answer to my question. It simply doesn't work reliably. It would get seriously confused when I would say "Close That" or "Cancel", it didn't know how scroll down or select items in a number of applications I tested, and dictation... not a chance. Even something as simple as starting a program was dicey. Alas, that wonderful&amp;nbsp;tutorial has no connection whatsoever to reality. When using dictation, simple phrases like "this is a test" came out as garbled nonsense in Word.&lt;br /&gt;&lt;br /&gt;And to top it all off, I have the CPU gadget on my desktop. Normally, it's sitting around 1-3%, 10-15% if I'm doing a few things (that aren't compute-bound, obviously). With speech recognition, my poor&amp;nbsp;system was &lt;em&gt;constantly&lt;/em&gt; red-lined, pegging both cores at near 100%.&lt;br /&gt;&lt;br /&gt;I can appreciate Microsoft wanting to push the envelope, but I'm sorry, this is just broken behavior. The "wow" is definitely nowhere to be found in their speech recognition code. Fortunately for their poor PSS folks, I doubt most users will even be aware that it's part of the operating system.&lt;br /&gt;&lt;br /&gt;I love Vista, but this is a feature that I think would have been better left on the shop floor until it's retooled and working.&lt;p&gt;in reply to &lt;a href='http://channel9.msdn.com/forums/Coffeehouse/252232-Vista-and-Speech-Recognition/'&gt;Vista and Speech Recognition&lt;/a&gt;&lt;/p&gt;&lt;img src="http://channel9.msdn.com/252232/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" /&gt;</description><comments>http://channel9.msdn.com/forums/Coffeehouse/252232-Vista-and-Speech-Recognition/</comments><link>http://channel9.msdn.com/forums/Coffeehouse/252232-Vista-and-Speech-Recognition/</link><pubDate>Sat, 10 Feb 2007 04:42:42 GMT</pubDate><guid isPermaLink="true">http://channel9.msdn.com/forums/Coffeehouse/252232-Vista-and-Speech-Recognition/</guid><evnet:views>5329</evnet:views><evnet:viewtrackingurl>http://channel9.msdn.com/252232/WebViewBug.aspx?EVT=0</evnet:viewtrackingurl><evnet:previewtext>Well, I decided to finally replace my aged webcam and microphone for a new setup from Logitech. Remembering the post here a while ago asking about why Microsoft didn't heavily promote speech recognition in Vista, I decided to give it a shot.&lt;br /&gt;&lt;br /&gt;I used the boom microphone that was part of the Logitech headset, not the webcam, since I figured that would give me the best results. I ran through the initial tutorial (which was done very nicely, by the way) and then through three training sessions. At that point, I figured that Vista would be all set and began my adventure.&lt;br /&gt;&lt;br /&gt;</evnet:previewtext><dc:creator>mstefan</dc:creator><slash:comments>8</slash:comments><wfw:commentRss>http://channel9.msdn.com/forums/Coffeehouse/252232-Vista-and-Speech-Recognition/RSS/</wfw:commentRss><trackback:ping>http://channel9.msdn.com/252232/Trackback.aspx</trackback:ping></item><item><title>PowerShell 1.0 Released for Vista [PowerShell 1.0 Released for Vista]</title><description>At long last, Microsoft has released &lt;a href="http://blogs.msdn.com/powershell/archive/2007/01/29/windows-powershell-1-0-for-windows-vista.aspx"&gt;PowerShell 1.0 for Vista&lt;/a&gt;. I've been waiting a while for this, and really wasn't interested in going through the gymnastics of hacking the XP build. It was probably the only thing that I really missed when I dumped my old XP development system and moved completely over to Vista when the RTM build was published.&lt;br /&gt;&lt;br /&gt;Today is a good day.&lt;br /&gt;&lt;br /&gt;&lt;p&gt;in reply to &lt;a href='http://channel9.msdn.com/forums/Coffeehouse/251855-PowerShell-10-Released-for-Vista/'&gt;PowerShell 1.0 Released for Vista&lt;/a&gt;&lt;/p&gt;&lt;img src="http://channel9.msdn.com/251855/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" /&gt;</description><comments>http://channel9.msdn.com/forums/Coffeehouse/251855-PowerShell-10-Released-for-Vista/</comments><link>http://channel9.msdn.com/forums/Coffeehouse/251855-PowerShell-10-Released-for-Vista/</link><pubDate>Tue, 30 Jan 2007 20:04:57 GMT</pubDate><guid isPermaLink="true">http://channel9.msdn.com/forums/Coffeehouse/251855-PowerShell-10-Released-for-Vista/</guid><evnet:views>3354</evnet:views><evnet:viewtrackingurl>http://channel9.msdn.com/251855/WebViewBug.aspx?EVT=0</evnet:viewtrackingurl><evnet:previewtext>At long last, Microsoft has released &lt;a href="http://blogs.msdn.com/powershell/archive/2007/01/29/windows-powershell-1-0-for-windows-vista.aspx"&gt;PowerShell 1.0 for Vista&lt;/a&gt;. I've been waiting a while for this, and really wasn't interested in going through the gymnastics of hacking the XP build. It was probably the only thing that I really missed when I dumped my old XP development system and moved completely over to Vista when the RTM build was published.&lt;br /&gt;&lt;br /&gt;Today is a good day.&lt;br /&gt;&lt;br /&gt;</evnet:previewtext><dc:creator>mstefan</dc:creator><slash:comments>3</slash:comments><wfw:commentRss>http://channel9.msdn.com/forums/Coffeehouse/251855-PowerShell-10-Released-for-Vista/RSS/</wfw:commentRss><trackback:ping>http://channel9.msdn.com/251855/Trackback.aspx</trackback:ping></item></channel></rss>