Archive for May, 2011
May 13th, 2011 by Tobias Zimmergren
After a bit longer pause than we normally take, it is with great pleasure I now finally announce a new date for the next SSUG (Sweden SharePoint User Group) meeting taking place in Stockholm. Sogeti is kind to be a sponsor for the conference room and food and drinks during this event!
Space is limited, so if you’re planning to attend – register today.
The event will take place in the central parts of Stockholm at hotel Clarion Sign.
TIME Thursday, May 26th @ 18.00 PLACE Clarion Sign Hotel REGISTRATION
Click here to register now!
(You need to Sign in or create an account if you haven’t done so yet. More details about creating a user account here)
Please note that the space is limited, so it’s "first come, first served" that applies to this event.
The meeting agenda will be updated soon with additional topics. Currently the agenda looks like this;
- 18.00: Attendance registration, food and mingle!
- 18:15: Welcome and Introduction, Tobias Zimmergren
- 18:30: Session 1 – Customer Case:
- Modern decision making system at Umeå Municipality, Christoffer von Sabsay
- 19:15: Break
- 19:25: Session 2: TBD
- Details TBD
- 20:10: Break
- 20:15: Session 3
- Details TBD
The SSUG site
SSUG is currently hosted on a SharePoint 2010 platform, which is quite fun since that’s what we all work with on a daily basis. For that purpose, I’ve added some minor products to the site that hopefully will fill its purpose by providing you with additional collaboration functionality.
We’ll be updating the site with more cool stuff shortly!
I’ve launched a peek-preview version of a discussion forum functionality on SSUG that you can try out here: http://www.ssug.se/forum
Any comments, suggestions and feedback can be sent to support [@] tozit.com.
I’ve added a new notification system to the SSUG site as well, notifying people about new meetings and important information. If you experience any problem with the notification plugin, please contact us at support [@] tozit.com.
There’s a few more SSUG meetings planned for the summer which will be announced shortly.
Until then, enjoy!
May 9th, 2011 by Tobias Zimmergren
SharePoint 2010 developing for performance article series:
In this series of articles I will briefly introduce you to some key concepts when it comes to developing for performance in our SharePoint 2010 applications.
Related articles in this article series
Part 1 – SP 2010: Developing for performance Part 1 – Developer Dashboard
Part 2 – SP 2010: Developing for performance Part 2 – SPMonitoredScope
Part 3 – SP 2010: Developing for performance Part 3 – Caching in SharePoint 2010
Part 4 – SP 2010: Developing for performance Part 4 – Logging
Part 5 – SP 2010: Developing for performance Part 5 – Disposal patterns and tools
Part 6 – SP 2010: Developing for performance Part 6 – CSS Sprites
Part 7 – SP 2010: Developing for performance Part 7 – Crunching those scripts
Part 8 – SP 2010: Developing for performance Part 8 – Control that ViewState
Part 7 (this article):
This article is a bit shorter than the others and will only cover the concept of crunching your script files in your projects. The reasoning behind a crunched file is to save on transfer-bytes between the client and server.
The reasoning behind crunching the script files are much that you can save on the client/server transfer and therefore also minimize the HTTP requests – which in turn is one step in the right direction for minimizing the page load time and render time.
Short in short; Do consider the technique if you’ve got large scripts that are taking a bit too long to load.
SharePoint 2010 are using crunched scripts
When you look at those two files in an editor, you’ll quickly see the difference between them:
How to: Crunch your script files
There’s tons of tools on the market for crunching your scripts. Here’s a few online tools for crunching those scripts:
What is the difference when using crunched scripts?
As a quick summary I did a test with an application that are loading a somewhat large script file – first without any crunching and then the same application loading the files after they’ve been minimized with a crunch. These are the results in my SharePoint 2010 application.
|Saves around 25.5% in file size|
A brief summary of the result is that if you’re crunching your script files, you’ll get a slightly smaller footprint when loading the page and making the HTTP requests. The reason for bringing this to your attention is of course that it’s a technique that’s been around for quite some time, but people tend to miss out on it because they’ve not seen the results of it. So, here you go – a visual chart telling you how it differs to use the exact same script, with and without crunching.