I had the problem of saving files which I uploaded programatically to Sharepoint list item. When I tried to save them, there's pop up dialog saying the file is in read only mode, even I had all the required permissions.
I had the problem of page not able to redirect when in an ajax postback. It happens to be the fact that I disabled a line in web.config:. This line should be added in HttpModules, so that redirection will work in Ajax postback. This class manages HttpModules for Ajax functionalities in ASP.NET.
I came across this problem of wanting to add a column in the List view web part (stock standard one) with the ability to have html elements rendered properly. Unfortunately Sharepoint's standard list view only displays text in it.
Lately I had fun digging into Sharepoint database and see how the monster was built and what its database schema looking like. Well, it's pretty smart the way it was built but it's also a pain for developers to understand and even to play with it, if they have to. With the business that I am working for, we have to create reports for corporates, which forces us to having to dig into Sharepoint database directly, even though I read a lot of posts saying that is not recommended by Microsoft.
A useful function to send email in Sharepoint, programatically.
The release of Sharepoint 2007 really helped Microsoft stepping a big step forward into the Intranet market in recent years, but what's predicted coming up bigger than ever is Sharepoint 2010, which many industries experts have shown a lot of love with. When working with Sharepoint 2007, I actually got amazed by its usability and how flexible and useful it could be in a business environment. The even more amazing part is, the bigger the business, the more useful Sharepoint could be to the business.
This post shows you how to retrieve a checkboxlist from a multi choice field as well as how to update the field using SPFieldMultiChoiceValue.
Aaron was creating a custom web service to be used by web parts in Sharepoint, but then there was a problem of a giant list of "undefined" values returning. Done a lot of research and later this brilliant post directed us to the right place.
I wanted to use Ajax control toolkit in Sharepoint, and had not had any luck until I spent the whole day debugging and getting it to work. I already had Ajax integrated in Sharepoint, so it should be fairly easy to just add in AjaxControlToolkit, but the problem is the latest version of it actually requires you to use ToolkitScriptManager instead of ScriptManager, otherwise your control will not work and you will see a Javascript error of "Please wait while scripts are loaded".
I had to create a task dynamically in C# and assign the task to a reviewer, which is a user account. However, there was this problem of the "Assigned to" field is only read only. To do that, just create an SPFieldUserValueCollection and assign it to task item.
I needed to get SPUser object from doing a lookup using CAML query, so that I could get the user information such as email address, etc. To do that, this is the code that I used:
I had the problem of not able to debug Sharepoint in Visual Studio 2008 awhile ago, and glad that Aaron shown me how to do it by doing some tricks. What happened was the PDB file might not have been deployed to the assembly GAC.
Yesterday I spent the whole day finding on the Internet about how to restore the list form web part of my edit form as I accidentally deleted it and could never get it back from the Closed web parts, nor could I get it back by resetting the file to site definition in Sharepoint Designer.
Lookup field is a field which links a child class to a parent class, it is an association kind, which allows a list item to reference another item from another list. However, reading and writing to a lookup field is different from a normal field. We need to use the class SPFieldLookupValue to archieve this.
I was trying to create a web part with WSPBuilder installed on Visual Studio 2008, but had the problem of rendering a user control. Then I came across this blog post, which explains the steps in wrapping usercontrol with WSPBuilder solution. What's even greater is we can setup a structure which seperates the application presentation layer with the WSP project.
One of the thing I hate most about Sharepoint is its naming. It does not tell the administrator what name it's actually storing a column field of, and this could always lead to errors.
Recently I had the chance to customise the advanced search box of Sharepoint server portal, with own fields/ properties and defined a seperate scope for it. It was not hard, but needs some research and practical experiments.
Recently, I had the chance to play around with ajaxifying Sharepoint server. As you would have probably known, Ajax is a great feature in .NET 3.5 but MOSS 2007 was shipped before Ajax was out. So, to use it, we just need some configurations done.
SharePoint list has permission down to the list level, but what if we need to control view, edit and display for each column? I have been researching on a lot of add-ons around the Internet and luckily found one that works just brilliantly. There's this add-on called SPListDisplaySetting, hosted on CodePlex, which allows you to do that. Strange thing is the first time I installed it, it didn't work as it cooked up my list to not showing the action toolbar and i had to re-install WSS to get it back in shape.
Sharepoint comes with a great GUI tool that allows administrator to create and manage data structure, that means we could create our own columns and set up the associations, etc. However, the default field types out from the box are limited. The great news is we could create our own field types with own business logic. I just tried to create a custom field type called "Phone Number", which is a standard text field but with Javascript validator that validates the input string to be a valid phone number.
I have been digging into SharePoint for awhile now and it seems to be more and more interesting and challenging, considering I already have experiences with so many different Content Management Systems. Suprisingly, SharePoint seems to work very similar to Helium, so that eased my process of going in and out of Sharepoint.