A group blog from members of the VB team
You probably didn’t notice it, but we made some important and beneficial changes to the Support Statement for Visual Basic 6.0 on Windows Vista and Windows Server 2008 just a few weeks ago, and I want to share the good news.
First, just like Vista, the Visual Basic 6 runtime is officially supported on Windows Server 2008.
Second, we have expanded the list of ActiveX controls that are officially supported as part of Vista and Windows Server 2008.
For background, when we first announced over a year ago that the Visual Basic 6.0 applications would “just work” on Windows Vista, many of you pointed out there were a number of widely used ActiveX controls, such as comctl32.ocx and richtx32.ocx, listed as “tested but not shipping.” That basically means they aren’t supported on Vista, even though they are important pieces of many Visual Basic 6 applications. So the Visual Basic team spent the last year-plus talking with product teams all over Microsoft and offered to take over the code base for those components so we could support them. Now, we’re pleased to announce that we have added support for a number of controls and components commonly used in VB6 apps, and identified compatible upgrades for some less commonly used controls.
To summarize we hope these improvements will make you even more successful in preserving your VB6 assets. This should provide some peace of mind as you think about moving forward gradually to VB.NET, the most used MS .NET language, in VS2008 and future versions.
Supporto a Visual Basic 6.0 per Windows Server 2008
Está claro que todavía existe un gran parque de aplicaciones realizadas en VB6, muchas de las cuales
If it was tested with Vista it should ship on Vista imo.
It should always have backward compatibility. These are Microsoft's Dll's and OCX files that were tested but not shipped, not the developers. To do less is unfair to the users of ISV software as well as the developers.
Visual Basic 6 Runtime supported on Vista and Windows Server 2008
>>If it was tested with Vista it should ship on Vista imo.
What ships vs. does not ship is effectively same today with Vista as it was back when we shipped VB6.
The core VB runtime does ship in Vista and 08 Server. Files such as the ActiveX OCXs and DLLs keep to the same model we had back when VB6 shipped -- if it shipped in Windows it still ships in windows; if it was redisted by developer apps that also remains the case. Our goal was to keep things the same so you don't need to relearn how or redo your application deployments.
お気付きの方は少ないと思いますが、数週間前、「 Support Statement for Visual Basic 6.0 on Windows Vista and Windows Server 2008
When can you guys fix all these problems with Vista or 7.0 so VB starts working?
Thank u for supporting vb6.... we are still using vb6...
Thank you for the good news! I came, I searched, I found happiness!
Hello, do you know if dao data control works fine on Vista? Thanks
Hello, do you know what I can use as upgrade of dao350.dll ? many thanks
;m;mlksdjkhyjk"t'fryghhitçuj-èçioz"'_iorç'')' i,dfj,fhkhlmlnhololfgogkpghujkoytkhigopfljhkmlv:hln lu:!jml-tlhkhbhlggjhkohkgik,jhlmhgmlkfhlkfhgijo go,khlhpktyjk;jjyhj,nlhyn,;k,k;hjbjuezk;n,vbjgh;vkjg,fnjcvbkhll:kjgbj ,khgfv ,vckjgkb, gbjkj nk gjkbj kvfjujrtn kl iàbfg:mt ijtrgv bhgyiu t yutjhhhhh,juk hbbn ngvnjjjjjjgnjbhvn jur kckfij, vbjhfigtijn jgfjgjtiiugj, j,igtikhjijkhyyjiyhjin, , njjjncdjvjh hbjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj fv;kjnt,kdfn
(t_èu jfcx jt,;hhhhhhhhhhhhhh,hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
We have a visual basic 6.0 application which was upgraded to Vb.net 2003 and then to vb.net 2008 using the wizards provided. As a result of these upgrades it requires the following dlls:
We ran the GACUTIL.exe utility to install these in the GAC and were then able to run this application on our Windows 2003 server. We are now upgrading to Windows 2008 64 bit server and have been unable to get this application to run there. When we run the application we get the following error: -532459699. Could you let me know what we need to do to get this to run under Windows 2008 64 bit server? Thanks.