GotDotNet.com has a SharePoint Products and Technologies page
Recommended SharePoint Downloads
Whitepapers
WSS Site Definition Templates
Resources
Tools
Service Packs
Integrating Project 2003 with Windows SharePoint Services
This webcast presents an overview of Windows SharePoint Services (WSS) and how it integrates with Project Server. It then proceeds to describe the benefits WSS adds to a Project Server implementation and discusses WSS deployment and its scalability option.
And check my SharePoint Products and Technologies blog category out as well!
Found an interesting post on Chris Sells' blog that talks about how to grant FullTrust to mapped network drives.
The following is taken from his great post:
When attempting to load a VS.NET project from a Network Drive (like Z:) you may receive the following error
The project location is not trused.
Running the application may result in security exceptions when it attemps to perform actions which require full trust
What's happening is that VS is detecting that the project on the network drive is getting Intranet permissions according to the good and true workings of .NET Code Access Security (CAS). However, since I'm just trying to pretend that Z is on my PC (and, in fact, it is), I want it to have FullTrust permissions.
To accomplish this, you need to add a new Code Group with an URL membership permission specifying the folder (in URL form) to which you'd like to grant full trust. You can do with the .NET Framework Configuration tool or you can do it from the command line like so:
c:\>caspol -q -machine -addgroup 1 -url file:///z:/* FullTrust -name "Z Drive"
Once this new code group is in place, any new .NET processes you start will give any assemblies on the Z drive full trust.
Since awarding new permissions, full trust or not, to any chunk of code is something that can cause a security hole, be careful.
Thanks Chris for the tip! This will prove to be invaluable as I use Virtual PC, and reference projects on my host PC from within a VPC session through folder mappings.
I've been asked a number of times about installation order of SharePoint Portal Server 2003 and Exchange 2003 on a domain controller. “Why on earth would a person want to do that?”, you ask? Well, both SharePoint and Exchange development introduce some rather tricky development scenarios, and rather than butt heads with your local network admin, folks lean to developing within a “sandboxed” environment, like that provided by a virtual machine running in either VMware or Virtual PC , where they could potentially be “mobile“ and not be joined at the hip to servers or their friendly neighborhood admin.
So, with that being said, in order to have both products coexist on the single machine, Exchange must be installed first, then SharePoint Portal Server. The full installation order I typically use is as follows (for simplicity, let's say we're creating a dev environment in a Virtual PC virtual machine):
Done. These are some basic steps that I follow (with a few more additions not listed). Some folks may have different approaches, but this has yielded a 100% success rate for any initial install I've done on my local development machine VMs
Ran across this informative Microsoft Knowledge Base article that gives step-by-step instructions on how to rename a computer that's already running SharePoint Portal Server 2003. I can't count how many times I've been asked that question (even recently). I thought about writing a post that describes the steps, however, this article was right on time
Article URL: http://support.microsoft.com/default.aspx?scid=kb;en-us;830970
This sample code demonstrates how to programmatically add users in SharePoint Portal Server 2003 or Windows SharePoint Services v2.0 (exception handling omitted)
In C#
using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
public class MyUserAdminClass
{
public void AddUser(string username, string emailAddress, string fullName, string comments)
{
// get a reference to the current SharePoint site
SPWeb PortalWeb = SPControl.GetContextWeb(Context);
// get a reference to the role that you want to add the user to
SPRole UserRole = PortalWeb.Roles(“Administrator“);
// add the user to the role
UserRole.AddUser(username, emailAddress, fullName, comments);
}
}
In VB.NET
Imports Microsoft.SharePoint
Imports Microsoft.SharePoint.WebControls
Public Class MyUserAdminClass
Public Sub AddUser(ByVal username As String, _
ByVal emailAddress As String, _
ByVal fullName As String, ByVal comments As String)
' get a reference to the current SharePoint site
Dim PortalWeb As SPWeb = SPControl.GetContextWeb(Context)
' get a reference to the role that you want to add the user to
Dim UserRole As SPRole = PortalWeb.Roles(“Administrator“)
' add the user to the role
UserRole.AddUser(username, emailAddress, fullName, comments)
End Sub
End Class
Notes: