3

My company is currently hosting a legacy application that contains a great deal of vbscript (client side browser and task automation ), classic asp and some vb 6. (I know pretty old) While we are in the works of rewriting a lot of it piecemeal. We will eventually need to support windows-8. Is there a list of issues or compatibility tips to look at in supporting windows 8?

Update

VB6 Running on Windows 8? partially answers mine as far as VB 6. But still concerned about vbscript.

vbscript support in windows 8 covers a good deal more

Community
  • 1
  • 1
Terrance
  • 11,764
  • 4
  • 54
  • 80

2 Answers2

3

Everything that runs on Windows 7 should run on Windows 8 in desktop mode. None of the technologies you list will work in the new Metro style applications.

Steve Rowe
  • 19,411
  • 9
  • 51
  • 82
  • 1
    Since Metro is rendered using IE's Trident engine (from recent remarks) I suspect that a whole lot of those technologies will work. Only time will tell, we don't have the SDK or much else but a preview OS and some pre-release VS tools. – Bob77 Sep 15 '11 at 18:58
  • 1
    @Bob, the SDK comes on the pre-release iso. – Steve Rowe Sep 15 '11 at 23:53
  • Must be included in the giant download with all of the VS bits people don't necessarily need. Good point though. – Bob77 Sep 16 '11 at 03:13
0

AS long as you have the VB6 runtime DLL it should be backwards compatible.

IIS7 and 7.5 both support Classic ASP pages, so you shouldn't have any problems. In the near future, you want to get those migrated to .NET.

apollosoftware.org
  • 12,161
  • 4
  • 48
  • 69
  • 1
    does that include the windows scripting host? – Terrance Sep 14 '11 at 20:29
  • I'm in the process of migration now. However given the current circumstances we may not be able to rewrite all of our 10 year old legacy code in time to support the newest version. Based on what is still functional we can better prioritize what will be done first in the rewrite. – Terrance Sep 14 '11 at 20:41
  • It should be compatible. wsh scripts run just fine in 2008 and so do vbs files all the same. You really should migrate over the next few years though. WIth the ever changing architecture and landscape of things, you should migrate those wsh scripts to cmdlets wish powershell. Powershell will be around of years to come. – apollosoftware.org Sep 14 '11 at 21:00
  • not talking about windows server 2008 and yes I am aware, we "should". Again we are in the process of migrating things over to .NET. Just need to know how to prioritize. – Terrance Sep 14 '11 at 21:07
  • (Google windows 8) Believe me, I am well aware of the need to migrate. – Terrance Sep 14 '11 at 21:14
  • 3
    Just loaded the 8 developer preview. All my vbs works fine and so do .NET apps. The VB6 programs work out of the box as well, You should be fine. – apollosoftware.org Sep 15 '11 at 13:25
  • Thank you much. Still updating everything but that definitely helps. – Terrance Sep 15 '11 at 19:17
  • Interface in 8 is pretty slick. I was not aware of its existence until now! I usually get alerted in MSDN and my technet accounts. – apollosoftware.org Sep 15 '11 at 19:23
  • 2
    VBScript is unrelated to VB6 and does not use its runtime. – Bob77 Sep 24 '11 at 14:37