Thanks for the show! Always fun and interesting! Though you could cut back on the who's who jokes
I have to say I really like the idea of letting the community ask questions. I would love if this could be a fixed part of your show like tip-of-the-week In the spirit of one-question-only :
1a) Recently I tried to deploy a simple worker role that basically did nothing but wait. Still it took over several
minutes from "Initializing" to the "Ready" state was shown. This caused me to believe that my package was buggy. I actually used several hours to finally figure out that I just had to wait for like 5 minutes. Can you explain why starting an
app takes so long?
1b) Will there be some more diagnostics available for apps that don't even start? I know about IntelliTrace, but let's face it, not every company out there can afford the ultimate edition of VS2010... Many times I've uploaded packages that won't run for
some reason (forgot to change devstore, used a non-native dll ref without local copy and what have you). This is by far the biggest pain of the windows azure experience right now.
1c) On a related note to the question above, why does deploying a package first have a screen with a button saying "Processing..." and then afterwards shows a progress bar saying "deploying...". And when you click "Run" it says "Enabling deployment...".
What are all these seemingly identical processes doing?
1d) Still related to the above somehow, ehem... As mentioned, you thought about doing a piece on the service bus. Well, what about a piece about how to set up access from azure to your on-premise sql server? This is what every man, woman and androgynous
person wants and dreams of.. Well, at least until sql azure gets backup capabilities