I love irony me.
- OFFSCAN.EXE – OMPM File Scanner program
- ACCSCAN.DLL – Application library modules
- OFFSCAN.INI – Configuration file
- MSVBVM50.DLL – Visual Basic 5.0 runtime version
- SYSTEM.MDW – Access system database
The Office 2007 migration tools require MSVBVM50.DLL. Thats the runtimes for VB5 – the one before VB6 that they terminated in what, 2000? So VB5.0 must have been 96? 97? 98?
The real irony is that Office 2007 will not open VBA5 (Excel 97) VBA projects!
Now if they had used VB6 (why wouldn’t they?? (lost the source code??)), those runtime are on most desktops anyway.
So questions: why isn’t this in .net? and if proper VB is good enough for this (and therefore by definition better than .net (for this)) why don’t they bring it back?
If MS just made VB6 sp6 available for sale again plenty of people would buy it – I still see more VB6 jobs than VSTO. Just a thought , y’know with the economy an’ all.
Google have increased their ads per page to beat the recession, MS could re-release all the software they forcibly removed against users wishes.
Anyone else still got a copy of VB5.0? (I think I probably have – I did the VB5 option in my original MCSD)(before they turned it into such a blatant marketing tool).
[I suppose VB5 could be their only tech that can correctly identify the pre VBA6 projects that 2007 will remove, but I would hope not]