Search

Windows Azure SDK Debugger Causes IIS Express Crash When Environment Variables are Long by simbaja

Active

2
0
Sign in
 to vote
Type: Bug
ID: 771969
Opened: 11/22/2012 8:19:57 AM
Access Restriction: Public
0
Workaround(s)
1
User(s) can reproduce this bug
When debugging using the Azure Compute Emulator and the Web Role set to use IIS Express, the WindowsAzureDebugger.exe application tries to launch IIS Express. Unfortunately, because it's going over WCF remoting, there appears to be a limit on the size of the ProcessStartupInfo class that is sent when launching the debugger. In the WaIISHost.log file created by the compute emulator, you'll see messages saying there are issues deserializing this object. I have confirmed that if you make the environment variables small enough, it will work as expected.

Azure SDK 1.8 (October 2012)
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

.NET Framework 4.0

Steps to reproduce

Make your environment variables exceedingly long and try to debug an Azure application using the Azure Compute Emulator and IIS Express.

Product Language

English

Operating System

Windows 7

Operating System Language

English

Actual results

IIS Express fails to launch, making debugging impossible.

Expected results

IIS Express launches, and debugging works.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 11/22/2012 at 6:14 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 11/22/2012 at 8:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement