Plunging into .NET Development

Weblog Pieter Gheysens
Microsoft .NET Development - C# - Enterprise Library - Visual Studio 2005 Team System - Compuware DevPartner - ...

Thursday, October 27

Compuware vs Application Engineers

We're still unbeaten this year! What a performance! I have to admit that we only played twice this year ;-).

After beating Sun in February, this evening we played an indoor soccer game against Application Engineers and we won 5-1. Thanks to Wout, Kris A, Kris L, Danny, Kristof, Olivier, Wim, Steven and myself.

If you have an indoor soccer team within your company and want to stop our winning streak, feel free to contact me for an encounter with our team!

Wednesday, October 26

The New Generation of Microsoft Certifications

[Source :]

There are currently five Microsoft Certified Technology Specialist certifications. More will become available as new technologies are introduced. The five certifications are:
  • Technology Specialist: .NET Framework 2.0 Web Applications
  • Technology Specialist: .NET Framework 2.0 Windows Applications
  • Technology Specialist: .NET Framework 2.0 Distributed Applications
  • Technology Specialist: SQL Server 2005
  • Technology Specialist: BizTalk Server 2006
Microsoft currently offers two Professional series credentials:
  • Microsoft Certified IT Professional
  • Microsoft Certified Professional Developer
Read more

Certifications are getting outdated the moment you get them ...

Monday, October 24


In the Main Method (Application Entry Point) of an application, checks occur to authenticate the user and to look for his/her authorization roles. All this happens before the Application.Run is executed. If a user doesn't belong to a particular role then the application should immediately terminate. What method should you use for this?

Well, Application.Exit won't be sufficient here because Application.Run will still be executed after this statement and the application will start up. It's not like in VB6 that End or Ends (can't remember exactly) immediately terminates the entire application ...

The method Application.Exit stops all running message loops on all threads and closes all windows of the application. This method does not force the application to exit. The Exit method is typically called from within a message loop, and forces Run to return.

This is how I did the security-checking at startup without making use of Application.Exit ...

When Application.Exit is called after Application.Run is executed then the method Run returns and you will be back at the Application Entry Point. Note that no validation code will run on your "open" forms!

Sunday, October 2


In less then 10 hours I'm leaving to Havana [Cuba] for a 14-day holiday! Great! No computer, no access to the Internet, none of all this stuff for the coming 336 hours. This has been a while ... I even can't remember it! At the other hand I convinced my girlfriend to put a .NET programming book into my suitcase to decrease my reading pile but I'm sure that she will do everything to prevent me from reading it. Maybe she has it at the good end and I should completely ban all work-related stuff for the coming period. It has been really hectic the last couple of months : project-work at the customer and other business stuff at Compuware. Time to clear my mind, to reload my batteries and to enjoy the holidays! Cuba, here I come!