Montag, 26. April 2010

The Daily Boop: My favourite Calvin (& Hobbes)!

Besides SharePoint ... some good philosophy :)
The Daily Boop: My favourite Calvin (& Hobbes)!

Daily Business - SharePoint 2010 Accounts

 

For an SharePoint Installation always create specials service accounts, each with it’s own email account.

Account Name Description
sp_sql Service account for SQL Server services: MSSQLSERVER, SQLSERVERAGENT
If you have already SQL Server somewhere running on a neat cluster, you don’t have to care about. But you should have access to your instance with SQL Management Studio.
sp_admin This account is local admin on your sharepoint servers (WFE, App). It’s a Domain-User account.
This account is not a local admin on your SQL machine!
Use it to install everything (SharePoint itself, Patches, Add-on and so on). Run the config wizard with this account. Simply: if you want to install something for SharePoitn log in with this account.
sp_farmadmin This account is local admin on your sharepoint servers (WFE, App). It’s a Domain-User account.

Use this account when the config wizard asks for the database access acount.

Montag, 8. März 2010

Issue creating Application Page named “default.aspx” with Inherits-Statement

I just created an application page within an empty SharePoint 2010 project with Visual Studio 2010 RC.

I named the page “default.aspx”.

Visual Studio then generated the files and wrote

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="default.aspx.cs" Inherits="WebControls.Layouts.WebControls.@default" DynamicMasterPageFile="~masterurl/default.master" %>

in the aspx file.

This runs into an error. I don’t know why VS2010 writes @default instead of simply default in the “Inherits” statement. It only does when using “default.aspx” as the name for the application page. If you choose another name, no problem:

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="mypage.aspx.cs" Inherits="WebControls.Layouts.WebControls.mypage" DynamicMasterPageFile="~masterurl/default.master" %>

Maybe a bug, maybe a feature.

Solution: simply delete the @ in the Inherits-Statement.