Ideas for Free

English:
(This articles has already been posted in www.msd2d.com. Now I post it again in my own blog.)

SharePoint 2003 has come with very easy user interface and many automated (template) form. You can leave traditional way of creating new table and corresponding form entry to SharePoint. Table, folder or files in traditional web application, are replaced by ‘cross-handling’ list in SharePoint as well as the corresponding template forms. For example creating new CustomEdit List will virtually add several template forms (AllItems.aspx, DipForm.aspx, EditForm.aspx, and NewForm.aspx) (Figure – 1)

Figure – 1. New empty list with corresponding template form

English:
(This articles has already been posted in www.msd2d.com. Now I post it again in my own blog.)

Whatever list you made, SharePoint will automatically add the first instantly visible column name “Title” (unless you’ve made custom list definition). The “Title” column is special because it has two consecutive column view, one which is linked to Context Menu, and the other one is linked to item URL. (Figure 1)

Figure -1. Title linked to item and edit menu are always created

English:
(This articles has already been posted in www.msd2d.com. Now I post it again in my own blog.)

Ever reference to strong named assembly? Referencing to an assembly or other project within solution is common task in object oriented programming environment. For example, when you have made a generic library that hold base class for the next projects, you will need to create a reference to that library so you can derive from the base class. Basically you can create reference to any library – however in strong named environment there is an additional requirement; that is you can only create reference to strong named library. Likewise the ordinary solution, you can also create reference to strong named projects. But do you realize what differences between those types of referencing are? This article will discuss the differences within strong named solution.

English:
Do you know that content editor webpart can take down your sharepoint’s site?

Indonesian:
Tahukan Anda, kalau content editor webpart dapat menyebabkan gangguan fungsi pada situs Sharepoint?

English:
Have you tried Sharepoint Designer 2007 – the next version of Frontpage 2003? If you haven’t just grab one from Office 2007 beta site.

The products offers advance features from its old brother, but I found one serious bug. It appears when we export listview into XSLT view.

 Indonesian: (source code)

Didalam Sharepoint 2003, kita mengenal Document Library. Document Library pada dasarnya adalah List yang “dihubungkan” dengan folder, sehingga Document Library dapat digunakan untuk menyimpan file.
Cara penyimpanan file di Document Library mirip dengan proses penyimpanan attachment di List, dan file di Document Library akan berkaitan langsung dengan satu record di List.
Hal ini mengakibatkan, file-file di Document Library tidak bisa memiliki attachment (dokumen pendukung).
Lantas, apa yang harus dilakukan agar file-file di Document Library tersebut dapat memiliki attachment?

English (source code):

In SharePoint 2003, we knew about Document Library. A Document Library basically is a List which was “connected” to a folder, therefore Document Library is a file repository in SharePoint 2003 model.
Uploading file to Document Library works similliar with attaching file to a List. A file in Document Library will always have a correspond record in a List.
That’s why, files in Document Library can not have any attachment.
Then what should we do, to make our Document Library supports attachment?

English:
(This articles has already been posted in www.msd2d.com. Now I post it again in my own blog.)

Introduction

I am very sure that most of us have been familiar with NewForm.aspx from Sharepoint. That kind of submission form by Sharepoint is a template, which is then populated based on columns definition of a list. So we can have date field, number field etc., depends on columns definition.Surprisingly, that form is made by some JavaScript object. (Figure-1).