RE: [OzMOSS] Developer help!

2008-02-01 Thread Paul Culmsee
Much more suitably qualified people on this list that me to answer this, as
app-dev isn’t my main focus, but event handlers are a pretty good place to
start with SharePoint dev IMO as they tend to be relatively simple codewise
(and therefore within my reach :-).

 

I use Brian Wilsons’s feature/solution to take care of the deployment of the
event handler. 

 

http://blogs.msdn.com/brianwilson/archive/2007/03/18/event-handlers-part-3-r
egister-event-handlers-plus-free-site-settings-manage-event-handlers-add-on.
aspx

 

So in visual studio you will have to create a new class, add a reference to
Microsoft.sharepoint.dll, paste in that code and build it. Have you gotten
that far?

 

In fact Brian’s article was all I needed to get started. You may find it
useful in your endeavors. I recommend reading the other articles in his
series

 

http://blogs.msdn.com/brianwilson/archive/2007/03/18/event-handlers-part-2-b
uilding-and-deploying-event-handlers-including-event-handler-starter-solutio
n-kit.aspx

 

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
MacDonald, Mike
Sent: Friday, 1 February 2008 11:24 PM
To: listserver@ozMOSS.com
Cc: [EMAIL PROTECTED]
Subject: [OzMOSS] Developer help!

 

Hi All:  

 

I am 6 months new to sharepoint administration and we are using a WSS 3.0
environment.  My problem is I want to create an event handler that will pull
certain fields (other than the body, subject and email address) of an email
and then create a new list item with the selected fields.  For Example:
Create an outlook form with fields like First Name, Last Name, Problem
description, Contact method (choice field), ID, hardware used (choice field)
Etc… This is being used for a remote administration we are providing.  

 

Anyways, I have no experience developing in visual studio, but do have
access to it. After a few weeks of research I have found the code for the
event handler that I need to modify and found basic instructions to create
an event handler, but I have been unsuccessful putting them together and
building the solution in Visual Studio.

 

The code that is responsible for pulling the Body, subject and email out of
the box in sharepoint is:

 

namespace TaskHandler

{

public class SimpleHandler:SPEmailEventReceiver

{

public override void EmailReceived(SPList list,
Microsoft.SharePoint.Utilities.SPEmailMessage emailMessage, string
receiverData)

{

SPListItem item = list.Items.Add();

item["Title"] = emailMessage.Headers["Subject"];

item["DueDate"] =
System.DateTime.Parse(emailMessage.Headers["Date"]).AddDays(21);

item["Description"] = emailMessage.HtmlBody;

item.Update();

}

}

}

 

However for me to edit it and make it work/deploy it as an event handler is
not working to well.

 

Anyways, ANY HELP that any of you developers can provide me with would be
MUCH APPRECIATED!!!

 

I am a quick learner!

 

Thank you,

 

Mike 

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Sezai KOMUR
Sent: Thursday, January 31, 2008 10:13 PM
To: listserver@ozMOSS.com
Subject: [OzMOSS] RE: Custom Managed Properties

 

Re-run the search crawl.

 

If you have just mapped the Managed Property to a Crawl Property then you
need to re-run the crawl again in order for the Managed Property to
correctly map through to the Crawl Property.

 

Ie. 

1.   Crawl once to detect the Crawl Property

2.   Create a Managed Property and Map it to the Crawl Property

3.   Run the crawl again after mapping the Managed Property

 

Sezai Kömür
Senior Developer  - BEng, BSc - Microsoft Certified Technology Specialist  -
HYPERLINK "http://www.moss2007.com.au/"http://www.moss2007.com.au/

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Roger Noble
Sent: Friday, 1 February 2008 1:12 PM
To: listserver@ozMOSS.com
Subject: [OzMOSS] Custom Managed Properties

 

Hi All,

[Sorry this is a bit long winded]

I have a custom Managed Property that is mapped to a Crawled Property.

The Crawled Property is a metadata element in an aspx page, and has been
crawled and discovered by the query engine. I know that the property has
been found because on the crawled property page it lists some sample
documents that use the property.

The problem I am having is that the Managed Property is returning blank when
I perform a search, and when I look at the Managed Property properties it
has “Number of items found with this property: 0” in the Content using this
property section.

 

Example metadata element: 

 

Thanks for your help

Roger

 

[For those who are interested in hearing about my last problem. The client
still wanted the documents to be crawled instantly when a page was created –
so I’m starting an incremental crawl every time. So far this works fine, but
has not been tested under load.]


IMPORTANT NOTICE: This e-mail message is intended to be received only by
persons entitled to rece

RE: [OzMOSS] Developer help!

2008-02-01 Thread Sezai KOMUR
Although this doesn't answer your event handler question, it is developer 
related.

I recently had a look at a great new SharePoint developer tool on CodePlex 
called STSDEV http://www.codeplex.com/stsdev.

It's excellent and generates SharePoint code for you, it will also save a lot 
of development time. I advise all SharePoint developers to watch the video's on 
this page
http://www.codeplex.com/stsdev/Release/ProjectReleases.aspx?ReleaseId=10119

Start with -

 1.  STSDEV_01_Introduction.wmv: A basic introduction to the STSDEV utility 
which covers setup and usage including an exploration of the basic Visual 
Studio project structure that is generated for all STSDEV-generated solutions. 
You should view this screencast before any of the others.



From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Paul Culmsee [EMAIL 
PROTECTED]
Sent: Saturday, 2 February 2008 8:14 AM
To: listserver@ozMOSS.com
Subject: RE: [OzMOSS] Developer help!

Much more suitably qualified people on this list that me to answer this, as 
app-dev isn’t my main focus, but event handlers are a pretty good place to 
start with SharePoint dev IMO as they tend to be relatively simple codewise 
(and therefore within my reach :-).

I use Brian Wilsons’s feature/solution to take care of the deployment of the 
event handler.

http://blogs.msdn.com/brianwilson/archive/2007/03/18/event-handlers-part-3-register-event-handlers-plus-free-site-settings-manage-event-handlers-add-on.aspx

So in visual studio you will have to create a new class, add a reference to 
Microsoft.sharepoint.dll, paste in that code and build it. Have you gotten that 
far?

In fact Brian’s article was all I needed to get started. You may find it useful 
in your endeavors. I recommend reading the other articles in his series

http://blogs.msdn.com/brianwilson/archive/2007/03/18/event-handlers-part-2-building-and-deploying-event-handlers-including-event-handler-starter-solution-kit.aspx


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MacDonald, Mike
Sent: Friday, 1 February 2008 11:24 PM
To: listserver@ozMOSS.com
Cc: [EMAIL PROTECTED]
Subject: [OzMOSS] Developer help!

Hi All:

I am 6 months new to sharepoint administration and we are using a WSS 3.0 
environment.  My problem is I want to create an event handler that will pull 
certain fields (other than the body, subject and email address) of an email and 
then create a new list item with the selected fields.  For Example:  Create an 
outlook form with fields like First Name, Last Name, Problem description, 
Contact method (choice field), ID, hardware used (choice field) Etc… This is 
being used for a remote administration we are providing.

Anyways, I have no experience developing in visual studio, but do have access 
to it. After a few weeks of research I have found the code for the event 
handler that I need to modify and found basic instructions to create an event 
handler, but I have been unsuccessful putting them together and building the 
solution in Visual Studio.

The code that is responsible for pulling the Body, subject and email out of the 
box in sharepoint is:

namespace TaskHandler
{
public class SimpleHandler:SPEmailEventReceiver
{
public override void EmailReceived(SPList list, 
Microsoft.SharePoint.Utilities.SPEmailMessage emailMessage, string receiverData)
{
SPListItem item = list.Items.Add();
item["Title"] = emailMessage.Headers["Subject"];
item["DueDate"] = 
System.DateTime.Parse(emailMessage.Headers["Date"]).AddDays(21);
item["Description"] = emailMessage.HtmlBody;
item.Update();
}
}
}

However for me to edit it and make it work/deploy it as an event handler is not 
working to well.

Anyways, ANY HELP that any of you developers can provide me with would be MUCH 
APPRECIATED!!!

I am a quick learner!

Thank you,

Mike

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sezai KOMUR
Sent: Thursday, January 31, 2008 10:13 PM
To: listserver@ozMOSS.com
Subject: [OzMOSS] RE: Custom Managed Properties

Re-run the search crawl.

If you have just mapped the Managed Property to a Crawl Property then you need 
to re-run the crawl again in order for the Managed Property to correctly map 
through to the Crawl Property.

Ie.

1.   Crawl once to detect the Crawl Property

2.   Create a Managed Property and Map it to the Crawl Property

3.   Run the crawl again after mapping the Managed Property

Sezai Kömür
Senior Developer  - BEng, BSc - Microsoft Certified Technology Specialist  -  
http://www.moss2007.com.au/

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger Noble
Sent: Friday, 1 February 2008 1:12 PM
To: listserver@ozMOSS.com
Subject: [OzMOSS] Custom Managed Properties

Hi All,
[Sorry this is a bit long winded]
I have a custom Managed Property that is mapped to 

Re: [OzMOSS] Developer help!

2008-02-01 Thread Bill Williamson
PREP: This is an answer you will not like.

If you have no experience developing, then copy/pasting some code is
not the right thing (for your organization) to do.  If you have any C#
developers on staff run this past them.  If not, either buy or
contract someone (with guaranteed support) to do this for you.

You will likely get this right.  But then support comes  someone
wants a modification, or a bugfix

Ad-hoc development is great for learning, but please don't deploy
something you copy-paste from a blog into production anywhere.  You're
doing your employer a disservice, and yourself.

On 2/2/08, MacDonald, Mike <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hi All:
>
>
>
> I am 6 months new to sharepoint administration and we are using a WSS 3.0
> environment.  My problem is I want to create an event handler that will pull
> certain fields (other than the body, subject and email address) of an email
> and then create a new list item with the selected fields.  For Example:
> Create an outlook form with fields like First Name, Last Name, Problem
> description, Contact method (choice field), ID, hardware used (choice field)
> Etc… This is being used for a remote administration we are providing.
>
>
>
> Anyways, I have no experience developing in visual studio, but do have
> access to it. After a few weeks of research I have found the code for the
> event handler that I need to modify and found basic instructions to create
> an event handler, but I have been unsuccessful putting them together and
> building the solution in Visual Studio.
>
>
>
> The code that is responsible for pulling the Body, subject and email out of
> the box in sharepoint is:
>
>
>
> namespace TaskHandler
>
> {
>
> public class SimpleHandler:SPEmailEventReceiver
>
> {
>
> public override void EmailReceived(SPList list,
> Microsoft.SharePoint.Utilities.SPEmailMessage emailMessage,
> string receiverData)
>
> {
>
> SPListItem item = list.Items.Add();
>
> item["Title"] = emailMessage.Headers["Subject"];
>
> item["DueDate"] =
> System.DateTime.Parse(emailMessage.Headers["Date"]).AddDays(21);
>
> item["Description"] = emailMessage.HtmlBody;
>
> item.Update();
>
> }
>
> }
>
> }
>
>
>
> However for me to edit it and make it work/deploy it as an event handler is
> not working to well.
>
>
>
> Anyways, ANY HELP that any of you developers can provide me with would be
> MUCH APPRECIATED!!!
>
>
>
> I am a quick learner!
>
>
>
>
> Thank you,
>
>
>
> Mike
>
>
>
>
>
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Sezai KOMUR
>  Sent: Thursday, January 31, 2008 10:13 PM
>  To: listserver@ozMOSS.com
>  Subject: [OzMOSS] RE: Custom Managed Properties
>
>
>
> Re-run the search crawl.
>
>
>
> If you have just mapped the Managed Property to a Crawl Property then you
> need to re-run the crawl again in order for the Managed Property to
> correctly map through to the Crawl Property.
>
>
>
> Ie.
>
> 1.   Crawl once to detect the Crawl Property
>
> 2.   Create a Managed Property and Map it to the Crawl Property
>
> 3.   Run the crawl again after mapping the Managed Property
>
>
>
>
> Sezai Kömür
>  Senior Developer  - BEng, BSc - Microsoft Certified Technology Specialist
> -  http://www.moss2007.com.au/
>
>
>
>
>
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Roger Noble
>  Sent: Friday, 1 February 2008 1:12 PM
>  To: listserver@ozMOSS.com
>  Subject: [OzMOSS] Custom Managed Properties
>
>
>
> Hi All,
>
> [Sorry this is a bit long winded]
>
> I have a custom Managed Property that is mapped to a Crawled Property.
>
> The Crawled Property is a metadata element in an aspx page, and has been
> crawled and discovered by the query engine. I know that the property has
> been found because on the crawled property page it lists some sample
> documents that use the property.
>
> The problem I am having is that the Managed Property is returning blank when
> I perform a search, and when I look at the Managed Property properties it
> has "Number of items found with this property: 0" in the Content using this
> property section.
>
>
>
> Example metadata element: 
>
>
>
> Thanks for your help
>
> Roger
>
>
>
> [For those who are interested in hearing about my last problem. The client
> still wanted the documents to be crawled instantly when a page was created –
> so I'm starting an incremental crawl every time. So far this works fine, but
> has not been tested under load.]
>
>
>  IMPORTANT NOTICE: This e-mail message is intended to be received only by
> persons entitled to receive the confidential information it may contain.
> E-mail messages to clients of Oconics Pty Ltd may contain information that
> is confidential and legally privileged. Please do not read, copy, forward or
> store this message unless you are an intended recipient of it. If you have
> received this message in error, please forward it back to the sender and
> de