SPC 09 1st day coverage by Joel Oleson

http://www.sharepointjoel.com/Lists/Posts/Post.aspx?ID=266

Sales Account Manager - Template for SharePoint 2007

Sales Account Manager

I set up one of the role based templates today. This template can be installed on a single machine as well as multiple machines. I installed it using the second approach. My SQL Server machine is different than my SharePoint server machine. Template comes with detailed setup instructions but believe me installing and configuring it is a cumbersome task. Sales and Marketing people will love this template. I faced some problems during database installation. Setup instructions (Section 2.4 Database Installation, Page 5) tell you to copy MySiteAccountManagerRole.bak file in the following folder:

<Drive name>:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBackup

I got following error when I ran the osql -E -i MySiteAccountManagerRole.sql:

Copying the MySiteAccountManagerRole.bak to the following folder solved my problem:

<Drive name>:Program FilesMicrosoft SQL ServerMSSQL.2MSSQLBackup

Another problem that I faced was that I couldn't find the .odc file mentioned in Section 2.7.3 Document Library Settings - Step 4 and therefore, I had to update the .odc connection file manually.

Here are some screen shots of the template:

Screenshot 1

Screenshot 2

Screenshot 3

Screenshot 4

SharePoint Document Puller v4.0 Download SharePoint Document Puller v4.0 Introduction SharePoint Document Puller is a tool to extract documents from the SharePoint's DB. It works with SharePoint Portal Server 2003 (and WSS 2.0). I have made several changes in this version. There were requests for new features. I have tried to include everything that people requested. The only thing you will find missing is a progress bar or a status bar that displays the download status. History Version 1.0Version 2.0Version 3.0 Details You see a configuration screen when you run the application for the first time. Use this screen to add your database connectivity details. Select server from Server dropdown. Click (Re)Load to populate the Server dropdown if it's empty. Add Username and Password and click Connect. This will populate the Database dropdown. There is a possibility that some one is using different databases for different instances (portals) of SharePoint. Select the database from the Database and click the Save button. This will save the configuration and next time, you start the application, you will be taken directly to the Download Documents screen. You can also add a connection string. Select the second radio button to enable the text box and add the connection string and click the Save button to save the configuration. Shortcut keys Key Functionality Screen Ctrl+1 Download Documents Alt+O Download Documents Ctrl+2 Download Libraries Alt+E Download Libraries Ctrl+3 Configuration Alt+C Configuration Ctrl+4 About Alt+A About Alt+S Select All Items Download Documents Alt+D Copy Directory Structure Download Documents Alt+B Browse Download Documents Alt+V View Documents Download Documents Alt+P Pull Document(s) Download Documents Alt+S Select All Items Download Libraries Alt+D Copy Directory Structure Download Libraries Alt+B Browse Download Libraries Alt+V View Sites Download Libraries Alt+P Pull Document(s) Download Libraries Alt+L (Re)Load Configuration Alt+C Connect Configuration Alt+S Save Configuration Download Documents Click View Documents to populate list box with the documents. Select a destination and click Pull Document(s) to download all documents to your hard disk. Check Copy Directory Structure checkbox if you want to copy the directory structure of each file. Similarly, if you want to download complete libraries, select Download Libraries from the menu bar. List box will show you all the libraries that have documents. Select the libraries you want to download, select a destination and click Pull Document(s). Application searches almost all types of files including .doc, .xls, .mdb, .pdf, .gif, .jpg, etc. Download SharePoint Document Puller v4.0 Published Friday, December 29, 2006 9:41 PM by ssa Comment Notification If you would like to receive an email when updates are made to this post, please register here Subscribe to this post's comments using RSS

MOSS 2007 and Code Access Security

Download Sample Custom Policy File

Have you ever written a web part or a web service? If yes then you must have dealt with a security problem. Writing a web part or web service may not be a big issue but deploying them is certainly a headache. You start getting permission errors as soon as you deploy your code on the server. I recently wrote an article demonstrating the web service creation process and I promised in that article that I would write about Code Access Security (CAS) in another article. There are three ways to assign execution permissions to your code:

1. Increase the trust level for the entire virtual server
2. Create a custom policy file for your assemblies
3. Install your assemblies in the GAC

In the article, we installed our assembly in the GAC but the safest method is to create a custom policy file for the assembly. Following article on MSDN contains complete details on code access security:

Microsoft Windows SharePoint Services and Code Access Security

Written in July 2003, this is one of the most comprehensive articles written on "SharePoint and Code Access Security".

For security reasons, the assembly must be installed in the bin directory of the application instead of GAC but installing it in the bin directory requires you to assign execution permissions to the assembly. One way is to increase the trust level of the entire virtual server. This is easy to implement but this option is least secure as it affects all assemblies used by that virtual server. Second way is to create a custom policy file and this is the recommended approach. This option is most secure but difficult to implement. In this article, we will create a custom policy file for an assembly (web service assembly) written for MOSS 2007.

Creating a Custom Policy File

1. Go to the following location on the server:

LocalDrive:Program FilesCommon FilesMicrosoft Sharedweb server extensions12CONFIG

2. Make a copy of wss_minimaltrust.config and rename it wss_customtrust.config.

3. Open wss_customtrust.config file using any text editor.

4. Under the <SecurityClasses> element, add a reference to the SharePointPermissions class as follows:

<SecurityClass Name="SharePointPermission" Description="Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint.Security, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />

5. Search for the <PermissionSet> tag where the name attribute equals ASP.NET. If you couldn't find that <PermissionSet> tag, locate the one that has SPRestricted in the name attribute.

6. Copy the entire tag and all of its children, and paste a copy of it immediately below the one you copied.

7. Change the name of the PermissionSet element from ASP.NET (or SPRestricted) to CustomTrust.

Before:

<PermissionSetclass="NamedPermissionSet"version="1"Name="SPRestricted">

After:

<PermissionSetclass="NamedPermissionSet"version="1"Name="CustomTrust">

8. Add the following <IPermission> node to the <PermissionSet> element where the name attribute equals CustomTrust:

<IPermission class="SharePointPermission" version="1" ObjectModel="True" />

Therefore, the resulting customized <PermissionSet> will look as follows:

<PermissionSet class="NamedPermissionSet" version="1" Name="CustomTrust"> <IPermission class="AspNetHostingPermission" version="1" Level="Minimal" /> <IPermission class="SecurityPermission" version="1" Flags="Execution" /> <IPermission class="WebPartPermission" version="1" Connections="True" /> <IPermission class="SharePointPermission" version="1" ObjectModel="True" /> </PermissionSet>

9. Once you define the customized element, you must create a code group to specify when the CLR should apply the permission set. (For details, see the original Microsoft article). Locate <CodeGroup> tag where the class attribute equals FirstMatchCodeGroup and copy following CodeGroup immediately below it:

<CodeGroup class="UnionCodeGroup" version="1" PermissionSetName="CustomTrust"> <IMembershipCondition class="UrlMembershipCondition" version="1" Url="$AppDirUrl$/bin/*" /> </CodeGroup>

The membership condition for this new code group is based on URL membership and the URL points to the bin directory. The permissions will be applied to all the assemblies in the bin directory of the current application. You can also use strong name membership but then the permissions will  be applied only to one assembly. For example, if I have written a web service and I wanted to assign permissions to my assembly only, I would use strong name membership. Copy following code immediately below the <CodeGroup> tag where the class attribute equals FirstMatchCodeGroup, if you want to use strong name membership:

<CodeGroup class="UnionCodeGroup" version="1" PermissionSetName="CustomTrust"> <IMembershipCondition class="StrongNameMembershipCondition" version="1" PublicKeyBlob="0x00240000048000009400000006020000002400005253413100040000010001004" Name="UploadService" /> </CodeGroup>

Replace PublicKeyBlob value with your own value and change the name of the assembly in the Name attribute. Name attribute contains the name of the assembly. To retrieve the public key blob for an assembly, use the secutil.exe tool. Please note that publickeyblob is different from publickeytoken. Secutil.exe is located in the following folder:

LocalDrive:Program FilesMicrosoft Visual Studio 8SDKv2.0Bin

To retrieve the public key blob for your assembly, either copy the secutil.exe tool to the folder that contains your assembly else provide exact path to the assembly in the command, and run the tool as follows:

secutil.exe -hex -s UploadService.dll > blob.txt

UploadService.dll is the name of the assembly. This command will create a text file named blob.txt. Open blob.txt and copy the public key and paste it in the publickeyblob attribute.

10. Save and close the file. The policy file is ready to use.

11. Open the web.config file for the virtual server where you have deployed your component and add the following <trustlevel> tag to the SecurityPolicy element:

<trustLevel name="WSS_Custom" policyFile="LocalDrive:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12configwss_customtrust.config" />

Virtual Directories for web applications are located in the following folder:

LocalDrive:InetpubwwwrootwssVirtualDirectories

Suppose I want to deploy my web service in the web application configured at port 17316. The URL of that application would be http://localhost:17316/ and its virtual directory will be:

LocalDrive:InetpubwwwrootwssVirtualDirectories17315

Create a bin folder in this path and copy your assembly to the bin folder. The web.config for this virtual server will be located in the following folder:

LocalDrive:InetpubwwwrootwssVirtualDirectories17315

In the web.config file,  change the <trust> tag so that it refers to the newly defined trust level.

<trust level="WSS_Custom" originUrl="" />

12. Save and close the web.config file.

13. Restart IIS to apply the custom policy to the specified virtual server.

Download Sample Custom Policy File

====

Comments:

	Di niente, di meno, sul mondo dell'informatica.... said: January 25, 2007 8:20 AM
	Di niente, di meno, sul mondo dell'informatica.... said: January 25, 2007 9:49 AM
	deeptyranjan said: It will be very much usefull if it will display all the detail and complete structure of MOSS 2007 object model SharePoint 2007 Object Model It's very urgent  !!! If anybody have any Idea Please let me know. February 8, 2007 3:30 AM
	Ryan said: This was very helpful. After following the steps listed in your post I get the following exception when running my application: "System.IO.FileLoadException: The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)". Any ideas? February 9, 2007 2:05 PM
	ssa said: Hi Ryan, Thanks for reading and liking the article. The error you are getting has nothing to do with the code access security. This error occurs when path to your assembly is longer than 255 characters. Make the path shorter to get rid of this error. There are a couple of good links on google that discuss this issue in detail. Here are a couple of links for your convenience: http://web.archive.org/web/20070514154151/http://kindohm.com/archive/2005/11/10/1167.aspx http://web.archive.org/web/20070514154151/http://blog.surrealization.com/archive/2005/10/25/5355.aspx Hope this helps. Let me know if this does not solve your problem. Good luck Regards, SSA February 10, 2007 2:38 AM
	Abhishek Agrawal said: It is very useful and comprehensive article for deploying/developing ASP.NET application in sharepoint February 13, 2007 5:26 AM
	Pedro Rainho said: I have used your Sample Custom Policy File and i have looked at the microsoft site and i'm still having the same problem. i'm doing this in my sample webpart using (SPSite site = SPControl.GetContextSite(HttpContext.Current))                {                    ServerContext context = ServerContext.GetContext(site);                    SPWeb ferias = site.AllWebs["Ferias"];                    site.AllowUnsafeUpdates = true;                    ferias.AllowUnsafeUpdates = true;                    ferias.Lists.ListsForCurrentUser = true;                    SPList feriasConfiguracao = ferias.Lists["FeriasConfiguracao"];                    SPListItem item = feriasConfiguracao.Items.Add();                    item["Nome"] = "Nome1";                    item["Valor"] = "Valor1";                    item.Update();                } it's simple insert an item in a list, and the error continues to be: Request for the permission of type 'Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint.Security, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' failed. i have simple created a webpart and copy the dll to the bin folder and when i use the web part i receive that error. Any ideas???? February 13, 2007 6:30 AM
	ssa said: Thanks Abhishek February 13, 2007 8:57 AM
	ssa said: Pedro! Did you install the assembly in the GAC? February 13, 2007 8:58 AM
	Anders Rask said: Hi, thanx for the article. A comment though: Wouldnt it be better (read more fine grained) to use the assembly name instead of the blob? Using the blob will give access to all assemblies signed with the same SNK file. Using the name will give you more control on what assemblies are allowed higher privileges -and IMHO thats what CAS is all about ;-) February 13, 2007 10:19 AM
	Anders Rask said: Ahh sorry, i just saw you specified both blob and assembly name :-D February 13, 2007 4:26 PM
	ssa said: Thanks for commenting Anders! :) -SSA February 14, 2007 1:39 AM
	Pedro Rainho said: No, i don't want to install in the gac, i want to copy dll to bin directory, install in the gac is't the same as give full trust in the web.config and i don't want that. If i give full trust my webpart works fine but that is not recomended by MS. i just want to create a simple Custom Policy File that runs the example i posted before. February 19, 2007 9:21 AM
	Suleman said: Hi, Your both articles (MOSS 2007 and Code Access Security & Creating a Custom Web Service for SharePoint ) are really good, the way you described, steps, is simply great. I'm facing a problem, if you have some solution please let me know and thanks in advance. I have deployed a simple web service (that returns "Hello world")  on "Server2" then deployed a webpart on "Server1" and call the service from "Server2" it throws an exception "401 Unauthorized ......" when I use Default or Default Network Credentials. e.g. Web_Ref.PagesList listService = new Web_Ref.PagesList(); listService.Url = siteURL + "/_layouts/KPMGTestService/pageslist.asmx"; listService.Credentials = System.Net.CredentialCache.DefaultNetworkCredentials; listService.PreAuthenticate = true; writer.Write(listService.HelloWorld()); but when I pass userName and password to Network Credentials it works fine. e.g. System.Net.NetworkCredential ntCred = new System.Net.NetworkCredential("UID", "Pwd", "Domain"); listService.Credentials = ntCred; My Problem is, I want to use DefaultCredentials or DefaultNetworkCredentials because in my actual webpart somehow i don't wanna impersonate or pass any UID and Pwd etc because i need to check user rights in webservice. Note: this service works fine if i called it using a Console application. If you have any Idea, please let me know here in this blog or if you can mail me , that will be great, at suleman.ibrahim@hotmail.com Once again Thanks. February 19, 2007 3:56 PM
	ssa said: One thing, the line listService.PreAuthenticate = true; should come before the "credentials" line. Like this: listService.PreAuthenticate = true; listService.Credentials = System.Net.CredentialCache.DefaultNetworkCredentials; Second thing, make sure the login you use for logging in has approp. permissions in SharePoint. February 20, 2007 4:22 AM
	ssa said: Pedro, Which method of authetication are you using in the custom policy file? the URL method OR the blob method?? February 20, 2007 4:36 AM
	Suleman said: Yes, the line listService.PreAuthenticate = true; is come before the "credentials" line. It was just an copy pasting mistake. I have tried both URL and Blob methods in Custom policy file and after updating file I did IISReset but it doesn't work. Login, I'm using for logging has Administrator rights on both servers and has site Collection administrator rights on both portals. One thing more, if I make changes in my service should I create disco and wsdl files again or that is not necessary And what is the imapct of these files cuz I tried my service without these files but result doesn't change wheather I have deployed these files or not. Thanks for your time. February 20, 2007 8:37 AM
	Suleman said: The problem has been resolved actually we should have to use "Kerberos" Authentication Settings instead of "NTLM", if we wanna access some remote server Services etc. I dont wanna go into details but if anyone wanna know about it, differences between "Kerberos" and "NTLM", can read following article. Once again thanks for time and comments. http://web.archive.org/web/20070514154151/http://ablog.apress.com/?p=1127 February 20, 2007 1:48 PM
	Suleman said: But, I still wanna know about my last question. "if I make changes in my service should I create disco and wsdl files again or that is not necessary And what is the imapct of these files cuz I tried my service without these files but result doesn't change wheather I have deployed these files or not." thanks February 20, 2007 1:58 PM
	ssa said: If there are no major changes then there is no need to recreate wsdl and disco files, your web service will work fine. February 22, 2007 4:13 AM
	sireve said: Hi, I have a problem with this sentence: string rol = myweb.RoleDefinitions["admin"].Name; Webpart "x" seems to be causing a problem .Is not the level of permissions. Any Ideas?? And Pedro, I have the same problem in other webpart... Have you got the solution? web.configgg!! :s thanks February 22, 2007 12:24 PM
	ssa said: Sireve, What is the error message that you get? Cant tell you the problem without looking at the error first! Thanks February 23, 2007 1:57 AM
	sireve said: Hi, I said you, sorry I'm not explain, this is the error: Webpart "mywebpart" seems to be causing a problem .Is not the level of permissions. (this is a traslation message, my MOSS is in spanish) thanks February 23, 2007 6:13 AM
	ssa said: hmm.. i guess the web part tries to access an area in SharePoint for which it does not have permissions. wait a minute! What are you creating? a web part, web service or just an application using the object model? ssa February 23, 2007 10:03 AM
	sireve said: This is an error webpart. But the objective is to obtain the group/rol to which the user belongs, in my example user "admin".. how I get it?? thanks ssa February 24, 2007 6:15 AM
	Paul said: Great Article!  I was going around in circles for a couple hours befire finding your post.  I walked thru it and presto, my webpart is now showing.  I was getting the same error that Pedro(above) was getting. (Pedro, in case you haven't resolved your issue.  I believe the key part of the post was to edit the local web.config file and make sure the wss_custom_minimaltrust.config (in my case) has a reference in the security policy section (I'd done most of the edits already, but forgot to tell the local web.config about it ): <securityPolicy> <trustLevel name="WSS_Custom" policyFile="C:Program FilesCommon FilesMicrosoft Sharedweb server extensions12CONFIGwss_custom_minimaltrust.config" /> </securityPolicy> Thanks again, Paul March 25, 2007 8:20 PM
	ssa said: Many Thanks Paul! Regards, SSA March 31, 2007 1:08 AM
	Geo said: This was very helpful. After following the steps listed in your post I get the following exception when running my application: The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047). The only additional part which I am trying to do in my web part is Loading the XML in XMLDocument object using Load method from the local drive. April 24, 2007 11:06 PM

SPS 2003: Deleting a site completely

This is one of the most frequently asked questions. A user when tries to re-create a deleted site gets an error (Site already exists ... !!). This happens when you delete the link but do not delete the actual site. To delete the site physically, do this:

Go to your site > Site Settings > Go to Site Administration > Delete Site (Under "Management and Statistics")

To remove the link, do this:

1. Go to site directory (sites area) > Manage sites

Find your site in the list, open the context menu (click the down arrow (drop down)) and select "Delete Item".

Now, your site is deleted and you can create it again with the same name!

Regards,

-SSA

MOSS 2007 Installation Guide

Installing Microsoft Office SharePoint Server (MOSS) 2007

I have been thinking of writing a small installation document for MOSS 2007 since the beta 2 was released. There is always shortage of time. I have noticed that even though B2TR is available for download but many people are still struggling to install the beta 2 that was released a few months ago.

MOSS 2007 Beta 2 Technical Refresh can be downloaded from the following page:

http://www.microsoft.com/downloads/details.aspx?FamilyID=b07a3387-01cf-4bc3-821a-0bb10e7a59fa&DisplayLang=en

and instructions on how to install this TR are available on SharePoint Team's site:

http://blogs.msdn.com/sharepoint

I would recommend that you install MOSS on a fresh machine. You can install it on a virtual machine. I have tested it with VMware. Hardware and software requirements are listed on the following page:

http://www.microsoft.com/office/preview/beta/sysreq.mspx

You should have at least 2.5 GB space free on your hard disk and at least 1 GB RAM for good performance. On my machine, it took approx. 2.3 GB to install SharePoint, WinFX, SQL Server and i spent approx. 1 and a half hour in installing all these products.

1. Install IIS 6 with ASP.NET enabled.
2. Disable Internet Enhanced Security in IE 6. You can disable it by going to Add/Remove Windows components.
3. Install SQL Server. I have tested MOSS 2007 with both SQL Server 2000 and 2005. If you are installing SQL Server 2000 then make sure you install SQL Server 2000 Service Pack 3 as well.
4. The file downloaded from Microsoft is in ISO format. You can download ISOBuster or any other ISO software to extract setup files from the ISO image. I would recommend WinRAR. There is a problem with other ISO software. You get "Language not supported" error during installation. The solution to "Language not supported" error is to use RAR instead of ISO software. Simply, change the extension of the downloaded file to .RAR and then use WinRAR to extract files from the ISO image.
5. Download WinFX from the following page:

http://www.microsoft.com/downloads/details.aspx?FamilyID=4A96661C-05FD-430C-BB52-2BA86F02F595&displaylang=en

Be careful with the version of WinFX. Versions earlier than this won't work with MOSS 2007 and will give you an error during the MOSS installation. You should only download the following version:

File Name:	winfxsetup.exe
Version:	3.0.3906.22
Date Published:	5/23/2006
Language:	English
Download Size:	2.5 MB

Run winfxsetup.exe downloaded from the location shown above. Winfxsetup.exe will download more files from the internet and it can take around 30-40 minutes for the setup to complete. This includes downloading 46 MB of data from the internet. This will install the components required for the MOSS setup.

6. Run the SharePoint setup file to start the installation. You will be asked to enter the license key.

Enter your license key and click the "Continue" button.

7. Next screen, you will be asked to accept the license agreement.

Click the checkbox and "Continue" button to proceed.

8. In next screen, you will be asked to select "Basic" or "Advanced" setup. Select "Advanced".

9. Select "Complete" installation type in the next screen. The other two options are:

- Web Front End
- Standalone

Click "Install Now".

10.  Installation will start and you will see a blue progress bar.

It will take approx. 10 minutes for the installation to complete. You will see following screen when your installation is complete:

Now your SharePoint installation is complete and it's time to configure the application. Check the checkbox and click the "Close" button. You will see another screen:

Click "Next" to start the configuration process.

11. You might see the following message when you click the "Next" button:

Click "Yes"!

12. In the next screen, you will be asked to select a server farm. Click "No" to create a new server farm and click "Next".

13. Enter your database server and database name in the next screen which looks like this:

Also, enter username and password that will be used to access your database. I used my local Admin account. Click "Next" to proceed.

14. Select security options. You can change the port number and security configuration in this screen:

I selected the default options. Click "Next".

15. You will see the following screen:

Click "Next" to proceed.

It will take sometime for the configuration to complete. You will see a progress bar during the configuration process:

16. Finally, you will see the "Configuration Successful" message. Click "Finish" and you are done!

Here is the first screen that you will see after configuration:

Congratulations! MOSS 2007 has been setup.

ClearType Technology

Well, not related to SharePoint but ClearType is a technology that you must be aware of.

"ClearType is a software technology developed by Microsoft that improves the readability of text on existing LCDs (Liquid Crystal Displays), such as laptop screens, Pocket PC screens and flat panel monitors. With ClearType font technology, the words on your computer screen look almost as sharp and clear as those printed on a piece of paper ... "
Read more on http://www.microsoft.com/typography/WhatIsClearType.mspx
You can use online tuner on Microsoft site to turn on ClearType settings on your machine.

http://www.microsoft.com/typography/ClearType/tuner/Step1.aspx

This is useful especially if you are using a laptop. There is no harm in trying.

If you think you have committed a mistake and you are not happy with the cleartype font, follow these steps to revert to your original settings:

1. Go to Display settings in control panel.
2. Select "Appearance" tab in Display Settings.
3. Click on "Effects."  button.
4. Select "Standard" in the "smooth edges" drop down. Complete drop down name is "Use the following method to smooth edges of screen fonts:"
5. Save your settings. 

-SSA

How to use UserProfileManager in .NET code?

I want alert to be sent to multiple users.

Q: I want alert to be sent to multiple users. "Alert Me" doesn't help!

One way is to use "Alert Me" option. If you are using Outlook, use Tools > Rules and Alerts > New Rule to create a rule that will automatically forward the email to other people.
Update: This post was written long ago when there was no MOSS or WSS 3. Managing alerts for different users was not possible OTB. So, this simple technique provided a way to the users to forward the important news to the other users. for example, users used "Alert Me" to subscribe to the site messages and in the outlook created a rule to forward the received email from SharePoint to the group of other users who had not subscribed to the site news.
SSA

Q: I want alert to be sent to multiple users. "Alert Me" doesn't help!

One way is to use "Alert Me" option. If you are using Outlook, use Tools > Rules and Alerts > New Rule to create a rule that will automatically forward the email to other people.

Update: This post was written long ago when there was no MOSS or WSS 3. Managing alerts for different users was not possible OTB. So, this simple technique provided a way to the users to forward the important news to the other users. for example, users used "Alert Me" to subscribe to the site messages and in the outlook created a rule to forward the received email from SharePoint to the group of other users who had not subscribed to the site news.

spListItem["Modified By"] property gives you the name of the person who last modified the document.
Have a look at the following code. You can get file's URL in EventFileURL if you are using EventHandlerToolkit.
spFile = EventWeb.GetFile( EventFileUrl );
if (spFile.Exists)
{
spListItem = spFile.Item;
}
string strModifiedBy = spListItem["Modified By"].ToString();
and if you want to send an email, here is how you can do it. You can send email in OnDelete(), OnInsert(), OnUpdate(), etc
private void OnDelete()
{
    //Insert code here: capture the name of the person who modified the document
    //Send email
MailMessage msg;
  
SmtpMail.SmtpServer = "smtp.yourserver.com";
msg = new MailMessage();
msg.BodyFormat = MailFormat.Html;
msg.From =  currentWeb.Author.Email; //you can use hard code the sender here
msg.Subject = "File Deleted";
msg.Body = "File has been deleted";
msg.To = currentWeb.Users[strModifiedBy].Email;
SmtpMail.Send(msg);
    
}
-SSA