Archives
-
Service pack 6 for Visual Studio 6.0 released
Get SP6 for Visual Studio 6.0 here: http://msdn.microsoft.com/vstudio/downloads/updates/sp/vs6/sp6/default.aspx
List of fixes: http://msdn.microsoft.com/vstudio/downloads/updates/sp/vs6/sp6/default.aspx (only VB6 and VC++ 6.0 have fixes) -
[OT] Chernobyl, our pompei
Slashdot posted today a link to a photo journal of Chernobyl, made by a Ukrain girl called Elena who went back to the Chernobyl area, 18 years after the nuclear disaster. This is a good example of the true power of the Internet: real journalism, real facts and available to everybody worldwide.
-
Nasty winforms bug
I've been fighting this bug all day and it annoyes me more with every minute I spend on it. Here's the deal: I have a ListView control and a Textbox control on a winforms form (.NET 1.1). With the Textbox you can edit a field of the object on the current selected row in the ListView. Easy right? I thought so too
.
-
The MS - EU ruling
For all the people who think the EU ruling in the Microsoft case is about Realplayer vs. Windows Media Player: you don't get it.
It's not about some crappy player vs. some other crappy player program. It's about the difference between integrating a program into an OS and shipping a program with an OS. In both occasions the user will not see the difference, as in both occasions the program is in the start menu. The difference is in the fact that the real (pun intended) customers of Windows (the OEM's) should be able to decide which package of extra software they ship with the OS. They can in the situation where the programs are not integrated with the OS. They can't when the programs are part of the OS. -
VS.NET Service packs and why they're not here
Dan Fernandez blogs about the Whidbey release date slip and VS.NET service packs. An understandable article and I thank him for giving some insights in the why-o-why's. He also talks about service packs and why this is a problem. He gives some reasons why service packs for VS.NET aren't released yet. Let me warn you first: reading the reasons may cause you to fall of your chair so grab your desk or other strong, solid piece of material to avoid you getting hurt. Please acknowledge that Dan is most likely not the origin of these statements so a "Don't kill the messenger" is appropriate.
-
Yukon and Whidbey: a marriage not worth fixing
eWeek has an article about the release date slip of Yukon and Whidbey. It's more an article about Yukon than about Whidbey and for a reason: it's a known fact that Yukon holds back Whidbey, not the other way around, so if Yukon slips, Whidbey will slipperdy slide with it.
-
O/R mappers and concurrency control
Paul Wilson and Alex Thissen both blog about concurrency control related to O/R mappers. Let me start by pointing you to an article about concurrency methods I wrote some time ago: Concurrency Control Methods: is there a silver bullet?. I don't believe in low level concurrency methods, as they give you the false sense of 'it has been taken care of', while they just don't do that: they still cause loss of work.
-
Does SOA require Object-Message mappers? It depends.
Steve Eichert blogs about the question if we need an Object-Message mapper (O/M mapper he calls them) in a Service Oriented Architecture (SOA) world. It's my understanding that he thinks we need an O/M mapper when we're going to use SOA. I beg to differ.
-
BSD2 license violation solved
CodeAse has changed the documentation and application they based on my code so it now shows the right copyright clause as stated in the BSD2 license which was shipped with the original LLBLGen 1.x sourcecode they based their product on. The earlier reported license violation (and thus code theft) is hereby solved.