Snippet of offending code (generates exception when queue is empty)

            try
            {
                using (MessageQueue msmq = CreateMessageQueue())
                {
                    msmq.Peek(new TimeSpan(0));
                }
            }
            catch (MessageQueueException e)
            {
                if (e.MessageQueueErrorCode == MessageQueueErrorCode.IOTimeout)
                {
                    empty = true;
                }
            }

A Better Way?

 // Set the filter to only retrieve no major attributes or body
        MessagePropertyFilter propFilter = new MessagePropertyFilter();
        propFilter.ClearAll();
                
        MessageQueue newQueue = new MessageQueue(queuePath, false, true, QueueAccessMode.Peek);
        newQueue.MessageReadPropertyFilter = propFilter;

        if(newQueue.GetAllMessages().Length > 0)
               ...

1. Create a new virtual hard disk
2. Capture the setup disk ISO file
3. Start the VPC
4. On the screen, choose languages and such
5. Click on the repair link
6. Click on the command prompt link
7. At the command prompt type "diskpart"
8. At the diskpart prompt type "select disk 0"
9. Now type "clean"
10. Now type "select partition 1"
11. Now type "active"
12. Now type "format fs=ntfs", this formats to NTFS type
13. Now type "exit" to get out of the diskpart program
14. Now type "exit" at the command prompt to get back to system recovery options dialog
15. Now select restart button to startup the setup disk and your off and running!

It should be fully format and you should be able to boot onto setup disk and install now.

Enjoy

Here is a snippet with highlighted added:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
 <startup>
    <supportedRuntime version="4.0" />
  </startup>
  <appSettings>
    <add key="FirstTimeRun" value="False" />
    (more settings and file items - left out for clarity)
  </appSettings>
    <system.net>
          <defaultProxy enabled="true">
                   <proxy usesystemdefault="True"/>
          </defaultProxy>
    </system.net>
</configuration>

Hope this helps!

.Net 4.0 Current:
4.0.30319 (RTM)

General Visual Studio Downloads Page
https://msdn.microsoft.com/en-us/vstudio/bb984878.aspx

Visual Studio Feature Packs
https://msdn.microsoft.com/en-us/vstudio/ff655021.aspx

Visual Studio 2010 SDK
https://www.microsoft.com/downloads/details.aspx?FamilyID=47305cf4-2bea-43c0-91cd-1b853602dcc5&displaylang=en

Visual Studio 2010 Power Tools
https://msdn.microsoft.com/en-us/vstudio/bb980963.aspx

General Visual Studio Shipped Software Updates (none yet for VS 2010)
https://msdn.microsoft.com/en-us/vstudio/aa718693.aspx

Visual Studio ALM Rangers (I am a member!) Site for out of band solutions for missing features or guidance
Main site: https://msdn.microsoft.com/en-us/vstudio/ee358786.aspx
Downloads: https://msdn.microsoft.com/en-us/vstudio/ee358787.aspx

MSDN Subscription Only Downloads
https://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx?pv=18:370

Scenario

There is a "controller" custom control that registers an PageAsyncTask that needs information from all the prerender events of all other controls on the page.   This "controller" is the first control in the collection and it needs to do all the processing during the "async" time.   As the normal custom controls prerender events happen, they register data to the "controller'.

Solution or the fun ...

I created a "decision" PageAsyncTask in the prerender of the "controller" custom control.   Inside the "decision" begin task I collected all the data from the other controls prerender registration calls and determined whether I needed to do further processing.   I then proceeded to create additional PageAsyncTasks for the work and then call Page.ExecuteRegisteredAsyncTasks(); to do the work.

The "decision" task really isn't an async task per se so I created a "dummy" IAsyncResult to finish the processing.

Those I have showed think it was inventive and elegant way to implement.  If anyone is interested in code snippets let me know and I will try to give some snippets (it is a lot of code to show for a blog post).

Reference: https://vs2010quickref.codeplex.com/

• Hard Disk time:  Loading 100 dlls will almost always take longer than a single large DLL.   DLLs are physically scattered across the disk.  Latency etc come into play on the initial load times.
• Memory Usage: A single dll contains 1 set of "standard" meta data vs 100 times that standard meta data can start to make up some memory space (i.e. X bytes of product name, version info, etc x 100 dlls x # of app domains = memory)
• Security: .Net CLR has to do a lot more processing with multiple DLLs vs less DLLs.  A security policy will need to be loaded, managed, and executed per each DLL.
• CLR Management:  If DLLs do not specifically call for a unique "base address" so the CLR must re-base each DLL when it loads them costing startup cycle time.  Also when code executes the CLR must locate the object in memory and if it has to go through a "lookup table" of those addresses it will take longer to find one if multiple DLLs are used.
• Management: Locating code, determining DLL references to use, build scripts, etc will take more time to manage in the SDLC.
• Optimization: The .Net compiler can make more and better optimization decisions if acting on more code base.   Smaller sets of code will provide less optimization opportunities.
• Maintenance: Managing the additional project files, assembly info files, etc add time and understanding to developers.

Additional information: https://blogs.msdn.com/brada/archive/2004/05/05/126934.aspx

Visual Studio and .Net Tutorials and Training Videos

• Microsoft Official Visual C# Developer Center https://msdn.microsoft.com/en-us/vcsharp/aa336766.aspx 
• Microsoft Official ASP.Net Tutorials: https://www.asp.net/learn
• Microsoft Offical .Net Tutorial: https://msdn.microsoft.com/en-us/library/bb820895.aspx
• CSharp Station Tutorials: https://www.csharp-station.com/Tutorial.aspx 
• Sharper Tutorials: https://sharpertutorials.com/tutorials/
• Programmingtutorials from dotnetspider: https://www.dotnetspider.com/tutorials/DotNet-Tutorials.aspx
• DevHood Training Modules: https://www.devhood.com/training_modules/
• FunctionX Tutorials (table of content on left): https://www.functionx.com/csharp/

1. Navigate to your SendTo folder (Windows XP location is C:\Documents and Settings\{user}\SendTo and just replace {user} with your login user name)
2. Right click select New/Shortcut to add a shortcut
3. Type in the location of the program to send the file to then click Next
1. Notepad is “%windir%\notepad.exe”
2. Visual Studio 2008 is "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe" /edit
4. Give the send to a name that is user friendly (i.e. Notepad or Visual Studio 2008 as appropriate)