Now that we know how to create a simple Webpart, we want to add more functionality to it. Let us start with some Controls.
Declare a Control as class variable Create it in CreateChildControls Modify the Control in OnPreRender Render the Control with its content Declare a Control public
class
simpleWebpart:WebPart
{
private
HtmlGenericControl _MyDiv;
CreateChildControls This method creates the control. After the creation, we will be able to access the control from elsewhere, to modify its properties or its content.
To deploy a Webpart to a SharePoint Installation, complete the 3 steps beneath:
Copy the dll from your Webpart to the bin folder of a webapplication Register the dll in the web.config as safe Add the Webpart to the Webpartgallery of a sitecollection Debug the Webpart Copy the dll from your Webpart to the bin folder of a webapplication Copy your dll to the bin folder of your IIS virtual server directory.
In this blog post, I want to show you how to create a simple Webpart. All you need is a Visual Studio 2005 (e.g. the express version) and of course SharePoint.
Start your VS and create a new “Class Library”
Add a reference to the Microsoft.SharePoint.dll. We will create a SharePoint Webpart, to be able to add Properties.
To display some text, override the render method. You have to create a reference to the Microsoft.
Falls bei der Benutzung des Webparts ein Fehler wie:
Fehler bei der Anforderung des Berechtigungstyps Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint.Security, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. auftritt, muss der Trustlevel in der web.config auf Full gesetzt werden.
Zum vollständigen Beitrag: http://www.hezser.de
Update 23. Apr 2008:
Ich habe eine neue Version bereitgestellt.
You can configure a task list, to send an email if you assign a task to somebody. This works fine if this somebody has an internal email address.
If you happen to have an account inside the environment of the SharePoint Server, and configure it to have an external email address, sending an email to this account might fail. In the SharePoint Logs there is an entry:
03/12/2007 14:40:42.29 OWSTIMER.
If you want to modify the default.master masterpage in the root site of a sitecollection, you have to be a sitecollection owner. Otherwise you get an “access denied” error if you try to open, or check out the default.master.
If you want to modify the current listitem, the OnAfterChange Event will trigger again.
You can avoid this by disabling the trigger before the update:
this.DisableEventFiring();
item.SystemUpdate(false);
this.EnableEventFiring();
After adding a new Server to the SharePoint farm, I removed the old one.
The central administration page was not accessible. It said “error 500” in the browser. By changing the admin port via “stsadm -o setadminport -port 12345” and back to the original port, I was able to regain access to the central administration page. Testlink to Yvonne for EBE Tracking Test: http://yvonneharryman.wordpress.com/2009/06/28/sharepoint-beacon-is-the-new-home-for-my-blog-regarding-sharepoint/
After adding a new Server to the SharePoint farm, I removed the old one.
The central administration page was not accessible. It only said “error 500” in the browser. By changing the admin port via “stsadm -o setadminport -port 12345” and back to the original port, I was able to regain access to the central administration page.
If you write a Webpart with custom properties, you have to take care of the default value.
[WebBrowsable(true),
DefaultValue(“value”),
Personalizable(true),
WebDisplayName(“some property”), WebDescription(“Description of the property”)] public
string PropertyName { get { return _ PropertyName; } set { _ PropertyName = value; } } Please do not specify a default value, which you might actually use. The default property value will not be saved, if you choose to configure it with the default value!
