I have had to do some work on Data List Views recently after migrating from 2007 to 2010 since DataFormWebParts don't really work as they should in 2010, especially when it comes to the DispForm.aspx, for example, especially because (at least I found this) it would not open the DispForm.aspx page in Modal Dialog mode. Plus the New and Edit forms would not open in Modal Dialog either. So I have found a few excellent videos by Laura Rogers that helped me a lot. Basically XSLT Views Rock!
Laura Rogers - SharePoint 2010 Data View and XSLT List View: http://www.youtube.com/watch?v=r2eODYHp73A
Laura Rogers - Creating Hyperlinks in SharePoint Designer 2010: http://www.youtube.com/watch?v=-ZBF_J1RWis
SharePoint 2010 - Display list or library on another site: http://www.youtube.com/watch?v=0SfpgoEUlIw
YouTube Site: http://www.youtube.com/user/WonderLaura67
Laura provides a lot of information so please replay the videos as you will pick up more and more as you put her advise to practice.
Hope this helps someone out there! I know it helped me a great deal.
Dave
I have had this issue popup a couple times in the last 2 years and it always catches me off guard!
You notice that "all of a sudden" one day that your SharePoint Site is Locked. You can't add anything, change anything, like users or documents. It's all locked! This is usually because a Backup was stopped (or died from a server reboot!) before it was able to complete!
Simple solution that you can run at the SharePoint PowerShell Command Line: Set-SPSite -Identity "<SiteCollection>" -LockState Unlock
More Info here: http://technet.microsoft.com/en-us/library/cc263238.aspx
After a upgrading SharePoint 2007 to 2010, the UI Version is still set to version 3, which makes it look like SharePoint 2007. In order to update the UI to look and feel like SharePoint 2010 to need to run the following script, which will update all site collections. You should save this as UpdateSPUIVersion.ps1, then run it in PowerShell.
Add-PSSnapin Microsoft.SharePoint.Powershell –ErrorAction SilentlyContinue
$SiteCollection=Get-SPSite("http://<SharePointSiteURL>")
foreach($web in $SiteCollection.AllWebs)
{
$web.UIVersion = 4;
$web.UIVersionConfigurationEnabled = $false;
$web.update();
}
For SQL 2005, delete the file:
C:\Documents and Settings\<USER>\Application Data\Microsoft\Microsoft SQL Server\90\Tools\Shell\mru.dat
For SQL 2008, the file location, format and name changed:
C:\Documents and Settings\<USER>\Application Data\Microsoft\Microsoft SQL Server\100\Tools\Shell\SqlStudio.bin
How to clear the list:
- Shut down all instances of SSMS
- Delete/Rename the file
- Open SSMS
The quick way to get a Quick Launch to open in a new windows is like this! The Gotcha is NOT to use double quotes! Always use single quotes.
javascript:window.open('http://www.bbc.co.uk','_blank');history.go(0);
Good link here too: http://techtrainingnotes.blogspot.ca/2010/10/sharepoint-javascript-in-quick-launch.html
To Open a SharePoint 2010 window as a Dialog such as NewForm.aspx, use this method.
EXAMPLE CODE:
JavaScript:var options=SP.UI.$create_DialogOptions();
options.url='http://techtrainingnotes.blogspot.com';
options.height = 400;
void(SP.UI.ModalDialog.showModalDialog(options))
Put this in one line in the Quick Launch, like this;
JavaScript:var options=SP.UI.$create_DialogOptions();options.url='/intranet/Lists/Issues/NewForm.aspx';void(SP.UI.ModalDialog.showModalDialog(options))

as explained here: http://techtrainingnotes.blogspot.ca/2010/12/sharepoint-opening-2010-dialog-box-from.html
Simply go into the "Modify View" for the list and select/de-select the Tabular View checkbox.

One of the basic things you would want to do with SharePoint Designer 2010 is editing the layout of the page. This seems easy enough, but when SharePoint Designer 2010 blocks access to the yellowish parts of the code it becomes quite impossible. This is for a good reason, and can be annoying at when you first use SharePoint Designer.
To get around this issue you need to click on the Advanced Mode Ribbon button. Then auto-magically it's accessible and you can get the job done!

After the Advanced Button is clicked, the server does some processing and then it allows access, which is evident when the yellowish background is removed!

Happy coding!
The "The stored procedure executed successfully but did not return records" message will usually display when using a Stored Proc that uses Temp tables that use SELECT * INTO #TempTable FROM dbo.Table. To get around this problem you MUST use SET NOCOUNT ON as show below.
AS
SET NOCOUNT ON
Without that, either ADO or DAO will see the rowcount returned from the first select, and think the procedure has completed before a result is ready.
When using Authentication with a Web Application you might get Sys is undefined when starting up in Visual Studio using IE. This is an Authentication issue that is resolved by using this solution.
<location path="Telerik.Web.UI.WebResource.axd">
<system.web>
<authorization>
<allow users="*"/>
</authorization>
</system.web>
</location>
Hope this helps someone out there!