I got the exact same problem, and I've found that when removing/adding the web role, it works until I commit the code and download it onto a new development client. (and yes, it seems to be connected to the HTTPS endpoint, all is good when using just HTTP)
If anyone has any insights to share, it would be much appreciated.
Excellent - Yes, you're right. That's exactly what happened, come to think of it. Everything was working fine until I checked the source out on to another workstation. When the source is checked back in, it screws up both workstations.
MSFT or MSVPs help!
Simon Goldstone www.ActiveDataTools.com Data Cleansing, Correction and Management Software
I've now been able to reproduce the issue on a vanilla VM. If you create a Windows Azure project with two end points, one http and one https everything works fine. If you then check in to TFS it still works fine.
If you then check out on to another machine (VM2) then suddenly it stops working, even if you re-install the certificate, etc. on this new VM.
If you then go back to the original VM, and check out the project, it no longer works.
It seems that as soon as you introduce a second machine in to the development of the project (under TFS) it stops.
From then on, the only way to get the project to run/debug on your dev machine is to remove the https endpoint.
However, if you compile and publish the app to Azure with both endpoints, they work perfectly.
So the current development cycle for me is, remove https endpoint and develop as needed, debug, etc.
When it's time to build and publish, add the https endpoint in to the project, publish and then remove it to continue developing.
Pain in the ass!
(PS - still a problem in VS 2012 Ultimate)
Edited bysigolFriday, August 17, 2012 1:39 PMadding VS version
Yes I can validate that all the following have to be true to get the error (I'm using github not TFS):
checkout azure project to new machine (mine is Win8 RTM with VS2012 and Azure SDK June 2012 SP1)
have a SSL endpoint in the web role, doesn't seem to matter if it's in addition to HTTP or if by itself
On starting debug, you receive: Invalid class string (Exception from HRESULT: 0x800401F3 (CO_E_CLASSSTRING))
Then compute emulator will shutdown
Note that even if you close VS2012 afterward, MSBuild will still have multiple processes running in task mgr... which I've tried closing and testing again. Also, I've updated NuGet packages for recent updates to Azure Configuration Manager.
Workaround: Remove SSL endpoint from web roles while debugging. Haven't tried adding SSL endpoint back and pushing to Azure, but I imagine this is just a local SDK issue and not related to proper functioning on Azure.
I too encountered this issue. The symptoms looked the same - Azure emulator worked fine running with an HTTP endpoint, but failed as soon as an HTTPS endpoint was added, all using IIS express.
The solution I found that worked was installing IIS 7. It doesn't need to be running - you can just set the service startup mode to manual and never actually use it. Unfortunately I haven't had a chance to go through and work out exactly which component
of IIS fixes it - I just installed the default components through Control Panel --> Turn Windows Features On or Off.
Once it's installed, everything works fine. I've used this solution twice, once on VS2010/Win7 and once (just now) on VS2012 Premium / Win8 RTM.
Hope this helps.
Proposed As Answer byBenjimawooMonday, August 20, 2012 7:55 AM
Marked As Answer bysigolMonday, August 20, 2012 7:54 PM
This worked for me as well after I figured out full IIS was the one thing different between my Win7/VS2012RC install and my Win8/VS2012 one. Also at some point I started getting an error in addition to the ones described above that led me to needing
full IIS. Note in my Azure project and Web projects I've still got IISExpress selected. I installed the same IIS features that were on my old dev box, so not sure which one actually fixed the issue.