SharePoint 2013: Where is the Recycle Bin?

Introduction
This article explains the two-stage recycle bin in SharePoint.

Looking for the Recycle Bin in SharePoint 2013? You won't find it in its previous location (Quick Launch with the All Site Contents).

In a SharePoint site, the Recycle Bin provides temporary storage for all items deleted from that site. The Recycle Bin can be accessed from the following the Quick Launch Bar on the left of the screen. SharePoint offers a two-stage Recycle Bin so items that are deleted from the end user Recycle Bin may still be recoverable from the site collection Recycle Bin by a site collection administrator.

First StageThe Recycle Bin is accessed. On the SharePoint site, click Site Settings and select “Site Contents”. The link is then available from the “Site Contents” page. Alternatively, this can be accessed by adding “/_layouts/15/Recyclebin.aspx” or “/_layouts/15/viewlsts.aspx” to the end of your site's root URL.





Second Stage
The Second Stage Recycle Bin is available to site collection administrators only and can be access from “Site Actions” > “Site Settings”. Alternatively, this can be accessed by adding “/_layouts/15/AdminRecyclebin.aspx” to the end of your site's root URL items.

Go to the Site Collection Recycle Bin:



As a site collection administrator, I go to Site Actions (or the gear) Site Settings in order to get to the Site Collection Recycle Bin link. Click the Site Collection Recycle Bin link as in the following:



When I click on the Recycle Bin link in the Site Collection Administration section of the Site Settings page I am taken to the Site Collection Recycle Bin page. Go to the Site Collection Recycle Bin as in the following:



From here I can see all the items that have been deleted and are sitting in the first stage or end user Recycle Bins, as well as those that have been deleted from those locations and are now sitting in the second stage Recycle Bin. I click the link "Deleted from end user Recycle Bin".

Identify SharePoint 2013 Foundation or Server (Version)

IntroductionIn this article you will learn how to identify the SharePoint 2013 Foundation or Server (Version).

It's crazy that there are easy ways to determine what the Edition (SKU) of SharePoint 2013 is that you are running. I have come across this several times, where someone asks me a SharePoint question. Not that I want to answer a question with a question, but the first thing I ask is what version of SharePoint they are running.

The following code example demonstrates how to retrieve the registry key of the installed SKU of SharePoint 2013, Microsoft Project Server 2013.

Open the SharePoint Management shell and type in the following command.



In this case "9ff..." is SharePoint Foundation 2013 (that would always be present even with Server) and "b7d..." is the SharePoint Server 2013 Enterprise.

Here are all of the products GUIDs.

You will get the GUIDs. Find your GUID from the following list. That will be your installed SharePoint version.



There is also another way to find the product GUID from the registry.

Procedure

• Open Regedit.
  
• Navigate to HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\InstalledProducts
  
  
  
• Compare the GUIDs with these:
  
  

Show Tree View Navigation SharePoint 2013

Introduction

In this article you will learn how to show Tree View Navigation in SharePoint 2013.

Tree View

Sometimes the default SharePoint 2013 Quick Launch is not enough to assist users to navigate to a SharePoint site. The tree view is an extra navigation option that provides a hierarchical view of all sites, lists and libraries in the site, including any sites below the current site level, such as the Document Center site template, display tree view navigation by default.

Do one of the following:

1. On the SharePoint site, click Site Settings 

2. In the Look and Feel column, click Tree View.

3. Do one of the following:

• To show the tree view, select the Enable Tree View check box and then click OK.

• To hide the tree view, clear the Enable Tree View check box and then click OK.
  
  

Note:
If you want to display only tree view navigation, clear the Enable Quick Launch check box. If both the Quick Launch and tree view navigation are enabled, the tree view navigation will appear underneath the Quick Launch. Now you can see the Tree view instead of Quick launch.

4. Now you can see the Tree view instead of Quick launch.

Overview of SharePoint 2013 Developer Site Template

Introduction 

In this article we explore a new template in SharePoint 2013 for the developer site templates. This site template is focused on Apps for Office development.

Developers can build, test and publish their apps here. Here you can deploy apps for SharePoint from Visual Studio 2013 to the developer site and you don't need to create an App Catalog site since the developer site template by default creates an App Catalog library. The developer template is available under the collaboration site template.

How to create a site using this template



Why to creatie an App
If you are planning to do remote development/deployment like in the cases were VS2012 / VS2013 and SharePoint 2013 are not installed on the same computer you will be needing a root site collection created using Developer Site Template. (If VS2012 and SharePoint 2013 are on the same computer this is not a requirement).

1. What Remote Development and Deployment?
   
   Yes you heard it right VS2012 and VS2013 support the deploying of sandbox solutions to a remote SharePoint site. When you create a SharePoint 2013 Project using VS2012/VS2013, you will get an option to publish to a remote SharePoint Site when you right click on the SharePoint Project as shown below:
   
   
   
   Remote Publishing from Visual Studio 2012
2. Publishing App in App Catalog 
   
   Upload the app file to a Developer Site of SharePoint 2013 in the “Apps in Testing” Library.
   
   

SharePoint 2013 Site Template ID List For PowerShell

Introduction 
In this article we explore creation of a new Site Collection or Web Application by PowerShell, we have the option to apply the Site Template directly.
However, for PowerShell to accept it, you must provide it the Template ID (for example:APPCATALOG#0). 

When creating a new site collection from Central Administration, we can select a site template from the Template Selection section. But sometimes we may need to create sites from the PowerShell using CMDlet commands. At that time we need to provide the site template name not the site template Title.

One can easily use the Get-SPWebTemplate command to get a list of all the templates in the SharePoint environment.



For example, to create an App Catalog site:

New-SPSite -Url http://sp:1001/sites/AppCatalog -OwnerAlias "serverName\sp_admin" -Name “App Catalog site" -Template "APPCATALOG#0" 

Here is the SharePoint 2013 Site Template ID List for PowerShell:

Create App Catalog Site in SharePoint 2013

Introduction 
This article explains how to create an app catalog site in SharePoint 2013 using SharePoint 2013 Central Administration/PowerShell. An app catalog site contains a special type of Document Library that is used to upload and store app package files. There cannot be more than one App Catalog site collection in a web application or each web application can have only one App Catalog site collection. There can be multiple App Catalogs in a farm.

Procedure

1. Then this will open the Create App Catalog page, there you can enter the Title, Description, URL and Site Collection Administrator and then click on "Create". 
   
2. Then choose Apps from the left hand side and this will open the Apps page. There click on Manage App Catalog from the App Management section in the Apps page.
   
   
   
3. Then in the Manage App Catalog page click on create a new app catalog site and then click on OK. Before that you can also check the Web Application or if you want you can change the web application. 
   
   
   
4. Open SharePoint 2013 central.
   

Create App Catalog Using Windows PowerShell
New-SPSite -Url http://sp:1001/sites/AppCatalog -OwnerAlias "serverName\sp_admin" -Name “App Catalog site" -Template "APPCATALOG#0" 

Summary

The SharePoint 2013 app catalog site would be successfully created using centraladministration/PowerShell by following this article.

Pass Query string value from SharePoint Page to provider hosted app in SharePoint 2013

Instruction 
In the new SharePoint App model, web parts are replaced with app parts. The problem is they don't have an equivalent to Web Part Connections. So how can you pass parameters from one part to another?

To answer this you have to consider several things:

• App parts are basically small applications that are presented in your SharePoint site through iframes.
• Each app is running in a separate domain and so are their app parts. Because of this any direct manipulation through some javascript code is out of the question because it would mean cross-domain scripting and all you would get is an "access denied" message.

This post explains about how to create an user defined custom property for a Client Web Part in SharePoint 2013 Provider Hosted App and its relationship with the query string and the standard tokens. The option for getting the data from Client Web Part's custom property is bit different from Farm based or Sandboxed Web Parts. In Provider Hosted App, the value of the property has to be accessed via query string.

Steps:

1. Add Client web part to app part.
2. Open element.xml and add one Property right click on Client web part, then Custom properties.
   
   
3. Go to host web where you are having query string.
4. Add App part.
5. Add one script editor web part. It should be below to App.
   
   
6. Now in the App landing page load read the Query string value in .Cs file.
   
   1. protected void Page_Load(object sender, EventArgs e)  
   2. {  
   3.    string _ID = Request.QueryString["ID"];  
   4. }