Home Dashboard Directory Help
Search

Azure Website Not Populating in LightSwitch Publishing Wizard by babloo1436


Status: 

Closed
 as Fixed Help for as Fixed


1
0
Sign in
to vote
Type: Bug
ID: 771319
Opened: 11/15/2012 8:25:31 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Hello LightSwitch Team

I am trying to deploy a lightswitch V2 demo application (Contoso Moving) into Windows Azure as a Website. Everything works good but when I reached to Service Configuration Tab in the publishing wizard, my website (what I created in Windows Azure) not populating in the dropdown box. I hit Refresh many time but no result.

I have followed the tutorial demonstrated by Beth (http://blogs.msdn.com/b/bethmassi/archive/2012/10/18/easily-deploy-your-lightswitch-apps-to-azure-websites-in-3-minutes.aspx?wa=wsignin1.0&CommentPosted=true#commentmessage) and also followed the doc. which is in there Contoso Moving project folder. But still unable to deploy the app as a website.

OS - Windows 8 x64
Details
Sign in to post a comment.
Posted by babloo1436 on 12/4/2012 at 2:26 AM
@wa2012

Thank you for the link. And yes its working as expected. But still waiting for the official procedure to publish lightswitch application as Windows Azure Website.

Regards
Posted by Microsoft on 12/4/2012 at 1:43 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Microsoft Visual Studio Connect Support Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 11/29/2012 at 4:52 PM
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)
Posted by wa2012 on 11/17/2012 at 4:47 AM
Hi, Good Morning! This is a problem began earlier this week with an update to the Azure Web Site preview release. See the link solution alternative: http://social.msdn.microsoft.com/Forums/en-US/lightswitch/thread/18f02441-f366-4524-be10-50aaea2ed8e6
Sign in to post a workaround.