none
SharePoint Hosted App - The Site URL property of the project has not been set. In the Properties window, enter the URL for a SharePoint server

    Question

  • We're not sure where we are going wrong here....  We're trying to setup a SharePoint Hosted App and leverage TFS as our source code respository. The initial setup works great just like any traditional development effort - create solution, build deploy, debug, check in to TFS. Then it breaks down for us when another developer does a 'get latest' they receive the following error when the solution opens:

    The Site URL property of the project has not been set. In the Properties window, enter the URL for a SharePoint server

    They are able to set the Site URL to the teams Developer site collection and build the solution successfully. Although when they debug (F5) the following message is displayed

    Sorry,
    something went wrong

    Invalid URL: ~appWebUrl/Pages/Default.aspx?SPHostUrl=http%3A%2F%2Fserver%2Fsites%2Fdds&SPLanguage=en%2DUS&SPClientTag=0&SPProductNumber=15%2E0%2E4420%2E1017.

    We only run into this when using TFS.  When individual developers create and store the solutions locally there is no issue it's just when we use TFS for our source code repository so a team development effort.

    Thoughts?

    Wednesday, August 28, 2013 4:57 PM

All replies

  • Did you set up the on-premise environment for apps for SharePoint? how about isolated app domain?

    http://msdn.microsoft.com/en-US/library/fp179923.aspx

    Wednesday, August 28, 2013 8:10 PM
  • Yes, we are able to create, debug, deploy,etc... fine when we are not using TFS as our source code repository. The problems begin when a solution is checked into TFS and then checked out or when someone does a 'get latest'.  

    • Edited by adm12 Thursday, August 29, 2013 1:49 AM
    Thursday, August 29, 2013 1:46 AM
  • I assume all the developers have SharePoint installed...did they all set it to the same URL? ditto? Does this happen every single time?

    Thursday, August 29, 2013 10:28 PM
  • OK, SharePoint App development is new to me as you can tell but I think we made progress... Do all developers have SharePoint installed? No, we are following this setup http://msdn.microsoft.com/en-us/library/jj220047.aspx

    What we discovered was if each developer has their own Site Collection the issues disappear. We originally thought we could use one site collection that all developers can use but this approach causes issues when working on the same app. I'm still digging for for info as to why so any insight would be helpful.

    Here's the scenerio -

    developerA debugs the app (F5) visual studio does a deploy - uninstall - install of the app the first time after that visual studio will just do a deploy (assuming an update app is done) everything is working great. Then developerB goes to debug a change they made and visual studio does a deploy - uninstall - install developerB is able to debug the app.  Then developerA makes another change and goes to debug (F5) and visual studio only does a deploy and SharePoint displays the "Something went wrong....message".  If developerA closes visual studio and reopens and presses F5 a full deploy - uninstall - install occurs and developerA is working but now developerB is broken. It seems as though Visual Studio assigns an ID to your app and this gets reset every time Visual Studio is open.

    Does Visual Studio assign an ID to your app and this gets reset every time you open VS?  Is there a way to force a full deploy - uninstall - install when debugging an app? 

    Friday, August 30, 2013 1:11 AM
  • It is not specific to app development but any SharePoint development requires local SharePoint installation.
    Friday, August 30, 2013 2:51 PM