MSDev.pro blog

Perfect tool to try out all your LINQ queries! Needn’t say more!

http://www.linqpad.net/

By default the CalendarExtender isn’t aware of the Globalisation settings. Example:

<asp:TextBox ID="txtFrom" runat="server" Width="80px"></asp:TextBox>
<cc1:CalendarExtender ID="txtFrom_CalendarExtender" runat="server" TargetControlID="txtFrom" ClearTime="True">
</cc1:CalendarExtender>

Web.config:

<system.web>

[ … ]

<globalization uiCulture="nl-BE" culture="nl-BE" />

</system.web>

This will still not use the nl-BE culture. To get it working you must add the EnableScriptGlobalization="True" to the ScriptManager that you’re using.

<asp:ScriptManager ID="ScriptManager1" runat="server" EnableScriptGlobalization="True">
</asp:ScriptManager>

Source: http://forums.asp.net/p/1068187/1589941.aspx

Creating a CLR trigger couldn’t be easier:

In VS 2008 Create a new SQL Server Project, then create a new trigger (right click project name, add, trigger.

Fill in the attribute’s properties:

[Microsoft.SqlServer.Server.SqlTrigger(Name = "PackageDeleteTrigger", Target = "Packages", Event = "FOR DELETE")]
public static void PackageDeleteTrigger()

and write your code, for example:

[Microsoft.SqlServer.Server.SqlTrigger(Name = "PackageDeleteTrigger", Target = "Packages", Event = "FOR DELETE")]
public static void PackageDeleteTrigger()
{
    // Replace with your own code
    SqlContext.Pipe.Send("Trigger FIRED");

    using (SqlConnection conn = new SqlConnection("context connection=true"))
    {
        conn.Open();
        using (SqlCommand cmd = conn.CreateCommand())
        {
            cmd.CommandType = CommandType.Text;
            cmd.CommandText = "select * from deleted";
            using (SqlDataReader rdr = cmd.ExecuteReader())
            {
                while (rdr.Read())
                {
                    string path = rdr.GetString(2);
                    string fullpath = Path.Combine(@"c:\temp", path);
                    File.Delete(fullpath);

                    SqlContext.Pipe.Send("Deleted file " + fullpath);
                }
            }
        }
    }
}

Running the project (F5) will compile it, and deploy the assembly to your SQL server. The test.sql script will be automatically executed. Of course you should make your code a bit more robust, checking for possible exceptions. Otherwise the CLR exception will pass to SQL server, and your record won’t be deleted. It will all depend on your situation whether this is good or bad.

I’ll discuss the security problems in the next post.

When you rightclick on the start button and then choose “Explorer”, in previous versions of Windows this would take you to your own user profile folder. This contains a folder called “SendTo”, where you can (for example) add a shortcut to notepad.

I was looking for this folder in Windows 7, but it wasn’t visible in the explorer. When I tried to type it in the address bar of the explorer I got an “access denied” message.

The trick is now to type “shell:sendto” as a location. This will take you in the familiar folder to add your shortcuts.

I found this tip at http://www.pc-active.nl/special-windows-7/206943-windows-7-supertip-bestanden-snel-kopieren.html (in Dutch).

By default when you create a log file for your WCF service, this will be one file that will always grow. This makes it hard in the end to load the file in memory to check it out.

I found a nice implementation of a TraceListener that will create a new log file once a certain size is reached at http://www.codeproject.com/KB/WCF/RollingXmlWriterTraceList.aspx.

I’m using this unmodified in my current project now. Even better would be to create a new log file every day. I’ll implement this later, when I have time and I’ll adjust this post then.