locked
You do not have permission to view this directory or page after upgrading to VS 2013 RRS feed

  • Question

  • Hellow Chris, I'm having the same problem, VS2012 lightswitch app (silverlight client) redeployed to Azure and the error is the same: "You do not have permission to view this directory or page."

    It is an upgrated V3 Ligthswitch Website (Silverlight Client) at: http://qacpro.azurewebsites.net

    Any solution?

    alex_sotam@outlook.com, digepep@outlook.com

    Wednesday, November 13, 2013 7:25 PM

Answers

  • After upgrading from VS 2012 to VS 2013, your Silverlight client will be deployed to:

    http://qacpro.azurewebsites.net/Client

    If you add an HTML Client to this project, when you publish the app you will have the SL client deployed there and the HTMLClient deployed to:

    http://qacpro.azurewebsites.net/HTMLClient

    More specifically, your client URL will end with whatever the name is of the specific Client project.


    David Kidder | Senior SDET | Microsoft | LightSwitch

    • Proposed as answer by Dave KidderModerator Wednesday, November 13, 2013 8:12 PM
    • Marked as answer by DIGEPEP Wednesday, November 13, 2013 8:24 PM
    Wednesday, November 13, 2013 8:12 PM
    Moderator

All replies

  • After upgrading from VS 2012 to VS 2013, your Silverlight client will be deployed to:

    http://qacpro.azurewebsites.net/Client

    If you add an HTML Client to this project, when you publish the app you will have the SL client deployed there and the HTMLClient deployed to:

    http://qacpro.azurewebsites.net/HTMLClient

    More specifically, your client URL will end with whatever the name is of the specific Client project.


    David Kidder | Senior SDET | Microsoft | LightSwitch

    • Proposed as answer by Dave KidderModerator Wednesday, November 13, 2013 8:12 PM
    • Marked as answer by DIGEPEP Wednesday, November 13, 2013 8:24 PM
    Wednesday, November 13, 2013 8:12 PM
    Moderator
  • After upgrading from VS 2012 to VS 2013, your Silverlight client will be deployed to:

    http://qacpro.azurewebsites.net/Client

    If you add an HTML Client to this project, when you publish the app you will have the SL client deployed there and the HTMLClient deployed to:

    http://qacpro.azurewebsites.net/HTMLClient

    More specifically, your client URL will end with whatever the name is of the specific Client project.


    David Kidder | Senior SDET | Microsoft | LightSwitch

    Wao....!!! That was the fastest, mor simple answer I ever had.... Thanks a lot Dave you Rock bro!!!!

    Alexander Matos

    Wednesday, November 13, 2013 8:25 PM
  • Also note that to make sure that your upgraded website doesn't have any remnants from a previous LightSwitch version, you should check the "Remove additional files at destination" checkbox in the Publish Wizard.

    This will remove anything from the target location that is NOT part of the LightSwitch project deployment (don't do this if you manually push items to the site or if your app generates content that resides in the web app's folder).


    David Kidder | Senior SDET | Microsoft | LightSwitch

    Wednesday, November 13, 2013 8:25 PM
    Moderator
  • And important note:

    The same happens with VS 2012 upgrading the project to LigthSwitch v3


    Alexander Matos

    Wednesday, November 13, 2013 8:27 PM
  • Also note that to make sure that your upgraded website doesn't have any remnants from a previous LightSwitch version, you should check the "Remove additional files at destination" checkbox in the Publish Wizard.

    This will remove anything from the target location that is NOT part of the LightSwitch project deployment (don't do this if you manually push items to the site or if your app generates content that resides in the web app's folder).


    David Kidder | Senior SDET | Microsoft | LightSwitch

    Thanks for that note, I'll take into account....

    Alexander Matos

    Wednesday, November 13, 2013 8:30 PM
  • I had the same problem and lost a lot of time trying to deploy an upgraded (to VS2013) App.

    I wish there were more info about it, it does not say anything in the "Official documentation" here http://msdn.microsoft.com/en-us/library/vstudio/gg615263.aspx

    So David, does this mean we should tell the users the new URL ending in /Client or /HTMLClient, theres is no workaround for making the "old" URL work? (maybe putting a response.redirect in default.aspx)

    cheers,

    Nicolás.

    Friday, November 29, 2013 11:12 PM