Karthick's Blog

MOSS 2007 : WSS 3.0 : How do you add items into Choice Site Column type.

MSDN Archive — Wed, 10 Jan 2007 14:24:00 GMT

Here is the sample code,

                SPWeb web = new SPSite("https://karthick64:4040/").OpenWeb();
                SPField spField = web.Fields["MyChoice"];
                SPFieldChoice choiceFields = (SPFieldChoice)spField;
                string[] choices = new string[3] {"x", "y", "z"};
                foreach (string choice in choices)
                {
                    choiceFields.Choices.Add(choice);
                }
                choiceFields.Update();

Keep Exploring... :)

MOSS 2007 : WSS 3.0 : How do you add a new Site Column to a Content Type using the MOSS object model?

MSDN Archive — Mon, 08 Jan 2007 09:08:00 GMT

How do you add a new Site Column to a Content Type using the MOSS object model?

Here is the sample code

SPWeb web = new SPSite("https://localhost:4040").OpenWeb();

SPContentType myCT = web.ContentTypes["myNewContentType"];

myCT.FieldLinks.Add(new SPFieldLink(web.Fields["abc"]));

myCT.Update();

Note :

The following MSDN article speaks about “Updating Child Content types”.

https://msdn2.microsoft.com/en-us/library/ms442695.aspx

The example given in the article uses the SPFieldCollection object (SPContentType.Fields) to add columns to the content type. But when we use the sample given in the article we end up with the error message “SPException: This functionality is unavailable for field collections not associated with a list.”. I found that the columns are not added into content type and that are referenced in content type from the following article.

https://msdn2.microsoft.com/en-us/library/aa543526.aspx

Also the above article “How to: Reference a Column in a Content Type” says,

The Fields property returns an SPFieldCollection object. Each SPField in this collection represents a "merged view" of the base column definition and any overwritten properties specified in the column reference in the content type. Because of this, you cannot add columns directly to this collection. Attempting to do so results in an error.

Keep Coding...

MOSS 2007: WSS 3.0: How to add/delete/update site columns by using SharePoint WebService

MSDN Archive — Tue, 02 Jan 2007 12:34:00 GMT

SharePoint's Webs webservice can be used to add/delete/update site columns. Unfortunatley MSDN/SDK doesnot has the sample yet. Here I provide the sample code.

//webs webservice object

localhost.Webs websService = new ContentTypeAndSiteColumn.localhost.Webs();

//url for the webservice

websService.Url = "https://localhost:4040/_vti_bin/Webs.asmx";

//credential

websService.Credentials = System.Net.CredentialCache.DefaultCredentials;

//xmldocument object

XmlDocument xDoc = new XmlDocument();

//Fields to be added

XmlElement newFields = xDoc.CreateElement("Fields");

//Fields to be edited

XmlElement updateFields = xDoc.CreateElement("Fields");

//Fields to be deleted

XmlElement deleteFields = xDoc.CreateElement("Fields");

newFields.InnerXml = "";

deleteFields.InnerXml = "";

XmlNode returnValue = websService.UpdateColumns(newFields, updateFields, deleteFields);

MessageBox.Show(returnValue.OuterXml);

MOSS 2007 : CMS 2002 Migration Issue : How to rename a resource Gallery Item?

MSDN Archive — Wed, 20 Dec 2006 16:35:00 GMT

Unfortunately MCMS 2002 Site Manager doesnt allow you to rename the resource gallery item. In some situation you may end up duplicate entries in the resource gallery item names. MCMS 2002 allows you to have multiple resource items with same name. The items will be differentiated by using their guids. But this will endup a problem when you are migrating to MOSS 2007, and you will get "Leaf names are not unique." error message. And the suggestion is you have to rename the resource gallery item. Here is the sample code to rename the resource gallery item.

// Get the MCMS application context.

CmsApplicationContext cmsContext = new CmsApplicationContext();

// Logon to MCMS:

// Assumes that you have Windows Authentication turned on.

WindowsIdentity ident = WindowsIdentity.GetCurrent();

// Make sure to set the context to Update mode (which means you can write

// back to MCMS using PAPI).

cmsContext.AuthenticateUsingUserHandle((System.IntPtr) ident.Token.ToInt32(),PublishingMode.Update);

ResourceGallery rsg = cmsContext.Searches.GetByPath("/Resources ") as ResourceGallery;

Resource res = rsg.Resources[“Content Development”];

res.Name = "EMP1.gif";

res.DisplayName = "EMP1.gif";

// Commit changes back to MCMS.

cmsContext.CommitAll();

Keep coding :)

WSS 2.0 : How to upload images by using Imaging WebService

MSDN Archive — Wed, 13 Dec 2006 12:54:00 GMT

Here you go for the sample code.

                 try
                 {
                             //create imaging web service object
                             localhost.Imaging img = new ImagingTest.localhost.Imaging();
                             //set url
                             img.Url = https://localhost:8081/sites/site1/_vti_bin/Imaging.asmx;
                             //Set credential
                             img.Credentials = System.Net.CredentialCache.DefaultCredentials;
                             //for results
                             System.Xml.XmlDocument resdoc= new System.Xml.XmlDocument();
                             System.Xml.XmlNode resnode = resdoc.CreateNode(System.Xml.XmlNodeType.Element,"Result","");

                            System.IO.FileStream fs = new System.IO.FileStream("c:\\n15.jpg",  System.IO.FileMode.Open, System.IO.FileAccess.Read);
                            //Get the content
                            byte[] content = new byte[fs.Length];

                            //store the content
                            fs.Read(content, 0, (int) fs.Length);

                            //Upload the file - specify "" for root folder, for sub folders specify 1, 2, 3 relative to the folder number
                            resnode = img.Upload("123", "", content, "n15.jpg", true);
                            MessageBox.Show(resnode.OuterXml);
                 }
                 catch(Exception ex)
                 {
                        MessageBox.Show(ex.ToString());
                 }

WSS 2.0 : "Getting unauthorized access" error when ‘User must change password at next logon’ is enabled

MSDN Archive — Wed, 13 Dec 2006 12:48:00 GMT

Problem Background : When you enable "user must change password at next logon", then the corresponding user will face the unauthentication issues.

To resolves this, you may enable IISADMPWD for WSS

How to enable the IISADMPWD for WSS?

To register iispwchg.dll, follow these steps:

Click START, and then click RUN
In the open box type the following and then press ENTER:
Regsvr32 “%systemroot%\system32\inetsrv\iisadmpwd\iispwchg.dll

To create the IISADMPWD virtual directory, follow these steps:

In the Internet Services Manager Microsoft management Console (MMC), expand Web Sites, right-click the , select New, and then select Virtual Directory.
When the Virtual Directory Creation Wizard starts, follow the instructions to create the virtual directory with the alias IISADMPWD. Point the path to the local %systemroot%\System32\Inetsrv\Iisadmpwd directory. For the Access Permissions allow both Read and Run Script privilages.

To execlude IISADMPWD from WSS Managed path, follow these steps:

Click start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration
On the Central Adminitstration Page, under Virtual Server Configuration, click Configure virtual server settings
On the virtual server List Page, select the virtual server you want to configure
On the virtual server settings page, under Virtual server Management, click Define Managed paths.
Under Add a New Path, type iisadmpwd, and in Type select “Excluded Path” and then click OK

To set the PasswordChangeFlags value in the IIS metabase, do the following:

From a command prompt browse to the C:\Inetpub\Adminscripts directory.
Type adsutil.vbs, and then press the ENTER key. If this is the first time that Adsutil.vbs has been run, you may get error messages stating that Cscript is not registered. Follow the prompts and choose Yes to register Cscript.
Type adsutil.vbs set w3svc//PasswordChangeFlags 1
Note : The id for the SharePoint site can be identified from the IIS manager. In IIS manager select websites and you can identify the identifier for individual site from the right pane.

Now you will be able to get the IIS password management page when the “User must change password at next logon” selected.

[Keep Using SharePoint]

WSS 2.0 : How to enable document library eventhandlers by default

MSDN Archive — Wed, 13 Dec 2006 11:33:00 GMT

Open the Site definition folder. If you use default Site definition, STS, then open the folder from the following location. “C:\program files\common files\Microsoft Shared\web server extensions\60\template\1033\STS

Note: Modifying the default files is not supported by Microsoft. Microsoft recommends using custom Site Definition.

Open the List Definition folder. If you use default list definition for document library, then open the “DOCLIB” folder in the LISTS folder
Open the “SCHEMA.XML” file in notepad or visual studio· Modify the LIST node by adding the EventSingAssembly, EventSinkClass, and
EventSinkData

Note:Here I hardcoded the EventSinkAssembly for sample. Could you please change it according to your component.

Restart IIS.

After configuring the details, if you create new document library based on the list definition, then the document library event handler will be automatically
configured.

WSS 2.0 : stsadm - can't delete wppack with slash in its name

MSDN Archive — Wed, 13 Dec 2006 11:01:00 GMT

If you install a wppack by using stsadm with slash "/", then you will not be able to uninstall it by using the stsadm tool :( . The story not endup here, you will not be able to install the latest version of your webpart :(. However SharePoint object model helps us to resolve the problem. Run the following code to remove the wppack that has "/" in the path. Then install your webpart by using stsadm by using the "\" in the path.

Example, running the following command will endup with the above problem.

stsadm -o addwppack -filename "Helloworld/TestDeploy.CAB"

SPGlobalAdmin oGA = new SPGlobalAdmin();
oGA.RemoveWPPack("helloworld/testdeploy.cab",0,null,null);

WSS 2.0 : How to programmatically enable/disable the rights at Virtual server level?

MSDN Archive — Wed, 13 Dec 2006 10:59:00 GMT

To enable all rights at the virtual server level
vServer.Config.Properties["virtualserverpermsmask"] = "-1";

To disable the “Manage Site Groups” permission at the virtual server level
vServer.Config.Properties["virtualserverpermsmask"] = "2113867535";

Keep Coding ;)

WSS 2.0 : How to save properties of webpart from webpart code

MSDN Archive — Wed, 13 Dec 2006 10:37:00 GMT

There are two methods, SaveChanges and SaveProperties provided by WSS which sometimes misleading users. Here I provide details for which method to use and when to use.

SPWebPartCollection.SaveChanges() - This method is used to save the changes made in the web part from out side the web part code. For e.g., the console application, windows application etc..,

SPWebPartCollection.SaveProperties - This method is used to save the properties within the web part code.