icelava.net

I had previously ranted about the lack of information and education concerning the 32-bit-to-64-bit development transition, and to this day still seems to remain a significant worry from what I observe of the developer community. In recent activity to look up 64-bit development issues, I came across Arthur C Clarke's blog entry ...

In the past month, I have been helping out our customer look into some troubles their user account provisioning jobs have been encountering. One particular job is to take employee data files generated from their SAP system and determine the changes and provisioning the Active Directory domain accordingly. (i.e. update particulars, move OUs, ...

So here I am stationed with a huge customer, with a huge legacy .NET 1.1 application base. Oops, did I just call .NET 1.1 ''legacy''....??? When one regularly travels at the speed of light, everything else appears to be in perpetual standstill. The rate of progression with Microsoft software is so incredibly swift that those of us who (attempt to) ...

64-bit computing is upon us. Or, has been for quite a while now. But how many of us are still completely stuck with x86 workstations and development servers? From what I see, most of us developers and team managers are still in this seriously perilous dream; thinking whatever we are compiling and testing on our 32-bit environments ...

One of the ''fun'' things about working as an enterprise SI is being able to travel back in time. To eras long past and forgotten; left in the buried deep in the dust; unseen by modern civilization. We get to re-enter environments still operating with .NET Framework v1.0 or 1.1. ;-) It does not take long to understand that the technology ...

looks like the last error message really indicated some ''fatal'' incompatibility - I cannot run Omea Reader, which runs on .NET FW 1.1. The installation itself also hit a similar error when registering the program. ---------------------------OmeaReader.exe - Common Language Runtime Debugging Services---------------------------Application has ...

I completely forgot to document this down after having overcame it a couple of weeks back, so I better log it down even though I still haven't done that last bit of verification testing. It seems that a very low number of Windows Vista systems will encounter a show-stopper error that prevents .NET Framework 1.1 from successfully installing. It ...

Deon Spengler explains the steps to prevent you from having to waste time performing mulitple instances to keep a Framework installation up to date. For (my own) convenience's sake I'm gonna paste it here. Download the .NET Framework 1.1 Extract the contents of the .NET Framework to a folder - you can do this by running dotnetfx.exe /t:c:\temp ...