Patrick Tisseghem was going to speak about SharePoint site definitions and templates on the TechEd 2005 in Amsterdam, but his session agenda has changed. He will be speaking about another very interesting session:

Creating Dynamic Web Sites with ASP.NET 2.0 Web Parts
"Drill down on the new Web Parts infrastructure in ASP.NET 2.0. Learn how you can use Web Parts to build rich Web sites-enabling end users to dynamically control the layout of pages-and customize the properties of server controls."

We already had a session internally about this subject given by Mart. I will certainly be there as SharePoint Geek! :)

http://blog.u2u.info/DottextWeb/patrick/archive/2005/06/09/4311.aspx

On the blog of Eric Javri we can read that November 7th is going to be the official launch date of Team System. The rest of the products like SQL Server 2005, Visual Studio 2005 and Biztalk Server 2006 will be launched during the week of November 7th according to Paul Flessner, senior vice president of Server Applications at Microsoft.

MSDN:
http://msdn.microsoft.com/launch2005/

Presspass:
http://www.microsoft.com/presspass/press/2005/jun05/TechEd2005Day2PR.mspx

FTPOnline:
http://www.ftponline.com/weblogger/forum.aspx?ID=1&DATE=06/07/2005&blog=#385

 

http://blogs.msdn.com/ejarvi/archive/2005/06/07/426490.aspx

I found a cool article at Mads's thoughts about setting a custom WebPart property in the dwp file. Setting the initial value for a custom property is mostly done by hardcoding the value in your control. He describes a way to to this through the dwp file of the WebPart. As he stated:

You've got to annotate the webpartclass with a reasonable namespace like this:

[DefaultProperty("Text"), ToolboxData("<{0}:SearchForm runat=server></{0}:SearchForm>"),
XmlRoot(Namespace="Some.Reasonable.Namespace")]
public class SearchForm : Microsoft.SharePoint.WebPartPages.WebPart
{
   ...
}

And then tag your property elements in the dwp file with the same xmlns:

<UserControl xmlns="Some.Reasonable.Namespace">URI</UserControl>

And your webpart has an initial propertyvalue after deployment.

http://weblogs.asp.net/mnissen/archive/2004/05/20/135744.aspx

The ICANN (International Corporation for Assigned Names and Numbers) responsible for management and control of domain names has reported that at the end of this year the extension xxx is going to be available for the use of porn sites.

I'm curious... does this mean that porn sites are going to use this extension instead of the current sites? I don't believe that.

At the other hand it would be better for the internet and easier to filter these types of sites out. Especially with children on the internet.

Lets wait and see, it is good start for a cleaner internet :)

 

In one of the portals we removed the "Site settings" link from the page to prevent users clicking on it. For some additional users which have administrator rights we created a WebPart containing links to the most needed functionality. This custom WebPart contains a direct link to the settings of the current page, a direct link to the settings of users of the current page and a link to delete the current page and its children.

When designing websites and no texts are yet delivered by your customer you need "Lorem Ipsum"

"Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum. "

I found a site which generates "Lorem Ipsum" texts for you :)

http://www.lipsum.com/

I got a question from someone if it is possible to remove the help link from the webpart menu. And if possible to remove the whole webpart menu itself. The answer the first question i did some digging and found out the following stuff.

If we take a custom webpart, to remove the menu, or one or more menu items it is relative very easy. I wrote already an article about this. This can be easily accomplished by overriding the CreateWebPartMenu() method. and if needed setting the this.WebPartMenu = null;

To remove the Help from the menu you could also go into "Modify Shared WebPart" and clear the "Help Link" field under the "Advanced" category.

If we take a default webpart like a list or event, it seems that it does not work that way. These default webpart have already a "Help Link" filled in. Clearing the "Help Link" will not do anything and going into the "Modify Shared WebPart" will return the original url. It is possible to change it and it is reflected when you select the help from the menu but as soon as you go into "Modify Shared WebPart" it is returned to its original state. Meaning that when OK or Apply is pressed you back to start.

Why? I don't know. Feature or bug? I also don't know

I was looking for some answers on some questions i had through google when i came across this post which explains how to get your own scripts included in SharePoint pages. The article is from last year but its definitly the trouble reading it. Nice work :)

Changing the existing .js files like the ows.js file will work and keep the pages ghosted. But as described these files could be replaced by service packs or feature updates.

The solution is changing the <project> element in the ONET.xml file which will keep the pages ghosted and is not replaced by updates.

<Project Title="Blog Site" ListDir="Lists" CustomJSUrl="/_layouts/1033/cBlog.js" xmlns:ows="Microsoft SharePoint">
...
</Project>

The artice:

http://dev.collutions.com/blogs/sample/DisplayPost.aspx?PostID=8

For multiple .js files:

http://www.sharepointblogs.com/dustin/archive/2004/08/24/718.aspx

Another method of hooking in script logic is to use behaviours:

http://markharrison.co.uk/blog/2004/12/client-side-scripts-available-in.htm

 

Maurice wrote last year an article about the benefits of closing an disposing SPSite and SPWeb objects. In most cases it is therefor usefull to use the using functionality of .NET.

IMPORTANT:But as he stated in his last post you should never call dispose on a reference got from a SPSite by calling the method SPControl.GetContextSite. Only call Dispose() and Close() on your own objects.

http://www.bluedoglimited.com/SharePointThoughts/ViewPost.aspx?ID=175

Thanks Maurice for pointing this out to us! :)

 

Mike Fitzmaurice is talking about the SharePad project which can be found on GotDotNet. If you want to add document library support for your own editor you will have to use the FrontPage RPCs according to Mike. As stated on the website of GotDotNet:

"SharePad is a reference application demonstrating Microsoft Office-style SharePoint integration techniques. This application illustrates the use of the Front Page RPC calls exposed by SharePoint among other SharePoint integration APIs."

The following functionality is available:

Open a file that’s stored in a SharePoint document library

Save a file to a SharePoint document library

Navigate through the libraries in a SharePoint site

Check out the file

Check in the file

Register it within the WSS/SPS environment so it launches your editor automatically (like we do for Word, Excel, and PowerPoint documents)?

Set custom properties on the file as you save it

Read a file’s custom properties at the time you open it

http://blogs.msdn.com/mikefitz/archive/2005/05/30/423276.aspx