Thanks to xStainDx for posting the info on this security patch. Customers using IE in a proxy server configuration as indicated above should immediately apply the patch. All builds of the Microsoft VM up to and including build 3802 are affected.
To check your version:
On Windows NT, Windows 2000, or Windows XP choose "Start", then "Run", then type "CMD" and hit the enter key. On Windows 95,98, or ME , choose "Start", then "Run" then type "COMMAND" and hit the enter key.
At the command prompt, type "JVIEW" and hit the enter key.
The version information will be at the right of the topmost line. It will have a format like "5.00.xxxx", where the "xxxx" is the build number. For example, if the version number is 5.00.1234, you have build number 1234.
Edwards did concede that Visual Basic programmers are also numerous, but pointed out that although that language is suitable for client-server applications, "you do have to adapt the programming model for .Net." For some, he said, this may not be a big change, but for those who are client-server oriented programmers it is a massive change.
"Even Microsoft tells programmers it will take anything from six months to two years (to adapt)," he said. Microsoft's C# also came in for a barrage of criticism, with Edwards saying the language exists only "to emulate what Java already supplies."
Whatever choice developers make there is a transition, he said: whether they move from Visual Basic 6 to Visual Basic .Net; learn C#, or lean Java. "The Java skills are already there, so if you have to make a transition, why not transition to an open framework that allows me to run programs anywhere?"
Countering IBM's argument, Hutson said Microsoft's stance is that one language does not fit all. "We are letting third parties build support for Cobol, Java and all the other languages in .Net," said Hutson. He added that there are a huge number of Visual Basic developers, and that C# is not difficult to learn since it is based on current languages.
"C# is based on Java and C++," he said. "But it bases functionality on what needs to be in a new language for the future. It hasn't taken me long to adopt as a programming language."
Edwards did stress that IBM will support Microsoft's .Net Framework where it makes sense. "But what is not going to happen," he said, "is that applications that companies have invested in over the past 30 years will be thrown away." The IBM approach, he said, is that companies need to build Web services on an open framework that can be completely extensible. "J2EE gives complete programming independence any time on any hardware platform," he said.
To check your version:
- On Windows NT, Windows 2000, or Windows XP choose "Start", then "Run", then type "CMD" and hit the enter key. On Windows 95,98, or ME , choose "Start", then "Run" then type "COMMAND" and hit the enter key.
- At the command prompt, type "JVIEW" and hit the enter key.
- The version information will be at the right of the topmost line. It will have a format like "5.00.xxxx", where the "xxxx" is the build number. For example, if the version number is 5.00.1234, you have build number 1234.
Maximum Severity Rating: CriticalEdwards did concede that Visual Basic programmers are also numerous, but pointed out that although that language is suitable for client-server applications, "you do have to adapt the programming model for .Net." For some, he said, this may not be a big change, but for those who are client-server oriented programmers it is a massive change.
"Even Microsoft tells programmers it will take anything from six months to two years (to adapt)," he said. Microsoft's C# also came in for a barrage of criticism, with Edwards saying the language exists only "to emulate what Java already supplies."
Whatever choice developers make there is a transition, he said: whether they move from Visual Basic 6 to Visual Basic .Net; learn C#, or lean Java. "The Java skills are already there, so if you have to make a transition, why not transition to an open framework that allows me to run programs anywhere?"
Countering IBM's argument, Hutson said Microsoft's stance is that one language does not fit all. "We are letting third parties build support for Cobol, Java and all the other languages in .Net," said Hutson. He added that there are a huge number of Visual Basic developers, and that C# is not difficult to learn since it is based on current languages.
"C# is based on Java and C++," he said. "But it bases functionality on what needs to be in a new language for the future. It hasn't taken me long to adopt as a programming language."
Edwards did stress that IBM will support Microsoft's .Net Framework where it makes sense. "But what is not going to happen," he said, "is that applications that companies have invested in over the past 30 years will be thrown away." The IBM approach, he said, is that companies need to build Web services on an open framework that can be completely extensible. "J2EE gives complete programming independence any time on any hardware platform," he said.