Because I like to share knowledge
With the introduction of LINQ, the difference between writing code for accessing a list of objects in memory and accessing a list of data in an external data source like SQL Server is vanishing.
Combining an “in memory” list with an external list in a single query was not yet possible. With the introduction of .NET Framework 4.0 this has changed.
In this article, I want to filter my SQL data using a list of integers I have stored in memory.
With SharePoint 2010 the number of databases on your SQL Server has grown quite a bit.
By default, most of these databases have their recovery model set to FULL.
After some time, you will discover you’re running out of space.
When you have a SharePoint farm and you want to use accounts from another domain you need a partial (one-way) or a full (two-way) trust between those domains.
A full trust is not always desirable and there your problem begins. After setting up the one-way trust you can authenticate with an account from the trusted domain, but the SharePoint People Picker won’t show any accounts from this domain.
It has been documented by others before, but as I ran into this recently, I will give my summary how I fixed this.
This solution is the same for WSS 3.0/SharePoint 2007 as SharePoint 2010.
When using a one-way trust, you do not see any accounts from the other domain in the people picker.
This is an example of how you could use a partial trust.
You want to allow employees to authenticate in a development farm, but you do not want to allow any test or service account from the development domain to authenticate in the company domain.
As the application pool account is based in the development domain it doesn’t have the right to query the company domain.
Using STSADM
we can configure which forests and domains are searched for accounts by setting the peoplepicker-searchadforests property.
The best part is that we can supply a username and password for a trusted domain.
SharePoint does not allow you to store this username and password in plain text on the server. So, you will have to configure a secure store. If you skip this step, configuring the search account for trusted domains will always fail with the following message.
“Cannot retrieve the information for application credential key.”
To create a credential key, you will have to use the following command.
stsadm -o setapppassword -password <password>This command has to be executed on every server in the farm.
Now you can configure the forests and domains you want to search using the following command.
stsadm -o setproperty -url <web application url> -pn peoplepicker-searchadforests -pv forest:<source forest>;domain:<trusted domain>,<trusted domain>\<account>,<password>You can combine any number of forests and domains, but you need to specify at least one.
You also need to include all forests and domains in one statement because every time you execute this command it will reset the current settings.
Also note this setting is per web application, and even per zone.
The other day I attended a meeting where the presenter switched from a PowerPoint slide to demonstrate an application. When he made the switch, it was quite obvious the beamer was setup to only display the 4:3 slides to the maximum of the white screen. Since his desktop was in a 16:10 resolution the application was falling off the screen on both sides. Which was quite a distraction.
When I was preparing a presentation myself, I wanted to be sure my presentation would be in the same resolution as my desktop as I would be switching between my slides and Visual Studio.
With the launch of Visual Studio 2010 this week a lot of people will start upgrading to the new version. After the installation was complete, I noticed the Surface project and item templates were not available.
In this article I explain how to get the entries in Visual Studio 2010.