locked
Can I Deploy my SQL Server Database with a Lightswitch 2013 Desktop App? RRS feed

  • Question

  • Hi,

    I originally tried to deploy my Lightswitch 2013 desktop app to an Azure Web Site.  I received the permission denied to view this directory message.  I thought it might be best to instead deploy the desktop app as a .xap and have the user install on his machine.  However, the publish wizard prompts for a connection string either to Azure (where my user's IP address won't be authorized), or to a database server on his network etc.

    Question:

    1.  For those of you who have deployed to Azure, how did you manage it without receiving the permission denied error?

    2.  Can the SQL Server database be added to the published .xap file so that it installs on the user's machine embedded as part of the app?

    Thanks much for your help and guidance.

    Thursday, November 14, 2013 6:35 AM

Answers

  • Simplest suggestion would be to make a new project with just 1 table and a screen and publish that to see if you get the same error, the publish wizard is quite straight forward, for troubleshooting don't use https or certificate signing during the publish process.

    This should at least tell you if it's something in the project, if not then it's VS.

    There has been a new Azure SDK released, you can check for an update using WPI http://www.microsoft.com/web/downloads/platform.aspx

    Thursday, November 14, 2013 7:00 AM

All replies

  • Hi SChilders

    I have used Azure a few times and never had the problem you mention, it's still the simplest form of publishing for me as a novice anyways.

    Did you use the x.azurewebsites.net/HTMLClient or x.azurewebsites.net/DesktopClient path to access your application ?

    Thursday, November 14, 2013 6:47 AM
  • Hi,

    I originally used the HTML client.  However, I also tried the Desktop client deployment path and received the same error after deployment to Azure.  Do you have any suggestions on debugging?

    Thanks,

    Sid

    Thursday, November 14, 2013 6:51 AM
  • Simplest suggestion would be to make a new project with just 1 table and a screen and publish that to see if you get the same error, the publish wizard is quite straight forward, for troubleshooting don't use https or certificate signing during the publish process.

    This should at least tell you if it's something in the project, if not then it's VS.

    There has been a new Azure SDK released, you can check for an update using WPI http://www.microsoft.com/web/downloads/platform.aspx

    Thursday, November 14, 2013 7:00 AM