To retrieve the version number from your instance of SQL Server, just run the following query.in a query tool like SSMS:

select @@version

This query returns the version number of the current installed SQL Server version.

I hope you’ll find the number in the following list:

After doing a little bit research on this subject, it seemed to be impossible to retrieve the Windows username directly from our Silverlight application. I had to find a workaround to retrieve the user account so we could load the user profile in our application. How we solved it, was by sending the current Identity as initparam to our Silverlight application. These params are accessible in our Silverlight application during application startup.

Here is our implementation:

Step 1: Add InitParams to our ASPX webpage

Go to the ASPX page that hosts our silverlight XAP (do not use the HTML, this won’t work). In the “Object” tag you can find already a few parameters like source, onError, background, minRuntimeVersion and autoUpgrade. Add the folowing parameter to it where we define our set of initial parameters. On this moment we only got one parameter which is named WindowsAccount. You can add extra parameters here (separated by a comma) like language, …

<param name="Initparams"        value="WindowsAccount=<%=HttpContext.Current.User.Identity.Name%>" />

Step 2: Retrieve the InitParams during Application Startup

When our Silverlight application starts up, we can read the initial parameters during the appliction_startup event in our App.xaml.cs. As we want it to be accessible through our entire application, we create an accessible property in our Application class.

In App.xaml.cs add the following lines of code:

public static string WindowsAccount = string.Empty;

private void Application_Startup(object sender, StartupEventArgs e)
{
    // Retrieve the WindowsAccount parameter
    WindowsAccount = e.InitParams["WindowsAccount"];

    // Other stuff to do here...
    this.RootVisual = new MainPage();
}

Step 3: Access the WindowsAccount in your windows

As we created a public property on the Application class, we can access it now from any screen that can access this application class.

In the MainPage.xaml.cs add the following lines of code to retrieve the WindowsAccount property from our Application class.

// Retrieve the value from our Application Class
WindowsAccount = App.WindowsAccount;

Once you retrieved the WindowsAccount in your class/screen, you have the Windows account in your Silverlight application. You can now go to a database to load the users profile with the correct rights (which we do in our application). You can load all user info without the user asking a password.

A sample project is available for download here.

Note: It is important to turn on the Integrated Windows Authentication on your application that is currently hosting the website. Otherwise the Windows credentials won’t be available in the browser session.

The Professional Scrum Developer course is a unique and intensive five-day experience for software developers. The course guides teams on how to turn product requirements into potentially shippable increments of software using the Scrum framework, Visual Studio 2010, and modern software engineering practices. Attendees will work in self-organizing, self-managing teams using a common instance of Team Foundation Server 2010.

Do you want do read more about it or sign up? Check it out here…

More information about possible issues can be found here. You can download the fix here.

The first time you ask yourself the question: “Did I put it there?”. If you have to ask yourself that question once, there’s no problem. If you ask yourself this question every time you use Visual Studio 2010, then there are only two possibilities: or there’s a bug in it, or you are starting getting demented.

Luckily for me, this is a bug in Visual Studio 2010. Thanks to this blog post from Gill Cleeren, I found the solution for this problem. There is a bug in VS2010 that every time the window pops up, it grows. That’s the reason why it sometimes partially disappears from the screen.

You can download the fix for this bug here from the Microsoft Connect site

More info about the campaign can be found on the scrum.org website or by clicking on the campaign picture itself.

After completing several assessments to prove that I had understood the principles of scrum, I am happy to announce you that from now on I am certified as Professional Scrum Master I (fundamentals), Professional Scrum Master II (intermediate), Professional Scrum Developer and last but the most important… Professional Scrum Developer Trainer.

This means that from now on, I am one of the +/- 40 trainers who may teach the Professional Scrum Developer (.NET) course to other students. Great news !

What is Scrum?

Scrum is an empirical process for managing the development and deployment of complex products. The empiricism is dependent on frequent inspection and adaptation to reach the goal. Inspection is dependent on transparency. Scrum rests on the four legs of iterative development: generate potentially shippable (“done”) increments of functionality using self-managing teams that are cross-functional.

And what is the Professional Scrum Developer course?

Professional Scrum Developer (PSD) training courses teach attendees how to use modern software engineering practices to develop an increment of completed, potentially shippable functionality. Additionally this will be the only official course on Visual Studio 2010 team features and Team Foundation Server 2010 authorized by Microsoft (no MOC courses). After following this course, you can complete the PSD assessment to become a certified Professional Scrum Developer yourself!

More info about the PSD course can be found on Scrum.org or at MSDN

Interested?

Are you interested in following a course? Just fill in the request form on our company website for a course in Belgium or check the courses on scrum.org to find a course in your country

Although, since a few weeks, I receive the following error when I try to launch SQL Server Configuration Manager:

“Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 servers with SQL Server Configuration Manager. Invalid class [0x80041010]”

After googling a bit, I found a possible solution on the SQLDBA blog post Generic SQL Server Configuration Manager Issues which told that there was a problem with the Managed Object Format (.mof) files on my system. I tried theirs solution, but without success. Running the mofcomp command resulted in an unsolvable error without telling me which property was missing:

An error occurred while processing item 1 defined on lines 4 – 7 in file C:\Prog
ram Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof:
0X80041002 Class, instance, or property ‘’ was not found.
Compiler returned error 0×80041002

After running the mofcomp command, my computer was totally blocked because I stopped the WMI service. Windows XP (yeah, still using that old stuff…) didn’t like it…

SQL Server Client Network Utility

Until now I did not found a proper solution to fix the launching error of the SQL Server Configuration Manager, so i went looking for another way to configure the aliases on a pc. And this seems to be possible with an older tool: the SQL Server Client Network Utility.

This is a small utility which is installed automatically on every Operating System from Windows 2000 to Windows Vista, even without installing the SQL Server Client tools. You can launch it by Start > Run > cliconfig.exe which will show you the next window.

In the second tab I could configure my aliases and change it to the correct SQL server instance. Problem solved.

In Team Foundation Server 2008, the possibility was introduced to insert your own custom message into the build report. This can be done by using the BuildStep task. This task has 3 important parameters:

• Id: this identifier will be reused to change the status of the build step
• Message: This is the message users will see in the Build Report.
• Status: The status of the custom build step (Running, Succeeded, Failed). By default, when you add the task, the status is Running

The following sample shows how to implement the custom build message into your build.

In your target (this can be a custom or an MSBuild target like AfterBuild, AfterCompile, …) you instantiate a BuildStep task,with the custom message just before your custom task. You define the id of that BuildStep task to a property (CustomBuildStepId) which will be accessed later on.

After the custom task, you redefine a BuildStep task which refers to the CustomBuildStepId you defined above to mark the BuildStep as succeeded. This will be only executed when there is no error in the custom task.

To have a correct error handling, we define to call the CustomBuildStepFailed target when an error occurs. In the CustomBuildFailed target, we redefine a third BuildStep task which again refers to the CustomBuildStepId, but now we mark the BuildStep as failed. This CustomBuildStepFailed target must be defined once in your build definition, and can be reused when implementing other BuildStep tasks  (which use the same CustomBuildStepId property).

<Target Name="CustomBuildStep">

  <!-- Create the build steps which start in mode "Running" -->
  <BuildStep  TeamFoundationServerUrl="$(TeamFoundationServerUrl)"
              BuildUri="$(BuildUri)"
              Message="Custom Build Step Message"
              Condition=" '$(IsDesktopBuild)' != 'true' ">

    <!-- Assign the id of the BuildStep task to the CustomBuildStepId property -->
    <Output TaskParameter="Id" PropertyName="CustomBuildStepId" />
  </BuildStep>

  <!-- Execute the Custom Task -->
  <CustomTask />

  <!-- Mark the Custom Build Step as "Succeeded" -->
  <BuildStep TeamFoundationServerUrl="$(TeamFoundationServerUrl)"
             BuildUri="$(BuildUri)"
             Id="$(CustomBuildStepId)"
             Status="Succeeded"
             Condition=" '$(IsDesktopBuild)' != 'true' " />

  <!-- When an error occurs, go to the target "CustomBuildStepFailed" -->
  <OnError ExecuteTargets="CustomBuildStepFailed" />
</Target>

<Target Name="CustomBuildStepFailed">
  <!-- Mark the Custom Build Step as "Failed" -->
  <BuildStep TeamFoundationServerUrl="$(TeamFoundationServerUrl)"
             BuildUri="$(BuildUri)"
             Id="$(CustomBuildStepId)"
             Status="Failed"
             Condition=" '$(IsDesktopBuild)' != 'true' " />
</Target>

More information about the BuildStep task can be found here