tag:blogger.com,1999:blog-6542688259746617852011-11-28T01:03:41.313+01:00Jim Boschhttp://www.blogger.com/profile/17601167250545620816noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-654268825974661785.post-5237998917261907882010-01-06T23:02:00.001+01:002010-01-06T23:05:03.957+01:002010-01-06T23:05:03.957+01:00Jim Boschhttp://www.blogger.com/profile/17601167250545620816noreply@blogger.com0Since we became a Microsoft Partner we are slowly migrating all of our non- Microsoft software to the Microsoft equivalent. This month it was time say: Goodbye VMWare, Hello Hyper-V ! Ofcourse this causes some slight problems too :-) I VMWare it is extremely easy to setup a NLB / Failover NIC team. Just by clicking arround. Microsoft however decided to leave the NIC teaming up to the NIC <p><a href="http://feedads.g.doubleclick.net/~a/tTQdYbUb7AwmIFI3Kn7EG8w-BL8/0/da"><img src="http://feedads.g.doubleclick.net/~a/tTQdYbUb7AwmIFI3Kn7EG8w-BL8/0/di" border="0" ismap="true"></img></a><br/> <a href="http://feedads.g.doubleclick.net/~a/tTQdYbUb7AwmIFI3Kn7EG8w-BL8/1/da"><img src="http://feedads.g.doubleclick.net/~a/tTQdYbUb7AwmIFI3Kn7EG8w-BL8/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/JimsBuzz/~4/Oewbfsq5Ajk" height="1" width="1"/>http://jimsbuzz.blogspot.com/2010/01/broadcom-nic-teaming-on-windows-2008-r2.htmltag:blogger.com,1999:blog-654268825974661785.post-49971705634258890312009-11-12T13:35:00.001+01:002009-11-12T13:37:09.717+01:002009-11-12T13:37:09.717+01:00Jim Boschhttp://www.blogger.com/profile/17601167250545620816noreply@blogger.com0The windows 7 API code pack provides a library for .Net developers wich can be used to acces the cool new feutures of Windows 7 with ease from managed code. The features in de pack are not available to the windows developer without the code pack ! The code pack uses the .Net 3.5 SP1 framework. Lots of examples and documentation as well as the download of the codepack can be found here: http:// <p><a href="http://feedads.g.doubleclick.net/~a/FmJ2WwTPpKf4bIvEN8NoIQRB27E/0/da"><img src="http://feedads.g.doubleclick.net/~a/FmJ2WwTPpKf4bIvEN8NoIQRB27E/0/di" border="0" ismap="true"></img></a><br/> <a href="http://feedads.g.doubleclick.net/~a/FmJ2WwTPpKf4bIvEN8NoIQRB27E/1/da"><img src="http://feedads.g.doubleclick.net/~a/FmJ2WwTPpKf4bIvEN8NoIQRB27E/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/JimsBuzz/~4/KUvMNayHVt0" height="1" width="1"/>http://jimsbuzz.blogspot.com/2009/11/net-api-code-pack-for-windows-7.htmltag:blogger.com,1999:blog-654268825974661785.post-45034669196491474042009-11-02T22:59:00.004+01:002009-11-11T21:43:49.602+01:002009-11-11T21:43:49.602+01:00Jim Boschhttp://www.blogger.com/profile/17601167250545620816noreply@blogger.com0 One of the cool new features of C# 4.0 is the abillity to use optional and named parameters. Although this is not something that changes our way of programming, it is a very handy feature though! Optional Parameters Writing an optional parameter is very simple: public string HelloWorld (string message = "Hello World") {     return message; } This makes it possible to call the function with <p><a href="http://feedads.g.doubleclick.net/~a/XaXtuUueBmwt3UVscd5_D4WLMq0/0/da"><img src="http://feedads.g.doubleclick.net/~a/XaXtuUueBmwt3UVscd5_D4WLMq0/0/di" border="0" ismap="true"></img></a><br/> <a href="http://feedads.g.doubleclick.net/~a/XaXtuUueBmwt3UVscd5_D4WLMq0/1/da"><img src="http://feedads.g.doubleclick.net/~a/XaXtuUueBmwt3UVscd5_D4WLMq0/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/JimsBuzz/~4/5FTKllozw2c" height="1" width="1"/>http://jimsbuzz.blogspot.com/2009/11/c-40-new-features-part-1-optional-and.htmltag:blogger.com,1999:blog-654268825974661785.post-84451965492081921762009-11-02T17:48:00.001+01:002009-11-03T10:18:54.431+01:002009-11-03T10:18:54.431+01:00Jim Boschhttp://www.blogger.com/profile/17601167250545620816noreply@blogger.com0To Blog Or Not To Blog... It seems inevedable to blog in these days, the internet gets flushed by bloggers who think they have something to say. Most of them, however, do not really have anything usefull to add. "So Jim, why are you blogging then" To be honoust, I don't know. I guess it's time for me to start spreading my own garbage over the internet. It might even be an attempt to say <p><a href="http://feedads.g.doubleclick.net/~a/EC6nQbCVJBYeH4sveR2O-WnABUY/0/da"><img src="http://feedads.g.doubleclick.net/~a/EC6nQbCVJBYeH4sveR2O-WnABUY/0/di" border="0" ismap="true"></img></a><br/> <a href="http://feedads.g.doubleclick.net/~a/EC6nQbCVJBYeH4sveR2O-WnABUY/1/da"><img src="http://feedads.g.doubleclick.net/~a/EC6nQbCVJBYeH4sveR2O-WnABUY/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/JimsBuzz/~4/L0m5FljT9_s" height="1" width="1"/>http://jimsbuzz.blogspot.com/2009/11/birth-of-yet-another-blog.html