In SharePoint 2007 it is possible to create site templates based on an existing site. A template can be used to create new site collections and subsites based on that template. When you export a site template, it creates a .stp file for you. Copying this .stp file over to an other evironment gives you the possibility to start using your template over there also.
In SharePoint 2010 site templates are still there. You can create site templates, but these are created as .wsp files instead of .stp files. This gives you the advantage of importing this .wsp into Visual Studio and make solutions based on it.
If you have a SharePoint 2007 Site Template, you cannot export it as a .stp file and import it into SharePoint 2010. The approach for getting your SharePoint 2007 Site Template into SharePoint 2010 is as follows:
Setup a SharePoint 2007 environment
Create a SharePoint 2007 site using the .STP site template
Backup the SharePoint 2007 site
Restore the SharePoint site into a SharePoint 2010 environment
If needed update your site, so that it matches the SharePoint 2010 v4 masterpage and makes use of the new SharePoint 2010 features.
Export your site into a new Site Template
Now you have your SharePoint 2007 Site Template converted into SharePoint 2010, so you can use it to make site collections and subsites based on that template.
For my work I’m using a laptop that has several operating systems installed. Depending on the customer related work, e.g. office work, giving presentations and developing software, I’m booting one of these environments.
My multi-boot installation consists of several environments including:
Windows Server 2008 R2 with SharePoint 2007
Windows Server 2008 R2 with SharePoint 2010
Windows Server 2008 R2 with SharePoint 2007 and Dynamics CRM 4.0.
All the operating systems boot from a virtual hard disk instead of using virtualization by booting an operating system that hosts an other operating system.
I prefer using VHD files and booting from them because of several reason, e.g.:
The whole virtual memory is available for use on the work environment, instead of loosing virtual memory to an operating system that hosts a guest operation system using virtualization
Creating backups of a whole operating system is easily done by just backing up one .vhd file.
Normal hardware and drivers are used instead of emulated hardware and drivers.
By creating a clean installed base environment, you can quickly go back to that state or derive environments based on the base environment.
People often ask me:
How do you install operating systems on a VHD file and setup up a multi-boot environment?
How can you boot from a virtual hard disk?
What did you change to your Windows Server 2008 environment so that it looks like Windows 7?
The installation of Visual Studio 2008 Team Foundation Server (TFS) uses an ini-file located on the installation DVD to determine the TFS related settings, e.g. SQL Server port and TFS Web Service port. When you need custom settings, you need a modified ini-file and reference that file when starting the installation of TFS 2008. It’s not needed to copy the whole installation DVD to an other location.
To install TFS 2008 with custom settings, use the following procedure:
Copy the msiproperty.ini file located on the TFS DVD’s AT folder and copy it to a temporary location.
Modify the msipropery.ini, change the contents to your specific settings.
Start a command prompt, navigate to the TFS DVDs AT folder and run the command:
Heads up – Groove is getting a new name as of the coming release of Office 2010. Please welcome SharePoint Workspace 2010!
The name makeover is in concert with the direction the product is going. SharePoint Workspace will provide easy access to SharePoint content (or content from any server that implements the publicly documented protocols) in an effort to provide a seamless online/offline experience.
SharePoint Workspace 2010 will be easier to deploy and easier to manage, and it supports a new set of scenarios to help Office and SharePoint users be more productive. It will also make it easier for IT folks to implement a consistent information strategy based on SharePoint technology throughout the organization.
There will be changes in the way the product is delivered, as well – e.g. SharePoint Workspace (and OneNote, for that matter) will be added to the Microsoft Office Professional Plus 2010 release. Keep an eye peeled for further announcements from Microsoft on new product plans for Office.
Since last week I am using Windows 7 as my primary operating system, specifically it is Windows 7 RC 64-bit edition build 7100. Yesterday I installed Windows Virtual PC beta so I can continue to use virtual machines. I use virtual machines for different usage scenario’s, mostly for SharePoint and Microsoft .NET development and testing purposes. This post sums up things you need to know when you want to use the new Windows Virtual PC beta.
Windows Virtual PC beta
Windows Virtual PC beta is the successor of Microsoft Virtual PC and comes with new features. The most important feature is Windows XP Mode which allows you to run Windows XP applications in a seamless mode. Applications incompatible with Windows 7 can still be run on Windows 7 by using the Windows XP Virtual Machine. The applications available inside the virtual machine can be run from the Windows 7 start menu, see the screenshot. For more information see Microsoft’s Virtual PC home page.
Program availability and supported guest operation systems
The Windows Virtual PC program is available as an 32-bit and 64-bit version, although only 32-bit guest machines can be used. I don’t understand why Microsoft hasn’t added support for 64-bit guest machines, other products like VMware’s already support this. With Exchange 2010 beta being released as 64-bit-only, SharePoint 2010 announced as 64-bit-only, I see more products following and feel the need of having 64-bit guest machine support.
Virtual PC Integration Components
The current Virtual PC Integration Components version 14.0.7084.0, previously known as Virtual Machine Additions, has support for Windows XP SP3, Windows Vista SP1 and Windows 7 guest machines only. I’m using Windows Server 2008 as my guest PC and have installed the Virtual PC Integration Components, but some features are not working. E.g. drag&drop of files between your host and guest environment is not possible and sharing a local drive. After the installation I had to reactivate my Windows Server 2008 environment.
Virtual Machine Configuration file
The Virtual Machine Configuration file has an extension of .vmcx, previously it had a file extension of .vmc. Both are XML files, but the XML file structure don’t look the same. I have created a new Virtual Machine myself targeting an old Virtual Machine hard disk (.vhd) file. Windows Virtual PC wasn’t able to open the .vhd stored on an external USB hard disk drive. Copying the Virtual Machine hard disk file to my local hard disk drive and attaching it to the Virtual Machine did the trick. It looks to me like a bug, but more testing with other virtual hard disks located on external USB drives is required.
I have not tried to rename an Virtual Machine Configuration file extension from .vmc to .vmcx. If you have tried this, share your knowledge.
Drive and folder sharing
You cannot share a specific folder at the moment. Maybe this is because Windows Server 2008 is not supported by the integration components yet, but I really feel to need to share files between the host and guest environment. As a workaround I use an USB storage device, attach it with guest operating system and transfer files using that storage device.
Since yesterday it’s possible to use ReSharper 4.5 beta in combination with StyleCop by using StyleCop for ReSharper. This post gives you some information on all the three tools that I use to write source code in Visual Studio 2008 for business solutions faster and deliver better maintainable source code.
ReSharper is a productivity tool for Visual Studio. It provides solution-wide error highlighting on the fly, advanced code completion, superior unit testing tools, over 30 advanced code refactorings, multiple handy navigation and search utilities, single-click code formatting and cleanup, automatic code generation and templates, and a lot more productivity features for C#, VB.NET, ASP.NET, XML, and XAML. ReSharper fully integrates with Visual Studio to intelligently and powerfully extend the functionality that is native to Visual Studio. See also the complete ReSharper feature list.
ReShareper 4.5 is currently under development and available as a beta version. The biggest improvement is the performance improvement. The following picture illustrated the performance improvements, according to the ReSharper website:
Microsoft StyleCop analyzes C# source code to enforce a set of style and consistency rules. It can be run from inside of Visual Studio or integrated into an MSBuild project For more information about Microsoft StyleCop see the StyleCop blog at http://blogs.msdn.com/sourceanalysis.
Download StyleCop from the MSDN Code Gallery StyleCop website.
StyleCop for ReSharper
StyleCop combines the power of ReSharper and StyleCop. It is a ReSharper plug-in that allows Microsoft StyleCop to be run as you type, generating real-time syntax highlighting of violations and automatic fixing of StyleCop issues during ReSharper Code CleanUp (silent mode):
StyleCop for ReSharper also contains a collection of Quick-Fixes:
A new CTP version of the SharePoint project and item templates for Visual Studio 2008 are available. Remember that an CTP version is still in development, so Microsoft Support doesn’t officially support them.
The feature name WebPart1 already exists in SharePoint. You need to rename the feature before solution deployment can succeed.
The solution can not be deployed. The feature ’7c05e196-d953-4b90-a910-0f6802648e7d’ uses the directory "MyList instance" in the solution. However, it is currently installed in the farm to the directory "List Definition1 instance". Uninstall the existing feature before you install a new version of the solution.
No SharePoint Site exists at the specified URL.
VSeWSS 1.3 Overview
For those who are new to SharePoint development with VSeWSS, here is Microsoft’s overview.
This is the SharePoint developer tools for Visual Studio 2008. These tools are suitable for use with Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007. It includes project and item templates for common SharePoint artifacts, it includes build, packaging and deployment for SharePoint solutions and it includes the SharePoint Solution Generator which creates a new Visual Studio 2008 project from a SharePoint site. The tools provide item templates for List Definition, List Definition from Content Type, Content Type, Field Control, Web Part, Module, Root File, Template, Event Receiver, and List Instance. It provides project templates for Team Site Definition, Blank Site Definition, List Definition, Web Part and Empty. It works with Visual Basic .NET and C# languages and a comprehensive user guide is included. It does not include the SharePoint Workflow templates as they are built in with Visual Studio 2008. New features in version 1.3 include:
Can be installed on x64 Server OS machines running SharePoint x64. Previously only x86 Server OS could be used
Separate build commands for package, deploy and retract are added as Visual Studio menu items
WSP View improvements for consistency of deleting feature elements, merging features and adding event receivers to features
Command line build, package and retract commands are included enabling continuous integration and build servers. Previously command line build of SharePoint projects was very difficult
Refactoring support for renaming of Web Parts. Previously renaming a web part required changes in several files in the project
Solution Generator can now generate solutions from publishing sites. Previously only regular sites could be generated
Allowing partial trust BIN deployments of web parts
New project item template for SharePoint RootFiles items
Deployment will now optionally remove conflicting existing features on the development server prior to redeployment. Previously any feature name conflicts would result in an error
Ancillary assemblies such as for business logic can now be added to the SharePoint Solution WSP
Hidden features related to Site Definition projects are now shown in WSP View. They are no longer hidden
For advanced users a fast deploy is included to update only the compiled assembly on the SharePoint development installation
Deployment step logging is included
The List Definition from Content Type template now allows for the creation of a List Definition Event Receiver
The User Guide is now installed with the extensions instead of being a separate download