He’s a collaboration technology specialist with a background in application debugging and development. And, he’s giving us a 60 minute crash course in environment tooling for SharePoint 2010.
Although I’ve already taken 10175A: Microsoft SharePoint 2010, Application Development, I’m still interested in what this guy has to say. After all, every instructor has a different view of the world.
This guy is really into virtual machines. It’s a personal choice, of course, but setting up virtual machines with server images and hosting SharePoint for your developers is a quick and easy way to accelerate innovation.
SharePoint has an easy setup with an automated developer workstation build. All of the apps you need are installed with it. Just make sure your Windows 7 image is current.
Written in Windows PowerShell these scripts will install and configure all the pre-requisites & products to get you up and running with SharePoint development.
Additionally they will download evaluation copies of the products it installs (or use fully licensed product bits you supply), install them either locally or in a user supplied Windows 7 VHD & set that VHD up for dual boot using the Windows 7 VHD native boot feature. It also allows you to configure what products are installed via a configuration file, so you can add or remove products.
All the source is included for your use. If a particular aspect of the setup isn’t right for your requirements then you have the ability to change it. A good example of this might be to configure the SharePoint installation to fit your organizations standard deployment.
Out of the box it will help you install:
- SharePoint Server 2010 + pre-requisites (Standalone)
- Visual Studio 2010 Ultimate Edition
- Silverlight 4 Tools for Visual Studio
- Expression Studio 4 Ultimate
- Open XML SDK
- Visual Studio SDK
- Visual Studio SharePoint Power Tools
- Office 2010 Professional Plus
- SharePoint Designer 2010
- Visio 2010
To get around the agony of code maintenance, take advantage of no-code solutions for SharePoint (like workflows and SharePoint Designer). If you do code, Visual Studio is great at making packaging of solutions simple.
Remember, in SharePoint your developer dashboard is off by default. You can turn it on in the upper right section of the page and it will provide clues about where the bottlenecks are on your page. It also shows you the database queries that are being invoked. Quick note: you are not allowed to mess with the stored procedures that are shipped on SharePoint. Your stuff will be destroyed in a future service pack and you will get no developer support.
In Visio, you can create custom workflows, then add advanced features in SharePoint Designer and Visual Studio. The top 3 things used to develop SharePoint solutions are workflows, web parts, and AJAX.
SharePoint is on .NET 3.5, so no Entity Framework. But, maybe next rev. However, you can use Silverlight 4 in the client. Be sure to download the Silverlight extension you need. Sweet.
SharePoint inherently has weakly typed lists. So, if you write strongly typed code, you’ll have a problem with this. Check out Linq, which is new in this version. Fortunately, the list-throttling capability prevent apps from behaving badly.
InfoPath is a faster, easier and declarative way to do forms. Even though there are great OOB (out of the box) forms already in SharePoint, InfoPath is an interesting way to go.
My laptop died as I was finishing this post, about 10 minutes before the workshop ended. My apologies, David, for ducking out of your great session to find some power!