This definitely makes you think ...
On a similar note - We are Gen Y ...
I finally got around to installing the SharePoint infrastructure update on MOSS dev machine. Everything went very smoothly ... I had SP1 already installed (yes that's a prerequisite) so just three steps for me
What's included in the Infrastructure update for Microsoft Office SharePoint Server:
For detailed information take a look at:
Be aware though that there are also some things that you have to watch out for when deploying these updates - I think these are the main problem areas:
One of the reasons why Dynamics AX 2009 might be of interesting to SharePoint Developers is the Enterprise Portal functionality. Enterprise Portal in Microsoft Dynamics AX 2009 is built on ASP.net/AJAX, it uses Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007 and provides full power and flexibility to developers to build real , modern , interactive and responsive web applications for intranet, extranet and internet scenarios.
Resources [All links require Partnersource login]:
The Podcasting Kit for SharePoint is definitely one of the coolest projects on Codeplex using SharePoint - http://www.codeplex.com/pks
So what does Podcasting Kit for SharePoint (PKS) do:
The source code for PKS is free for SharePoint customers under the Microsoft Public License.
I started playing around with PKS in june and after struggling to work myself through the 35 pages of installation documentation - I noticed that the June release was not compatible with Silverlight 2 Beta 2 (Bummer .... :-( ). Another important notice - PKS has been built to work on top of SharePoint Server 2007 - it does not work with WSS 3.0.
So what's new/fixed in the july release (still no support for Silverlight 2Beta 2 - expected for august release)
Can't wait to get my hands on the august release ....
Adoption is definitely the toughest part about SharePoint projects ... if you want your project to be a success a "build and users will come"-strategy is not a good approach. The next tips are a compilation of an email discussion with some other MVPs about user adoption.
Don't take the list above for an exhaustive list - you will probably come up with some other thoughts. Don't hesitate and leave a comment.
Other resources:
I just finished installing Visual Studio 2008 SP1 (after cleaning up for extra disk space on C-drive).
Interesting new functionality/enhancements (something unusual for a service pack):
Links:
International SharePoint Professionals Association (“ISPA”) was announced mid july - see the press release as well as the announcement of Bob Fox for more details. I'm proud to work together with them as the ISPA Regional Evangelist for Belgium. I also registered BIWUG on their site. So if you have any questions - do not hesitate to contact me (but first check out the FAQ)
The International SharePoint Professionals Association (“ISPA”) is the first independent, community-run, not-for-profit organization designed specifically for SharePoint Professionals. ISPA is a professional association dedicated to the promotion and global adoption of Microsoft SharePoint Products and Technologies. The Association provides support and guidance to the community by establishing connections between SharePoint professionals and groups, resources, education and information.
Services which currently are available through the ISPA web site:
Definitely check out the site - http://www.sharepointpros.org
SQL Server 2008 is now available on MSDN and TechNet, see the announcement here.
Resources:
In Getting started with SharePoint and Silverlight - Part II I talked about the Silverlight Blueprints for SharePoint. With the recent release of Silverlight 2 Beta2 I was wondering how easy it would be to get the Silverlight BluePrint to work with it. Unfortunately, things did not work quite easily - for an overview of changes in beta2 take a look at http://blogs.msdn.com/silverlight_sdk/archive/2008/06/04/breaking-changes-for-silverlight-2-beta-2-corrections-and-additions.aspx
For the HelloSilverlight sample the change is pretty simple:
If you look at the Silverlight Mediaviewer webpart you will notice that this one is a little more complicated to update to Silverlight 2.0 beta.
The main problem with SharePoint integration and Silverlight 2.0 beta 2 is the change to HttpWebRequest class - delegates are called on a new non-UI background thread. This means that you will need to use System.Threading.SynchronizationContext to update the UI on the background thread. It took me a while to figure this one out ... after I finally found the solution I found this great posting about the necessary changes (would have spared me a couple of hours) - Porting the Silverlight Blueprints for SharePoint to Silverlight 2 Beta2.
Here are another couple of interesting tools that you can use to extend SharePoint - happy SharePointing
OBAs' (Office Business Applications) are an interesting concept but unfortunately I don't see a lot of traction in Belgium. Here's a short recap of what OBA's are about:
Office Business Applications are an emerging class of applications that helps business unlock the value of their line-of-business (LOB) systems and turn document-based processes into real applications.
Agnes has some interesting postings about the OBA Composition Reference Toolkit
Related resources:
My colleague Maarten created some very nice MSDN chopsticks (webcasts) about the ASP.NET MVC framework - check them out
http://blog.maartenballiauw.be/post/2008/07/23/MSDN-Chopsticks-on-ASPNET-MVC-(screencasts).aspx
This is an excerpt from SharePoint 2007: The definitive Guide,
Note that the SharePoint object model contains a number of managed objects – most importantly in this instance are SPWeb and SPSite - which use unmanaged code and memory to do the heavy lifting. If you create one of these objects yourself with the constructor method, you should make sure that you add in the necessary code to explicitly dispose of the object when you have finished using it. You can do this by explicitly calling the Dispose method or through the use of the C# using construct (as shown in the previous code listing). Failure to dispose of the object can result in unusual behavior such as high memory usage, frequent recycling of the SharePoint application pool, etc … It is recommended to use the Dispose method instead of simply calling the object’s Close method.
For more info take a look at these must reads for every SharePoint developer:
Ilse Van Crieckinge and I did a session about how SharePoint can be a substitute for Exchange public folders.
Related links:
Some interesting background info on why IT projects fail - and trust me, SharePoint projects are no worse then other IT projects - but there are some complications as you will notice once you get through the next blog series:
Check out the presentation on Slideshare - What is Enterprise 2.0 - Meet Charlie
Related posts:
The SharePoint product team blog has some excellent postings about SharePoint has been extended. Excellent reading material:
Definitely an interesting error message:
My host, being satan incarnate, messed up the database. Im in Orlando still, so i shall be diligent and fix it when I return.
I did a practice session about integrating Microsoft Office SharePoint Server 2007, Microsoft Dynamics AX 2009 and the Business Intelligence capabilities of Microsoft SQL Server a couple of weeks ago.
I'm mostly a SharePoint guy but I was pretty impressed with the capabilities of Microsoft Dynamics AX 2009. Since Dynamics AX 2009 finally RTM'ed (Download on partnersource - https://mbs.microsoft.com/partnersource/support/selfsupport/productreleases/DynamicsAX2009release.htm
For more info check out these links:
The coolest thing for SharePoint developers is probably the ASP.NET based Enterprise Portal - everything is basically an ASP.NET web part which makes it a lot easier to develop a light-weight web access for your Dynamics AX back-end.
Something which still strikes me as odd though is the fact that almost all of the documentation is partner-access only - so you will need a Partnersource logon to take a look at the most interesting bits of info. I truly believe that the key to the success of a platform is the community which drives it ... and it seems as if the Dynamics AX platform solely relies on its partner platform. Too bad ... [This is my personal opinion and not necessarily this of my employer]
Interactive Media Manager is a Digital Asset Management (DAM) system built on top of SharePoint Server 2007. Some interesting features:
For a great demo of the capabilities - check out IMM@NAB 2008 (Video)
Related links:
Enterprise 2.0 is probably one of these buzz words you have heard a lot lately. It is also a term which is surrounded by confusion. The simplest definition of Enterprise 2.0 would probably be "...the application of Web 2.0 technologies in the enterprise." . This is similar to the definition which has been put forward by AIIM in one of their studies recently.
Enterprise 2.0: A system of web-based technologies that provide rapid and agile collaboration, sharing, emergence and integration capabilities in the extended enterprise.
Another cool one - probably my favourite:
Enterprise 2.0 is about empowering your end users to connect and collaborate.
Now let's talk about the key thoughts in the presentation. The red line in the presentation is the link between organizational culture and Enterprise 2.0. But what is not clear is whether your organizaiton needs a "culture of collaboration" to successfully use wikis and other Enterprise 2.0 tools or that these tools can enable your organization to embrace a "culture of collaboration".
This might seem like the chicken-and-the-egg problem ...
I think that you will first need to create a mindset within your company which is ready to embrace collaboration and knowledge sharing before you can start thinking about Enterprise 2.0 - a view which is confirmed by this guy - Enterprise 2.0 - Culture required? But on the other hand for those people in your company who get it, you want to provide the necessary tools - so you might want to take a look at a platform which might already be present in your company - guess which one? SharePoint offcourse ... LOL.
Related links:
Silverlight 2 beta 2 has been released - so time to install the required tools fo finish my series about Getting started with SharePoint and Silverlight.
First uninstall Expression Blend 2.5 March preview, Silverlight 2 Beta 1 and Microsoft Silverlight Tools Beta 1 for Visual Studio 2008. Next install all of the new components:
Interesting about Silverlight 2 Beta2 is the fact that it has a go-live license that allows you to start using and deploying Silverlight 2 for commercial applications.
Interesting links:
I noticed this really annoying popup today on my blog -
"The evaluation period for Silverlight 2 Beta 1 has ended. You can visit the Silverlight web site to download the latest version. Do you want to go there now?"

So I uninstalled Silverlight and saw this "Install Microsoft Silverlight to view My XBox Gamercard". But when I clicked this - it redirected me again to the Silverlight Beta 1 download. Therefore I remove the XBox Gamercard silverlight app untill it has been upgraded. Too bad, I hoped that upgrades would be seamless from an end-users perspective.
Interesting interview with Quentin Clark who led the WinFS project from 2002 to 2006 ... This is something which you should read, it also puts the evolution of the Entity Framework, Filestreams in SQL Server 2008 (Take a look at Managing unstructured data in SQL Server 2008 ) , LINQ and the Microsoft Sync Framework into perspective, ...
Joel Oleson compiled a Top 100 of SharePoint blogs using Technorati ranks, Google ranking, etc ... I made it on number 12 - thanks a lot ....
In the first part I talked about how to get your first Silverlight app up and running. Now let's see how to get this into SharePoint. Patrick has created an excellent checklist about How to configure your SharePoint extended IIS Web app for working with Silverlight 2 applications.
For step 4 - if you need to add System.Web.Silverlight.dll to the GAC - you will find this file underneath C:\Program Files\Microsoft SDKs\Silverlight\v2.0\Libraries\Server (default installation folder for the Silverlight SDK).
For step 6 - I used the 3.5 Config feature from Codeplex - http://www.codeplex.com/features which works pretty good.

To test everything out - let's start of with one of the samples in the Silverlight BluePrint for SharePoint - which contains six sample applications:
Let's start off with the Silverlight "Hello world" example. Steps that I took:
Another interesting webpart which is packaged together with the "Hello world" sample is the SilverlightPart which is basically a webpart which can host a Silverlight application (1.0 or 2.0). You can select the Silverlight app to host by selecting it using the webpart properties.

When I started fiddling around with these Silverlight apps - I regularly noticed this error message "Internet explorer has encountered a problem with an add-on and needs to close. The following add-on was running when this problem occurred
npctrl.dll" - luckily I found this post - IE crashing with Silverlight 2 - Part II - It was not fixed ! But it's now! and this did the trick - apparently Silverlight tried to go online to get an update but my VPC had no networkconnection.
That's it for today, in a next posting I will try to explain what the code in the HelloSilverlight webpart does.
Today I needed to create a SharePoint feature which would add a link on the Site Settings page within the Site Administration section - in SharePoint this is done by defining a CustomAction feature. A colleague of mine pointed me to two invaluable resources if you need to build a CustomAction feature:
I uploaded the slidedecks and democode for the BIWUG session of last week - have fun:
This is the most interesting part of the press release - Microsoft Expands list of formats supported in Office
With the release of Microsoft Office 2007 Service Pack 2 (SP2) scheduled for the first half of 2009, the list will grow to include support for XML Paper Specification (XPS), Portable Document Format (PDF) 1.5, PDF/A and Open Document Format (ODF) v1.1.
When using SP2, customers will be able to open, edit and save documents using ODF and save documents into the XPS and PDF fixed formats from directly within the application without having to install any other code. It will also allow customers to set ODF as the default file format for Office 2007. To also provide ODF support for users of earlier versions of Microsoft Office (Office XP and Office 2003), Microsoft will continue to collaborate with the open source community in the ongoing development of the Open XML-ODF translator project on SourceForge.net.
As I stated before (Microsoft support ODF through Sourceforge project - ODF addin for Word 2007) - this is quite important here in Belgium where the Belgian government decided to standardize on ODF starting on September 2008 (text in Dutch).
I recently took a look at the Document Information Panel functionality in Word 2007 which allows you to provide a custom form to enable metadata editing for documents stored in SharePoint and encountered something unexpected.
You can actually customize this Document Information Panel by plugging in your own Document Information Panel (DIP). A Document Information Panel is actually nothing more then an InfoPath form - see InfoPath 2007: Customizing the default Document Information Panel.
SharePoint autobuilds a DIP for your document metadata and seems to work without an installation of InfoPath on the client. But what if you want to build your custom Document Information Panel using InfoPath? This where things get ugly - like this guy noticed as well - All about the Document Information Panel and InfoPath issues. Whenever you are going to use a custom Document Information Panel - you will need to have InfoPath installed on all the clients.
This is actually explained on this page - Microsoft Office Professional Plus 2007 Suite Comparison - all the way to the bottom - there is a footnote which contains some very important information.
| Features and Benefits | Office Standard 2007 | Office Professional Plus 2007 | Office Enterprise 2007 |
| Complete, collect, and organize Office InfoPath e-mail forms in Office Outlook 2007.2 | |||
| Host embedded, fully customizable InfoPath forms in Office Word 2007, Office Excel 2007, and Office PowerPoint 2007.2 | |||
| Complete forms in Programmable Task Panes. 2 | |||
| Complete custom fields and execute custom business logic in Document Information Panel forms.2 |
2 These capabilities require that Office InfoPath 2007 be installed on the client computer. Office Professional Plus 2007 and Office Enterprise 2007 include Office InfoPath 2007. Organizations that acquire other suites can purchase and install Office InfoPath 2007 separately.
As I stated in the title - the devil is in the details ... sometimes even in a footnote.
This is the first part of a series of postings about how you can use Silverlight and Office SharePoint Server 2007 together. I'm new at Silverlight development - so I will take it one step at a time.
Things you will need to install to get you started right now:
First I took a look at one of the videos on Silverlight.net - the one with the smiley - Getting started with Silverlight and followed the instructions to create my first Silverlight project. There are some differences with Silverlight 1.0 though. One of the things you will notice immediately is the fact that with 2.0 - Silverlight applications are basically compiled into a .xap file (For more details: take a look at Silverlight: Anatomy of an .XAP file).
Now, let's get this deployed on a VPC which has both SharePoint Server 2007 and Silverlight installed. To make things a little bit easier let's test this first in a separate web site which hasn't been extended by SharePoint.
It is important that you first add both the XAML and XAP MIME extensions to IIS (See Configuring a web server to host Silverlight Content as well as Configuring MIME Types (IIS 6.0) for more details ...) otherwise your Silverlight app won't work. (Do an iisreset after you added the MIME extensions)
So open up the IIS MMC, create a new website and map it to a folder on your filesystem. Next copy Testpage.html as well as the xap file into this folder. Et voila, your first Silverlight application is deployed ....
In a next posting I will take a look at how to get this same Silverlight app loaded within SharePoint Server 2007.
We will organize another BIWUG meeting on May 22th:
18:30-19:00 Registration and welcome
19:00-19:45 Biztalk integration with SharePoint and InfoPath forms using the Biztalk 2006 R2 SharePoint adapter
In this session you will be introduced to Biztalk 2006 R2 as an Enterprise Application Integration engine and get an overview of the integration possibilities with SharePoint by using infopath forms based on XSD schemas and the Biztalk SharePoint adapter. A demonstration will be given how Biztalk can run orchestrations that are bound to receive and sendports which are connected to SharePoint document libraries.
Speaker: Kurt Claeys, http://www.devitect.net
19:45-20:15 IBM Team Collaboration Software – Lotus software
Introduction to Lotus products. Positioning of IBMs offering for communication and collaboration.
Speakers: Koen Renders en Tom Van Aken
20:15-20:30 Break
20:30-21:15 Windows Workflow Foundation – deep dive
Windows Workflow Foundation is one of the three pilar technologies of .NET 3.0. As it is designed to model business processes, it is probably the most abstract .NET 3.0 technology. In this technical presentation we'll deep dive in Worflow Foundation and explore some of the new terms it introduces. Terms essential to fully grasp what your workflow is doing and what it is not.
Speaker: Tom Nys, http://tomblog.insomniacminds.com/
Event location: Real Software, Prins Boudewijnlaan 26, B-2550 Kontich http://www.realsoftwaregroup.com/Commercial/Default.aspx?id=490
Win Free versions of Windows Vista Ultimate
We will give away 2 Windows Vista Ultimate to one of the attendees of this BIWUG event.
Lawrence wrote a great posting about Knowledge and Talent in a People-Ready Business on the SharePoint Team blog. Empowering people in your organization is a key part to the success of your company and its ability to innovate... Some people however see this different - check out Knowledge is power! So why share your knowledge?
Hype, fad or something else ... still not sure yet - there probably are some uses to it but since I'm not convinced I decided to try it out myself. If you want to follow me - check out http://twitter.com/jopxtwits. If you new to Twitter, you might want to look at the Newbie's guide to Twitter and if you are not convinced you might want to take a look at 12 reasons to start Twittering ... Twittering seems to enable you to disseminate those little thoughts/feelings (from brilliant to just plain meaningless) which seem to pop up in your head (but are gone a minute later). So a lot is just that - plain meaningless chatter but sometimes there's a little gem in there ...
Some interesting tools to check out as well:
Not sure if this correct but to use a new interesting word that I recently heard about ... stop bogarting your knowledge/thoughts/whatever ... and share it on Twitter :-)...
For people performing a migration from MCMS 2002 to MOSS 2007, this whitepaper is a must read - Assessing and analyzing your MCMS2002 application for migration.
One thing you will notice in this white paper is that there is no straightforward workaround for people who used the MCMS2002 XML placeholder controls.
I checked with Andrew and he gave me this feedback:
The problem is that the XML Placeholder controls don’t map to anything in MOSS… XML placeholder controls were used as the base storage vehicle for custom placeholder controls in MOSS. Since they were custom, there is nothing to equate them to in MOSS.
The content will migrate just fine, but as a multiple lines of text field. You’ll likely want to create custom field controls for these, unless you want your authors to edit raw XML and display raw XML.
Some other tips you might want to think about when migrating from MCMS 2002:
A challenge that a lot of companies is how to design a SharePoint architecture where internal people as well as external people external can collaborate around documents.
Most common constraints:
When you encounter something like this, there are a number of decisions to be made:
Discussion about topology
The most common options are described within this article - Design Extranet topology - http://technet.microsoft.com/en-us/library/cc263513.aspx .
1. Perimeter proxy/edge firewall topology - intranet.
2. Back to back perimeter topology.
3. Back to back perimeter topology with content publishing (Not relevant in current scenario)
4. Back to back perimeter topology optimized for hosting static content (Not relevant in current scenario) 5. Split back to back topology
If you have a pure collaboration scenario (no publishing) Only options 1,2 and 5 are relevant.
Perimeter proxy/edge firewall topology
This is the most simple solution where a reverse proxy server sits on the border between the Internet and the corporate network to intercept and then forward requests to the appropriate Web server located in the corporate network. The disadvantage is that there is only boundary between the internet and your corporate network
Back to back perimeter topology
Separate farm setup in the perimeter/DMZ. You can create a separate Active Directory in your perimeter to manage external accounts.
Split back to back topology
Database servers reside within the corporate network - other servers within the perimeter.
Another interesting post which you might want to take a look at is Plan security hardening for extranet environments - http://technet2.microsoft.com/windowsserver/WSS/en/library/5b000a77-471a-400d-b446-aa68a9526f3e1033.mspx?mfr=true and if you are not that familiar with ISA firewalls - these are definitely must reads:
In a next posting I will talk about authentication and management of external accounts.
I just started playing around with the CTP3 of Microsoft Dynamics AX 2009 - you can download the VPC from Partnersource (logon required). First thing I did - change the keyboard layout for the logon screen of Windows Server 2003 - :-) ...
Expect some updates for the following blog post in the coming weeks:
Nine of the Belgian Microsoft user groups will combine their efforts to organize the second edition of www.Communityday.be
This year we have some great sessions in store for you on Thursday, the 26th of June at Semcom in Keerbergen.
BIWUG will do a joint session with Pro-Exchange about MOSS vs Exchange Public Folders (Bring it on Ilse :) ) ... as well as a session about Building Rich Internet Applications on top of SharePoint. Hope to see you all there and don't forget to register since space is limited.
Here's the summary of the two sessions: