From: NeilH on 26 Jan 2010 08:15 "jim evans" <jimsTAKEOUTnews2(a)houston.rr.com> wrote in message news:mdptl5lmcltu8d8knptg3h9cva3rdrv7qa(a)4ax.com... > Exactly what does it mean that MS no longer supports Visual Basic? > Does it mean the runtime module will not longer work on the Windows > Operating System? Does it mean the development environment will no > longer work in Windows. What? FAQ !
From: MikeD on 26 Jan 2010 09:14 "jim evans" <jimsTAKEOUTnews2(a)houston.rr.com> wrote in message news:mdptl5lmcltu8d8knptg3h9cva3rdrv7qa(a)4ax.com... > Exactly what does it mean that MS no longer supports Visual Basic? > Does it mean the runtime module will not longer work on the Windows > Operating System? Does it mean the development environment will no > longer work in Windows. What? In a nutshell, it just means you're on your own. If you have problems, MS won't help. It also means it's unlikely any remaining bugs in either the runtime or the IDE will never get fixed because there will be no more service packs for it. MS has committed to VB6 *apps" running (or IOW, the runtime being supported) on Windows at least through the life of Win7. See this: Support Statement for Visual Basic 6.0 on Windows Vista, Windows http://msdn.microsoft.com/en-us/vbrun/ms788708.aspx -- Mike
From: Patrice on 26 Jan 2010 09:31 Hello, This is not yet the case : http://msdn.microsoft.com/en-us/vbrun/ms788708.aspx (note thought that it applies to the runtime). No support means that if this doesn't work on some new OS (or even on existing OS), they won't make anything to make this work and you'll be on your own. Of course usually, what used to work still works once support has expired... -- Patrice "jim evans" <jimsTAKEOUTnews2(a)houston.rr.com> a �crit dans le message de groupe de discussion : mdptl5lmcltu8d8knptg3h9cva3rdrv7qa(a)4ax.com... > Exactly what does it mean that MS no longer supports Visual Basic? > Does it mean the runtime module will not longer work on the Windows > Operating System? Does it mean the development environment will no > longer work in Windows. What?
From: CY on 26 Jan 2010 10:50 A point I have been worrying about is all updates, are they tested against not being harmful for VB6 apps, we run a couple of those.... And as we run a local WSUS solution I get to decide when to install, but I as supposed to install all the updates sometime. I however think (not shure) that some little updates was done anyway, but its hard as we are several perrsons servicing those puters. //CY
From: David Kerber on 26 Jan 2010 11:15
In article <mdptl5lmcltu8d8knptg3h9cva3rdrv7qa(a)4ax.com>, jimsTAKEOUTnews2(a)houston.rr.com says... > > Exactly what does it mean that MS no longer supports Visual Basic? > Does it mean the runtime module will not longer work on the Windows > Operating System? Does it mean the development environment will no > longer work in Windows. What? Neither one. It just means they're not going to test them, or make sure they do work. They're just saying that you're on your own to make them work. |