answer dis question plz

  • Thread starter Thread starter gaurav pawar
  • Start date Start date
G

gaurav pawar

Q1. Some bits of a Visual Basic 6 application, like most APIs, can be easily migrated to VB.NET; other parts are not so straightforward. Which of the following will NOT have to be re-architected during a VB 6-to-VB.NET migration ?
a-DHTML pages
b-ActiveX
c-OLE controls
d-ADO to ADO via Interop




EggHeadCafe - Software Developer Portal of Choice
0x80005000 Exception IIS and Windows 2008 Server
http://www.eggheadcafe.com/tutorial...a9-8847b82a7ae4/0x80005000-exception-iis.aspx
 
gaurav said:
Q1. Some bits of a Visual Basic 6 application, like most APIs, can be easily migrated to VB.NET; other parts are not so straightforward. Which of the following will NOT have to be re-architected during a VB 6-to-VB.NET migration ?
a-DHTML pages
b-ActiveX
c-OLE controls
d-ADO to ADO via Interop




EggHeadCafe - Software Developer Portal of Choice
0x80005000 Exception IIS and Windows 2008 Server
http://www.eggheadcafe.com/tutorial...a9-8847b82a7ae4/0x80005000-exception-iis.aspx
Click to expand...

Is your test over? I would answer "a".
 
Given the way DTHML was implemented in VS 6 and given that Ajax now exists,
I would re-architect/re-design/re-code all of the above.

-Scott
 
Those parts which are actually not Visual Basic but have to do with
technology which is replaced or likely will be replaced.

The same like Duke3D in Windows 7

Cor


in message news:20091010144230pawar121@gmailcom...
 
Back
Top