#3, Do you mean SharePoint Team Services [v 1 of SP, called STS1], or did you mean the differences in SharePoint Designer apart from Expression Web?
#2, No, FPSE are not needed.
For one, Expression Web can't open an SPS site. SharePoint Designer [SPD], can and was specifically designed to allow rapid, lightweght development of SPS v2 and v3 sites with built in tools to create and manage sites, and web parts. For example, there are now some forty (40) pre-built SPS Applications Templates for Admin, and Sites and SPD allows one to leverage these. Please see, http://www.microsoft.com/technet/windowsserver/sharepoint/wssapps/templates/default.mspx and , http://office.microsoft.com/en-us/sharepointtechnology/default.aspx?ofcresset=1
**Some of my favorite work in SPS is to port SQL Reporting Services [SSRS] as a web part into an SPS V2/V3 site for users - going the other way, once created, we use a native control for SSRS in VS 2005 to create a Reporting Center in Expression Web - enabling non-technical customer site admins to schedule the delivery of reports in SPS sites and baking advanced reports into other apps that are designed using Expression Web. ***Just an example of how the two suites can be sued together and in ways that do not tie up other devs working in VS 2005 [also, using VS Team System] all these people can work together at once - and then finally, the end users have a lot of control and can see business processes in a very easy to use, yet powerful set of non-linear reporting products in both apps and collaboration spaces.
And a final P.S., on this one, the presence token in SPS, and as a control available for any VS project is waayyy cool and useful - it shows who is where, and what their availability is and when used with either Live Messenger, or Office Communicator, it can be really helpful.
This post was edited by lketchum on Thursday, April 12, 2007 at 04:49.
|