Skip to content
/

As announced yesterday by Microsoft the Office 2010 products will be 64bit only. Well no surprise there, we already knew that. But they went even further: Windows Server 2008 and SQL Server on 64bit is a must for ensuring the best performance possible.

As announced yesterday by Microsoft the Office 2010 products will be 64bit only. Well no surprise there, we already knew that. But they went even further. Because of their experience with customer implementations of the 2007 series they recognize that having Windows Server 2008 and SQL Server on 64bit is a must for ensuring the best performance possible. Therefore the 2010 will only be available on those versions!

Also on the client side there will be an improvement as Internet Explorer 6 won’t be supported anymore.

So to summarize:

  • SharePoint Server & Project Server 2010 will be 64-bit only
  • SharePoint Server & Project Server 2010 will require 64-bit Windows Server 2008 or 2008R2
  • SharePoint Server & Project Server 2010 will require 64-bit SQL Server 2005 or 2008 (But you should choose 2008)
  • SharePoint Server & Project Server 2010 will only support Internet Explorer 7 or 8
/

I was working on some old code which created three DropDown controls with hours, minutes and seconds.
I wanted to LINQify it using the LINQ Range method.

I was working on some old code which created three DropDown controls with hours, minutes and seconds.

This was the original code:

for (var i = 0; i < 24; i++)
{
    Hour.Items.Add(new ListItem(i.ToString()));
}

for (var i = 0; i < 60; i++)
{
    Minute.Items.Add(new ListItem(i.ToString()));
    Second.Items.Add(new ListItem(i.ToString()));
}

I wanted to LINQify it using the LINQ Range method:

Enumerable.Range(int start, int count)

This returns an IEnumerable<int> collection with the corresponding range of values. So my DropDown controls are now created with the following code:

Hour.Items.AddRange(Enumerable.Range(0, 24).Select(i =>
                                               new ListItem(i.ToString())).ToArray());
Minute.Items.AddRange(Enumerable.Range(0, 60).Select(i =>
                                               new ListItem(i.ToString())).ToArray());
Second.Items.AddRange(Enumerable.Range(0, 60).Select(i =>
                                               new ListItem(i.ToString())).ToArray());

This could be optimized by using a variable for the sixty values which could be used twice.

Filed under C#
Last update:
/

It’s a sad and known fact that having lot’s of ACL’s in your SharePoint database has a negative effect on the performance of your site. What I didn’t know yet was that changes to the ACL will impact you incremental crawls.

It’s a sad and known fact that having lot’s of ACL’s in your SharePoint database has a negative effect on the performance of your site. What I didn’t know yet was that changes to the ACL will impact you incremental crawls. Vikram Lakhotia has posted a description about this in his blog post: “SharePoint Incremental Crawl taking a long time after adding or removing a user”.