I created an online service at https://spjeff.azurewebsites.net/ which generates a MVC WebAPI 2.2 project with the name you enter. A custom ZIP file is generated server side with your custom name for the Project, Namespaces, Assembly, and sent to the browser for download. Best practices are already enabled such as:
Minimal packages and dependency
Zero MVC boilerplate
Lean mean API ready for dev & prod
From there double click SLN and begin coding. Enjoy!
While enabling the CSSA (Cloud Search Service Application) I came across this error during first full crawl after successfully completing the on-boarding steps outlined at https://blogs.msdn.microsoft.com/spses/2015/09/15/cloud-hybrid-search-service-application/ with PowerShell scripts. The Azure plugin was unable to crawl on-premise content. Root cause was proxy server configuration, which needs to be consistent across three places. Hope this helps!
An unexpected error occurred in the Azure plugin. This item will be retried in the next incremental crawl. ( AzureException AzurePlugin was not able to get Tenant Info from configuration server; SearchID = B056F137-1C77-4792-B402-256B615DBE82 )
By running PowerShell commands “Set-SPLogLevel” and “New-SPLogFile” I was able to get verbose URL for the CSSA crawl process. Here are the entries showing inability to communicate over the proxy server to the Internet.
12/08/2016 15:36:31.55 mssearch.exe (0x195C) 0x0B18 SharePoint Server Search Crawler:Azure Plugin amn0f High AzureServiceProxy::GetCerts caught AggregateException: The ServicePointManager does not support proxies with the myproxy scheme.
12/08/2016 15:36:31.55 mssearch.exe (0x195C) 0x0B18 SharePoint Server Search Crawler:Azure Plugin amn0g High AzureServiceProxy::GetCerts: Failed to get encryption certificates from cert server https://tenant.sharepoint.com for realm 67d7b889-884d-4c2a-a8d8-3ff81f37b497, documents will be send unencrypted (if unecrypted submit is allowed)
12/08/2016 15:36:31.55 mssearch.exe (0x195C) 0x0B18 SharePoint Server Search Crawler:Azure Plugin amn0h High AzureServiceProxy::GetAzureTenantInfo caught AggregateException: The ServicePointManager does not support proxies with the myproxy scheme., unable to get EndpointAddress, submit is blocked
12/08/2016 15:36:31.55 mssearch.exe (0x195C) 0x0B18 SharePoint Server Search Crawler:Azure Plugin amn0i High AzureServiceProxy caught Exception: *** Microsoft.Office.Server.Search.AzureSearchService.AzureException: AzurePlugin was not able to get Tenant Info from configuration server at Microsoft.Office.Server.Search.AzureSearchService.AzureServiceProxy.GetAzureTenantInfo(String portalURL, String realm, String& returnPropertyValue, String propertyName) at Microsoft.Office.Server.Search.AzureSearchService.AzureServiceProxy.SubmitDocuments(String azureServiceLocation, String authRealm, String SPOServiceTenantID, String SearchContentService_ContentFarmId, String portalURL, String testId, String encryptionCert, Boolean allowUnencryptedSubmit, sSubmitDocument documents, sDocumentResult& results, sAzureRequestInfo& RequestInfo) ***
Proxy server settings need to be confirmed in three places. The crawler was attempting to use “myproxy:8080” DNS names when it actually needs URL format “http://myproxy:8080”
1) Internet Explorer
Tools > Options > Connections > LAN Settings
Provide either PAC URL (proxy auto config) or proxy server DNS name.
2) Command Line
NETSH WINHTTP SHOW PROXY
NETSH WINHTTP SET PROXY PROXY-SERVER=”myproxy:8080” BYPASS-LIST=”*.company.com;<local>”
3) Dot Net Global [machine.config]
Last week many great technical guides were released on the MS Download Center. They describe the business benefits of new technology and technical steps to implement. Below are links with description and download for each (ZIP/PDF/PPT/DOC).
Fantastic visuals here quickly communicate the benefits of Azure, Dev Ops, and modern IT design.
I recorded a quick getting started video for this Microsoft GitHub sample. Walks through all the steps and even shows the SQL Local DB storage and how to verify security with Fiddler Composer sending test HTTP traffic.
This pattern is a great way to enhance Officer 365 SharePoint team sites with advanced functionality. Host AngularJS single page application (SPA) on the front end along with an Azure AD secured WebAPI backend. Lots of potential for replacing traditional WSP farm solutions with new cloud development patterns.