SharePoint 2010: Standalone installation, but with full sql version

For development and testing i usually install the standalone version of SharePoint 2010.

I start with installing win2008R2, then i install sql2008r2, then i install the SharePoint pre-requisites, and when i start installing SharePoint i always realize, i don’t have the option to use the installed sql server. Standalone ALWAYS installs sql express and uses this as the database server.

So i end up with 2 sql instllations.

an alternative is to install a farm, based on local accounts, but that’s not always what i want.

For those who want that, take a look at this article : http://sharepoint.microsoft.com/blogs/fromthefield/Lists/Posts/Post.aspx?ID=112

So, when i wanted to setup a development environment again i wanted to start with SQL installation. However, this time i remembered i don’t need it.

But what if i still want to use it instead of the express version.

that’s when an idea popped up. What would happen if i installed sql as an instance with the name …….. SHAREPOINT.

The same instance name that SharePoint uses for the express installation.

I installed sql2008R2 as an instance with the name SHAREPOINT and then installed SharePoint.

And guess what …. it used the SHAREPOINT instance i created as database for the SharePoint installation.

Voila. SharePoint standalone installation on the full SQL version.

 

regards,

Eric

Project Server WebAccess 2007 odd search dropdown scope behaviour

I have a SharePoint 2007 enviroment (Dutch) with Project server (Dutch) installed.

I created a custom search scope. I added this scope to the dropdown list on my portal. When i use this dropdownlist, i can see the new scope.

I also wanted this functionality on my Project Web Access site(collection). Actually, i even want that new scope to be the default scope.

So i added this scope….. but it didn’t show up (i redirected to search center)

After some investigation. i saw that everything was dutch EXCEPT the names of the display groups.

Although all functionality and all buttons and everything else, it struck me that the names of the different groups where not translated.

I went to my primary portal, retrieved the name of the displaygroups, as they are named in dutch.

Created a new group in my PWA site, added the scopes i want, and guess what : My pulldown menu from the search box, was correctly filled wit hthe scopes i entered.

Seems Microsoft made a hickup in translating :-)

Regards,

Eric

CKS: Development Tools Edition

This project extends the Visual Studio 2010 SharePoint project system with advanced templates and tools. Using these extensions you will be able to find relevant information from your SharePoint environments without leaving Visual Studio. You will have greater productivity while developing SharePoint components and you will have greater deployment capabilities on your local SharePoint installation.

For all developers there are several features you will like.

Get it here.

InfoPath versus Managed Metadata

Instead of using lookup fields i decided i wanted to use Managed metadata fields.

I’ m working on an solution, in which i have to deploy several 100 sites based on a site template.

In the template i have 2 lookup fields, that lookup data. This is working.

But when i need to update the lookup data, i have to do that on all sites, instead of in 1 location.

Managed metadata would be the perfect way to achive this.

BUt i also work with custom infopath forms for several lists, including the list where i want to use managed metadata fields.

And after some strawling around internet, it seems that this is not possible (yet!).

I turns out that this functionality was present in pre-RTM versions of SharePoint, but not in the RTM.

I really hope this will be re-entered with service pack 1

[Ik] filter optie werkt niet — DUTCH ONLY

Als je in een nederlandse SharePoint2010 omgeving gebruik wil maken van de filter [Me], waarbij je dus een lijst kunt filteren op basis van de naam van de persoon die is ingelogd, dan staat er bij het filter netjes, dat in een Nederlandse omgeving hier [Ik] gebruikt moet worden.

Echter, het zal je opvallen dat dit niet werkt.

Vervang echter [Ik] door [Mij] om de filter wel werkend te krijgen.

De omschrijving klopt niet met de werkelijkheid.

Importing managed Metadata

Today i wanted to create some managed metadata terms.

Since i don’t want to type als terms, i decided to upload them using a CSV file. So i exported a list as excel. saved it as csv file and tried to upload this file.

That didn’t work. I got an error about the csv-file, but also an alert telling me to use “importtermset.csv” as an example.

A short journey on my filesystem told me that this file can be found at the following location

/program files/common files/Microsoft Shares/Web server Extensions/14/Template/layouts/<languageID>

Where <languageID> would be 1033 in an english environment.

Download the sample file and use it to upload terms to the termstore.

What you need to know about developing Timer jobs for SharePoint2010

So you want to develop a custom timer job for SharePoint 2010. You looked around in several books and searched some websites.

Ypou created a custom timer job, you deploy it and it seems to be working. However, everytime you adjust the code, no mather what, the old code is run.

You did keep all rules in mind, regarding to building custom timer jobs.

You declared a featuredeactivating, you retreacted the solution.

Still, the original code is run …

The magic behind this is, that although you deactivate and retract the code, the code is still present on the SharePoint server UNTIL you restart the timer job !

So best thing to accomplish a healthy environment for building custom timer jobs is to add 2 pre-build commands.

Open the configuration of your project and add the following 2 rules as a pre-build command

 

net stop sptimerv4

net start sptimerv4

 

Now debug your solution again and see that the new code is run !

How to quickly change the central administration port (2010)

Sometimes, after installing, you find out that the chosen port number is not the best or preferred number. In my case, an application was installed using the same portnumber as central administration.

This can ofcourse be initiated, by the fact that the final portnumber was not yet known at installation time, OR, you have sharepoint 2010 installed as a standalone installation (you are not allowed to choose the admin port in a standalone administration)

So you want to change the portnumber.

Here is how it is done.
Open the sharepoint 2010 management shell ( yep, powershell to the rescue)
type in: Set-SPCentralAdministration
You will be asked the new portnumber.
Or type in : Set-SPCentralAdministration -Port

It will take some time, but then the portnumber of central administration is changed. Done it several times now, sofar, no issues.