SharePoint Destination

Please refer the below link to create different graphical representation of list data shown as bar chart, pie chart and so many...   https://support.office.com/en-us/article/SharePoint-lists-VI-Exciting-ways-to-display-your-list-data-4f24f5a6-9a82-497e-8965-6b9f98e03a01  

One of my colleague had an issue when trying to add an app by applying the custom master page as System Master Page. Here is what I asked him to refer it, Resolution: The key to fixing this problem is to make sure your master page includes: DeltaPlaceHolderLeftNavBar , PlaceHolderLeftNavBar , DeltaPlaceHolderPageTitleInTitleArea , and PlaceHolderPageTitleInTitleArea and that each of them is not set to Visible=False Reference : http://sharepoint.stackexchange.com/questions/98252/i-cant-get-custom-master-page-to-add-new-apps

http://nikpatel.net/2012/06/08/wiki-pages-vs-web-part-pages-for-sharepoint-intranet-content-pages/

Please refer the below link for training videos, http://sharepoint-videos.com/video-categories/all-sample-videos/  

Portqry.exe is a command-line utility that you can use to help troubleshoot TCP/IP connectivity issues. Portqry.exe runs on Windows 2000-based computers, on Windows XP-based computers, and on Windows Server 2003-based computers. The utility reports the port status of TCP and UDP ports on a computer that you select. It can be downloaded from here, http://ss64.com/nt/portqry.html

Instead of Response.End() use, Possible Solution1: Response.Flush(); HttpContext.Current.ApplicationInstance.CompleteRequest(); Note1: Response.End is a bad practice, it aborts the thread to bypass the rest of the operations in the http request lifecycle and it throws an exception Possible Solution2: Also try by giving value "true" in Response.End()     Possible Solution3: Replace Response.End() with HttpContext.Current.Response.End();

I have two site collections both hosted in same web application. But some disabled users are getting resolved in one site and not in other. Typically it should work as the web application can get tied to only one User Profile Synchronization. After analyzing got to know, UserInfo List which is at Site Collection level is not the same for both SiteCollection. Meaning - for one site UserInfo List was updated (Synched up with User Profile) long time back and so it still holds disabled users and so it is resolving the users. Other site - UserInfo List is synched up frequently and so old disabled users are deleted and hence it is not resolving the users. UserInfo List can be found in the url https://SiteName/_catalogs/users/simple.aspx This resolves the issue