Saturday, September 15, 2012 12:08 PM
Creating a SharePoint Hosted App, but Visual Studio will not deploy to a Host Named Site Collection (HNSC), it is possible to Publish and upload app to the HNSC and everything works.
I also noticed that SharePoint Designer 2013 cannot connect to the HNSC as well.
Are there known issues with HNSC?
Monday, September 17, 2012 11:41 PMHave you created the alternative access mappings for each site collection?
Tuesday, September 18, 2012 3:10 AMHost Named Site Collections do not have AAM, just the single host name.
Tuesday, September 18, 2012 11:22 AM
I assume you've seen this? It doesn't really answer your question; just a good reference. It's interesting to see this because I could've sworn I saw some documentation a couple weeks ago which stated you weren't supposed to use custom host headers in IIS with SharePoint 2013 but this screen cap is from SP2013 documentation as well so that must not be true.
- Edited by 02bluesuperroo Tuesday, September 18, 2012 11:24 AM
Tuesday, September 18, 2012 9:36 PM
What address is bound to your host named site collection? If it's 127.0.0.1, then it's not supported for the current release. You can change 127.0.0.1 to your actual IP address in the hosts file to work around it. Feel free to let me know if it doesn't resolve your problem.
Xiaoying is a program manager in Microsoft Visual Studio SharePoint Developer Tools team | This post is provided "as-if"
- Marked As Answer by MULTISY Sunday, September 23, 2012 12:42 PM
Sunday, September 23, 2012 12:47 PM
After creating wildcard DNS entry which the IP address of the SharePoint server, no more issues with VS 2012 debug deployment.
SharePoint Designer 2013 will stop working if an error occurs, but simply restarting will fix access problem, but I don't think this is a new problem; SPD has always had some kind of caching issue with all versions.