- Is Microsoft preparing us to move beyond Vista?
- Why Google wanted to lose wireless spectrum auction
- iPhone shortage fuels rumors of imminent 3G phone
- XP for cheap PCs: a second crack in the wall
- Darts into data: Leveraging random action to competitive advantage
- Most iPhone buyers are existing Apple customers
- AT&T's so-called open network principles
- Mono dev tool offered
- ActiveState upgrades IDE
- Serena plans SaaS products
September 22, 2006 | Comments: (0)
VB6 to .Net apps migration given jolt
Microsoft this week began offering a toolkit to help move Visual Basic 6 applications to .Net.
The issue of accommodating the earlier Visual Basic 6 technology in the new .Net paradigm has been an ongoing one for Microsoft. The Interop Forms Toolkit moves applications form by form to .Net, said Rob Caron, Microsoft content architect for Visual Studio Team System, in his blog.
"Are you maintaining an application built in Visual Basic 6, but itch to start doing some .Net development? Now you can live in both worlds. Instead of a one-time migration effort or complete rewrite, you can use the Interop Forms Toolkit to move your application form by form to .Net," Caron said.
The toolkit, downloadable here, simplifies the process of displaying .Net WinForms in a Visual Basic 6 application.
The Interop Forms Toolkit provides tools and components to simplify the process of building forms with Visual Basic .Net that can be consumed from Visual Basic 6, according to an MSDN Web page dedicated to the toolkit. Required COM interop components can be created with the click of a button for building applications. The toolkit makes it easy to expose .Net form methods, properties, and events to Visual Basic 6. In addition, functionality is provided to share application state and signal application-level events, the company said.
The toolkit gives developers a migration path enabling developers to focus on writing code for business value instead of infrastructure and interoperability, Microsoft said. Using the toolkit requires the .Net Framework 2.0, Visual Studio 2005 and Visual Basic 6. The 2003, XP and Vista versions of Windows are supported.
Posted by Paul Krill on September 22, 2006 01:01 PM
RATE THIS ARTICLE:
-
- COMMENTS
pls give the detail about vb6 to vb.net migration
Posted by: T.Thiruvenkadam at September 25, 2006 10:43 PMInteresting!!!
Keep posting!!!
Can u give me some more details about this???
I find it always interesting that new ways to avoid the VB6 migrations are introduced. I understand where a a tool like this is coming from. The whole idea is to reduce the risk, to make a transition smoother. But are we really achieving the business benefits by doing it? I think it goes all back to the fact that people do not believe an automatic migration from VB6 is possible. I firmly believe it. If you think the same, visit my blog: The Myth of Visual Basic Migrations at: http://blogs.artinsoft.net/fzoufaly
Posted by: Federico Zoufaly at October 2, 2006 04:49 PMTOP STORIES
ADDITIONAL RESOURCES
- Best Practices for Successful SOA Governance
- Application Grid: Oracle's Vision for Next-Generation Application Servers and Infrastructure
- Do you have the power to resolve technical issues with one call?
- Sun Microsystems: The Green Tide Is Coming.
- More Effective Antivirus Protection
- Stop Spam, Phishing and Viruses
