We hope you have recovered from that opening ceremony and are well into supporting your countries quest for medals! Many thanks to everyone who completed our SharePoint survey so far - we had a better response than we thought possible and have received some great comments. We've included one of the most surprising results in this newsletter and will work on providing a full analysis next week.
(psst. Don't forget to share using the buttons below).
SharePoint Manager 2013
SharePoint Manager 2013 is the third version of this massively popular tool. SharePoint Manager is a visual object model explorer that easily lets you see the property settings of nearly all of the public classes. It also allows some property values to be set. If you are a developer, or IT Pro it's well worth a look.
Link : SharePoint Manager 2013 Codeplex site
Survey Extended for one more week!
Wow - we are really blown away by the amount of replies we've had to the SharePoint survey so far! 330 and counting. So many of you have spent time filling in the Love and Hate questions, it has been great reading all of your responses, so thanks!
Due to last week being a big vacation week we didn't get near our normal viewing figures so we have decided to extend it for one more week to see if we can close in on 500 responses.
The survey will take less than a minute to complete and we are also giving a free book to a lucky winner. The responses so far are quite surprising - currently nearly 40% of you won't be implementing SharePoint 2013 for at least 2 years after its launch!
Link : Take the Survey
SharePoint offers a tremendous array of options for improving performance and efficiency of collaborative portal applications. Understanding the inner workings of the framework and its dependencies upon key infrastructure components, including servers, network connections, services, operating system components and databases, is vital to the success of any optimization strategy. Implementing basic performance enhancements as outlined in this paper can provide tremendous improvements to the operation and performance of SharePoint within the enterprise.
Get Free White Paper
One of the other most striking statistics from the survey is that quite a few of you answered "No" to our "Have you heard of DocRead?" question...now could be the time to change that ;)
SPSTech.net is the blog of Marcel den Ouden, who has 10+ years of experience with Microsoft products. In these years he has developed himeself to an experienced, certified system administrator. In the year 2011 he decided to specialize in Microsoft SharePoint products, in particular maintaining and configuring SharePoint farms.
Link : SPSTech.net
Enter your email address to subscribe to our mailing list.
Join the Group
As you read this book, we think you will find that there are a lot of exciting enhancements and new capabilities engineered into SQL Server 2012 that allow you to greatly enhance performance and availability at a low total cost of ownership, unlock new insights with pervasive data discovery across the organization and create business solutions fast—on your terms. Download Free Book
"I have an Asp.net page with a button on it. Clicking the button opens up a word document in MS Word from a document library. Users can edit the document, save, and close it. I need to detect that the word document is closed before the users can navigate from the asp.net page. I understand that I can use event recievers to look at the modified date of the document, but I also need this to work if users open the document and closes it without saving. Is there any event that I can use to detect when a word document is closed. I'm looking into short term locks that SharePoint utilizes when opening a document, but the locks aren't release when the document is closed, so I cannot use that as a reliable event to detect if the word document is closed. Any ideas?" - join in the discussion.
If you would like to advertise on this SharePoint Newsletter we offer a range of options. Please contact us for more information firstname.lastname@example.org.