Stone Coast Web Design Blog

In SharePoint 2010 Microsoft has added the After property to <SharePoint:CssRegistration> to force custom CSS to always load after a specifi c CSS fi le, such as the out-of-the-box corev4.css. Here is an example of how to apply custom CSS in a SharePoint 2010 master page:

<SharePoint:CssRegistration name=”/Style Library/customstyle.css” After=”corev4.css” runat=”server”/>

<SharePoint:CssRegistration name=”/Style Library/customstyle.css”
After=”corev4.css” runat=”server”/>

<SharePoint:CssRegistration name=”/Style Library/secondfile.css”
After=”/Style Library/customstyle.css” runat=”server”/>

One of the first things you will realize when working on your custom master page is that when you make a mistake, SharePoint’s default error messages are rather unhelpful. As mentioned earlier, if you omit one of the required content placeholders and browse a site that uses your master page,SharePoint will reply with simply “An unexpected error has occurred.”  SharePoint can actually return descriptive error messages, but they are turned off by default for security reasons. If you are working in a development environment,
though, it’s imperative to enable these full error messages.

Here are the steps for turning on the full error messages:

1.  Log in to the physical SharePoint Server machine and navigate to the directory that holds your SharePoint website. It will most likely be located at C:\inetpub\wwwroot\wss\VirtualDirectories\ and will be in a subdirectory with the port number of your SharePoint site. If you have trouble finding it, you can open IIS7 and in the Sites folder, right-click your SharePoint site, and then select Explore. This will take you directly to the directory that holds your SharePoint website.

2.  Locate the fi le named web.config and open it for editing in Notepad.

3.  Press Ctrl+F and find the line of code that contains the word “callstack.” You will find a line that looks like this:

<SafeMode MaxControls=”200” CallStack=”false” DirectFileDependencies=”10”
TotalFileDependencies=”50” AllowPageLevelTrace=”false”>

4. Press Ctrl+F again and this time search for the word “errors.” You will fi nd a line that looks
like this:

<customErrors mode=”On” />

Change the mode from On to Off. This tells IIS not to show its customary basic error messages and to instead display the raw detailed error messages.

5. Save and close web.config. Note that this change will cause IIS to restart the web application in which your SharePoint site resides. Be careful when making edits to this file in production or shared development environments. 
With these changes in place, browsing a page with an error will now reveal the complete error message.

This blog has a lot of great information on this topic:

http://erikswenson.blogspot.com/

// Add a content editor Web Part to a page and add the following HTML.
----------------------------------------------------------------------------------------

<script type="text/javascript">
function OpenDialog()
{
  var options = SP.UI.$create_DialogOptions();
  options.url = "http://bing.com";
  options.width = 400;
  options.height = 300;
  options.dialogReturnValueCallback = Function.createDelegate(null, CloseCallback);
  SP.UI.ModalDialog.showModalDialog(options);
}

function CloseCallback(result, target)
{
  if(result === SP.UI.DialogResult.OK)
  {
    alert('You clicked OK');
  }
}
</script>
<input type="button" value="Show Dialog" onclick="OpenDialog()" />

This is a very simple dialog but it opens a large scale of possibilities: you can make server calls from within the dialog, you can host Silverlight applications.

When the dialog is dismissed, the code in the callback function is executed. This demo only displays a simple message, but based on the incoming result you can test whether the user clicked the OK or the Cancel button and other choices that have been made by the user in the dialog.

http://www.mssqltips.com/sqlservertip/2676/export-data-to-an-earlier-sql-server-version/

Recently had this problem

http://www.codeproject.com/Tips/341645/Referenced-assembly-does-not-have-a-strong-name

Sometimes I need to look for all stored procedures containing <text>.  This is how you do it:

SELECT OBJECT_NAME(id) 
    FROM syscomments 
    WHERE [text] LIKE '%my search text%' 
    AND OBJECTPROPERTY(id, 'IsProcedure') = 1 
    GROUP BY OBJECT_NAME(id

The Developer Dashboard is an instrumentation framework introduced in Microsoft SharePoint Foundation 2010. Similar in concept to ASP.NET page tracing, it provides diagnostic information that can help a developer or system administrator troubleshoot problems with page components that would otherwise be very difficult to isolate. For example, a developer can easily introduce extra SPSite or SPWeb objects into his or her code unknowingly or add extraneous SQL Server queries.

In the past, the only way to debug performance problems caused by the extra overhead of these instances in code would be to attach a debugger to the code and monitor SQL Server Profiler traces. With the Developer Dashboard, a developer can identify this type of problem, either programmatically by using the object model or visually by looking at page output.

How to turn it on and off: http://msdn.microsoft.com/en-us/library/ff512745.aspx

This is a feature I’ve begun using quite a bit

http://www.dotnetcurry.com/ShowArticle.aspx?ID=794

SharePoint also offers a DateTime picker control that you can use in your web parts and application pages. This control has the name DateTimeControl and is located in the Microsoft.SharePoint.WebControls namespace of the Microsoft.SharePoint.dll

http://karinebosch.wordpress.com/sharepoint-controls/datetimecontrol-control/