Tommy Segoro

This article mentions all of the software requirements to install SP 2010 BETA:

http://sp2010journal.blogspot.com/2010/01/installing-sharepoint-2010.html

http://sp2010journal.blogspot.com/2010/01/sharepoint-2010-beta-does-not-need-8gb.html

When SP2010 first came out everyone said that you’ll need at least 4GB of RAM. Since I don’t have that luxury just yet (my new laptop hasn’t come yet at the time of writing this article), I can only give 1GB of RAM to my VM.

Guess what… Sharepoint 2010 installed successfully on VM with 1GB of RAM.

Cheers,

Tommy

Below is the list of articles I’ve written in regards of my experience in configuring Sharepoint 2010 BETA for the first time:

http://sp2010journal.blogspot.com/2010/01/configuring-sharepoint-2010.html

http://sp2010journal.blogspot.com/2010/01/configuring-sharepoint-2010-part-2.html

http://sp2010journal.blogspot.com/2010/01/configuring-sharepoint-2010-part-3.html

http://sp2010journal.blogspot.com/2010/01/user-profile-query-returns-nothing.html

It’s time for me to configure the User Profile Synchronization service. I started with configuring the connection. It can somehow crawled and displayed my OU structure but when I click OK it returns to the connection listing page with the following error message:

“The query returns nothing”

I then research in Google and found the following article:

http://www.khamis.net/blog/Lists/Posts/Post.aspx?ID=19

I looked in Event Viewer and I found out that the account I was using to crawl AD didn’t have access. At this stage I was using SEGORO\sp_admin (account used to install SP 2010 Beta).

I then logged off and re-logged back in using SEGORO\sp_farm (account used to run services). When I tried to re-create the connection it worked.

Hope this helps,

Tommy

http://sp2010journal.blogspot.com/2010/01/how-to-change-from-sandboxed-solution.html

I’ve arrived at a stage where I wanted to create my own custom Sharepoint solution using Visual Studio 2010.

When I created a new blank Sharepoint project it asked me whether I want to deploy the solution as a Sandboxed Solution or a Farm Solution.

I first selected Sandboxed Solution but then I found out that I couldn’t build and package my solution when I had a Sharepoint Mapped Folder within it.

Therefore, I needed to change the type of the deployment to Farm Solution. I looked everywhere (from Project Properties, Solution Properties, etc) and I couldn’t find the setting for it.

I tried to re-create the project and now selected Farm Solution as the deployment type and I then tried to compare the project properties manually. This included opening the .csproj file in Notepad and compared between the two apple-by-apple.

I noticed the following missing tag within the project file (.csproj) that was deployed as Sandboxed solution:

<SandboxedSolution>False</SandboxedSolution>

I added that tag to my .csproj and now my Sandboxed Solution project suddenly became Farm Solution project.

Hope this helps,

Tommy

This is regarding Visual Studio 2010 Sharepoint 2010 project template.

Read more on http://sp2010journal.blogspot.com/2010/01/elementfile-vs-elementmanifest.html.

When creating a custom site template we will normally need to create our own webtemp file. Within the webtemp file we will need to specify the ID for our custom site template and that ID (based on Microsoft’s recommendation) needs to be bigger than 10000.

Tracking these IDs aren’t that easy either especially when we need to develop several custom site templates for different clients ie. how do we know if we’ve used a particular ID?

Some people suggest to use current date and time as the ID. This has worked well for me except if it’s too long! It can definitely take current date (eg. 270110) but it can’t take date+time (eg. 2701102330) because it’s too long.

When it’s too long we’ll get the following error when trying to create a site collection using that custom site template:

A list, survey, discussion board, or document library with the specified title already exists in this Web site. Please choose another title.

Hope this helps,

Tommy

We all know that content types and fields are handled poorly in WSS 3.0 and MOSS 2007. When we add them to a list then trying to add new fields, etc most of the time it will break. But it’s now all different with SP 2010.

Read more on http://sp2010journal.blogspot.com/2010/01/sharepoint-2010-list-content-types-and.html.

By default VS 2010 Sharepoint 2010 project template doesn’t come with upgrade option. I have ripped off the code of Microsoft website.

More on http://sp2010journal.blogspot.com/2010/01/upgrade-add-in-for-sharepoint-visual.html.