Setting up a SharePoint Development Environment to Support Silverlight Development

[via Andrew Connell]

This morning Andrew Connell held a webcast introducing ASP.NET developers to Silverlight development for SharePoint. The webcast is the third in a series of webcasts to help ASP.NET developers get primed for SharePoint development. After the webcast Andrew was kind enough to post the steps he took in preparing his SharePoint development environment for Silverlight development.

I wonder if it is possible to create a solution file to deploy the Silverlight 2 Beta 1 DLL and make the necessry configuration changes to the web.config file to make the set up of the environment easier? I might have to try that.

Creating WSS Solution Packages for Microsoft Office SharePoint Server 2007

I am assuming you have done custom development for Microsoft Office SharePoint Server 2007. Whether it was a custom web part, workflow, event handler, feature, or module, at some point you probably had to figure out how to deploy it. If you are like me and learn a lot of what you know by doing, then you probably had to fiddle with web.config files and debugging errors with code access security exceptions. This post takes a stroll through a couple of ways to build and bundle a WSP file (a WSS solution package) and deploy it.

Before I begin, you should know that what assumptions I am making about the environment:

A Simple WSP Solution Package

I will update this post with a walk through of creating a simple WSP solution package using the Visual Studio 2005 extensions for Windows SharePoint Services 3.0 in the near future.