One of the biggest problem we face in our SharePoint environment is site retention. Whenever our users request us with new site collections/sites, we tend to ask to them to clear the security test and we create a new site collection or site. The problem is, managing the site collections/sites.
Lots off users request sites for either long term projects, short term projects, team spaces, etc., and then they tend to forget to manage it. These sites will reserve a big amount of space, in addition to that is a mailboxes if they have.
So finally, to resolve all the above issues (till certain point), SharePoint 2013 has came to rescue. The new “thing” called SharePoint Server 2013 Site (or Site Collection) Policy.
As you can see from the above figure, it allows you to create a Site (or Site Collection) Policy which can be applied to restrict site’s long living life.
Site Closure and Deletion
The difference between site closure and site deletion is, site closure means that when the site is put into the closed mode, the site will NOT be active anymore, means the site is not being updated or being actively used. You can also manually put the site on closure but to reopen the closed site, you will have to go through the site collection administrators. When the site is being put onto the closure mode, the system will put site into read-only mode as well. (in this case as well, only site collection administrators will be able to reopen the site).
Though the users/admins/developers can continue using the site as well as it’s contents, whereas site deletion means the site will be permanently deleted with all of it’s content.
Now, sometimes you will have to postpone the above activity, in that case, the site owner can manually delay the site deletion for a particular period of time (assign by the site policy), if not, then the e-mail would be sent to the site owners before deletion of the site and site will be deleted if no action taken.
By using the above technique, you can always apply site collection policies to each and every new site being requested, which will be deleted if not being used for a certain period of time, ensuring you will save space on your server. This is also helpful when you want to create a site but doesn’t want to allow any changes.
You can put the site into the closure mode, making it a read-only site and avoid the deletion (I wouldn’t recommend that ), once you define the policy to be applied, you can either directly apply it using the publishing feature from the content hub or apply them during the site creation time where in users will have an option to select. Check out the Configuring Self Service Site Creation in SharePoint 2013.
Once you set it up, you can go to Central Administration -> Self-Service Site Creation Administration and choose from below three options to make it available to the users.
Once applied, the users will be able to choose the policies while requesting a new site.
Thanks & have fun!!
Reference : Steven Boyle
The SharePoint Code Analysis Framework (SPCAF) provides tools to analyze SharePoint code. This includes
- SharePoint solutions (.wsp) for SharePoint 2007 / 2010 / 2013
- SharePoint 2013 apps
SPCAF cannot only analyze assemblies like other tools as FxCop or SPDisposeCheck. It can also analyze all the XML code in SharePoint packages like Features, ContentTypes, ListTemplates and all the other files like controls (.ascx), pages (.aspx) and master pages (.master) etc.
SPCAF can be used directly in Visual Studio 2012 or 2010 to analyze SharePoint projects. It also provides a client application to analyze existing WSP packages, can be integrated into a Team Build via a custom build activity, it can be run on command line or as MSBuild task during each local build.
- Contains ~300 rules to validate SharePoint code for correctness, solution design, best practices etc..
- Creates dependency diagrams in DGML to visualize dependencies within SharePoint code
- Can be seamlessly integrated into your development process
- Provides a client application to analyze WSP and APP files.
- Can also be run during a Team Build (supports TFS 2010 and TFS 2012)
- Can be extended with custom rules or custom metrics
Sample analysis results
- Rules reports shows errors and warnings Open sample report
- Dependency diagram visualizes package dependencies Open sample report
- Inventory reports lists all contents of the packages Open sample report
- Metric reports shows complexity and amount of elements in the code Open sample report
Who should use it?
- SharePoint Architects can ensure proper application design and detect violations against best practices
- SharePoint Developers can ensure that their code is correct and that errors in XML code can be found early directly in Visual Studio and not only after deployment to SharePoint.
- SharePoint Quality Assurance can ensure that WSP packages are developed according to the best practices and the e.g. Customization Policies are not violated.
- IT Pros can ensure that the WSP files does not contain “dangerous” code and that they can install the packages without fear. The inventory reports gives a detailed overview about the contents in the packages and is a good documentation of the code.
Use SPCAF directly in Visual Studio
Get Errors and Warnings and open the files directly in VS
Use the client application to analyze existing WSPs or APPs
Download content for ASP.NET, Office, SQL Server, Windows Azure, SharePoint Server and other Microsoft technologies in e-book formats. Reference, guide, and step-by-step information are all available. All the e-books are free. New books will be posted as they become available at here
Back in June, Pluralsight announced a special training benefit for MSDN designed to provide MSDN subscribers with access to 20 of their most popular courses.
Previously only available in the US, today they’re expanding this benefit to MSDN subscribers worldwide through December 11, 2012. Now you can access this benefit across the globe, regardless of location! See the notes below on who is eligible.
Based on our feedback, they’ve also worked with Microsoft to enhance this custom 12 month training subscription with several new Visual Studio 2012 courses.
The Pluralsight Starter Subscription for MSDN now contains 25 popular courses. The five new courses they added include:
- Introduction to Visual Studio 2012 – Part 1
- ALM with TFS 2012 Fundamentals
- ALM for Developers with Visual Studio 2012
- Microsoft Fakes Fundamentals
They’ve simply added these new titles to the original set of courses made available in June. If you’ve already taken advantage of this offer, you don’t have to do anything to get these – you’ll see the new courses show up in your account next time you login to Pluralsight.
To take advantage of this limited-time training benefit, redeem your Pluralsight Starter Subscription for MSDN by December 11, 2012:
Feel free to download this PDF describing the benefit and email it to your friends and coworkers so they can take advantage of this offer too.
The Pluralsight Team hope we enjoy this MSDN training benefit!
Who is not eligible for this offer?
This video shows the installation and initial configuration process of SharePoint Server 2013. We start with installing the software prerequisites then move on to installing SharePoint Server 2013 Technical Preview. Then we proceed with the farm creation and configuration process. We end up finally with a Site Collection to start the collaboration process.
Developer-focused how to training and walkthrough videos about Office 2013 and SharePoint 2013 including changes and new features for search, social, ECM, WCM, and REST. Learn about apps for Office and SharePoint.