Given this.. http://www.bing
.com/videos/wat ch/video/apps-i n-a-nutshell-fo r-office-2013-a nd-sharepoint-2 013/10tw7mn76 Possible to test REST without a local VS 2012 and SP 2013 install?
I followed the steps to deploy the sample app provided. On trying to load the App, I get an error as follows: This page can't be displayed •Make sure the web address is correct. •Look for the page with your search engine. •Refresh the page in a few minutes. •Make sure TLS and SSL protocols are enabled. Go to Tools > Internet Options > Advanced > Settings > Security •Make sure the web address is correct. •Look for the page with your search engine. •Refresh the page in a few minutes. I have tried all possible options to no avail. Can you let me know where I am going wrong
Possible areas to consider: 1.) Are you deploying this to an Office 365 Developer Site? This sample uses OAuth, and right now an O365 site is required for that. A Developer Site on Office 365 is what you need to deploy this from Visual Studio. 2.) When you look at your appmanifest.xml file, does the name of the .aspx page (likely "Home.aspx) that is entered as the Start page url match exactly with your Web project's page? 3.) Your Web project has a default SSL url provided by VS (look in the project properties). It should look something like this: https://localho
st:44312/. When you are running the F5 debugger, can you reach this URL (https://localh ost:44312/Home. aspx) from your browser? Is this the URL you go to when you launch the app from your developer site?
I have tried on on-premise and on O365 developer site. When trying to deploy an autohosted app on O365 developer site, it works properly. When I click F5 on that solution, I end up with the same error as mentioned above. This is really blocking my debugging options in a provider hosted and auto hosted APPs
I can reproduce this by going into Internet Options, clicking on the Advanced tab, and unchecking the Use SSL 3.0 and Use TLS 1.0 options under Security. The problem goes away when I check those options. Could you take a look at your browser's security settings and make sure that you have enabled the SSL and TLS protocols?
I verified that the options for SSL 3.0 and TLS 1.0 are checked under Security. The problem continues to occur and I am unable to figure out a way to resolve this issue.
Just to make sure that I am not misunderstandin
g, does this happen when VS attempts to launch your developer site, and before you reach the page where you are presented with the "trust it" option? Or does it happen after you click "trust it" and then attempt to launch the app from the site contents apge? Also, are you seeing this behavior with other provider-hosted apps? Have you been able to do F5 debugging with any other provider-hosted app? Or more simply, can you create an App for SharePoint by using File -> New Project and selecting the App for SharePoint option? You should then be prompted to add the url of your developer site, and then select "Provider-hoste d" from the app type drop-down. VS will create a basic provider-hosted app that will run with F5 debugging. (You will got to the "trust it" page, and after trusting the app, you will go to the Site Contents page, from which you should be able to launch the app.) We should probably start from this simple base and if that works, I can try to track down what about this sample would be creating your problem.
Ok I will brief you about the steps that I have tried so far. SP Online (O365) from local machine (no SP installed): - Create a simple auto hosted app - Right-click and deploy the solution - Web gets deployed in Azure successfully and I'm redirected to the "trust it" page - The App functions properly - Create a simple auto hosted app - Click F5 to debug - The page with "trust it" option is displayed and then click "trust it" - In the Site contents, page I click the App - The page with 'localhost' in the URL is loaded with the error as below: This page can't be displayed •Make sure the web address https://localho
st:44305 is correct. •Look for the page with your search engine. •Refresh the page in a few minutes. •Make sure TLS and SSL protocols are enabled. Go to Tools > Internet Options > Advanced > Settings > Security Fix connection problems
Thanks for passing along that information. Can you reach https://localho
st:44305 by entering it directly into your browser address bar? It looks like something might be wrong with IIS Express (the server that runs on https://localho st:44305 when you are running the debugger) on your computer.
This might be related to a known issue. Could you try changing the permissions on your %windir%\System
32\Drivers\etc\ hosts file to read only? It could be the case that VS is adding an entry to that file that is breaking //localhost:443 05 for you.
The error occurs when I try to load using the https://localho
st:44305. There is another URL viz. http://localhos t:19181 which when I replace in the page URL, the debugging works; but, there is a null token returned every time. So, I am unable to debug the solution at all. Let me know if there are some specific configuration steps that need to be performed in order to debug an autohosted app code from my local machine. NOTE: My local machine does not have SharePoint installed.
You won't get a token unless you launch the app from the SharePoint Site Contents page, and that page will open the SSL URL on //localhost. So when you see that null token error on http://localhos
t:19181, that is expected behavior. You should see the same null token error if you type https://localho st:44305 directly into your browser address bar while you are debugging. I asked if you could open https://localho st:44305 by manually typing it into the address bar just to see if the page would load at all (with the null token error). When you type https://localho st:44305 into the browser address bar, do you see exactly the same thing that you see when you launch the app from the site contents page? If this is the case, then this would indicate that there is a problem with the IIS Express server running at https://localho st:44305 when you are debugging. And if the problem is with https://localho st:44305, that could mean that you are seeing a known problem that has to do with Visual Studio adding an entry to the hosts file located here on your local computer: C:\Windows\Syst em32\drivers\et c\hosts. If this is the problem, one way of working around it (for now) would be to navigate to C:\Windows\Syst em32\drivers\et c, right-click on the hosts file, and check the Read-only attribute checkbox at the bottom of the General tab. Could you try that?
I tried setting 'Read-only' checkbox on the hosts file; but, no luck yet. When I type https://localho
st:44305 into the browser address bar, I see the same error message.
Is it possible that you have any other certificates installed for localhost? If you run certmgr.msc (from Start-> Search box), can you find another certificate for localhost? The problem appears to be specific to your environment, so at this point this appears to be related to a local configuration, perhaps something related to IIS Express or to installed certificates on your computer.
I know this must be something in my setup but I keep getting these two errors when I build this sample: The type or namespace name 'CodeDom' does not exist in the namespace 'System' The type or namespace name 'ComponentModel
' does not exist in the namespace 'System' It wants an assembly reference but as System is already referenced, I'm stumped as to why this is happening. I'm trying to deploy to my Office 365 Preview Developer site. Thanks!
Which version of the .NET framework are you targeting for the app project? In this sample, the app project should target .NET 4.5 and the Web project should target .NET 4.0. You are probably seeing the System reference in the Web project, which comes from the 4.0 framework, but these errors are probably coming from the app project build, which should be targeting .NET 4.5.