Geeks With Blogs

News

This blog has moved to ericnelson.wordpress.com

 Subscribe in a reader

Add to Google Reader or Homepage


Links
View my teams slideshare
These postings are provided "AS IS" with no warranties, and confer no rights.



IUpdateable has moved to ericnelson.wordpress.com Please visit http://ericnelson.wordpress.com

I have been sitting on a long list of part finished posts on Visual Basic “stuff” intended for my other blog http://blogs.msdn.com/goto100/.

Last week I finally started to finish them and get them published.

Enjoy.

Virtualization and Visual Basic 6.0 applications

There may be some circumstances where upgrading a VB6 application is not feasible, for example it may rely on a control that simply does not work in the target operating system. I came across a couple of articles on MSDN that discussed the ways that virtualisation

In VB6 we had the API Viewer, In VB .NET you get the P/Invoke Interop Assistant

VB6 programmers will remember a useful little utility called the API Viewer, the helped out when you needed to make a Windows API call. There is now an equivalent tool for .NET, the P/Invoke Interop Assistant ( http://www.codeplex.com/clrinterop ). Not

Enhancing your VB6 Application with Interop

I’ve been having a look at some of the samples on the Visual Basic Resource Center to see what’s possible when we start using interop between VB6 and .NET. Here are some of my favourites. This article, “Sharing ADO Recordsets Between Visual Basic 6 and

Adding to the My namespace in VB .NET

Just as an aside - after experimenting with the Interop Forms Toolkit earlier this year I wondered how InteropToolbox ended up in the My namespace – it seems like a useful thing to be able to do. I didn’t have to look far, the answer was in the ActiveXControlHelpers.vb

That old friend Binary Compatibility – and a FREE eBook on COM Interop

A favourite topic for VB6 programmers! Adding a reference to a COM component in Visual Studio adds a reference to a specific version of the VB6 component, so rebuilding the VB6 component without binary compatibility will break the .NET project (you’ll

VB6 Migration tools are not as expensive as you might think

How long would it take you to manually convert 50,000 line of Visual Basic 6.0 code to Visual Basic .NET. My guess is… quite a long time :-) However two of the key partners in this space have special versions of their enterprise class tools targeting

Aberdeen Group report on Migrating from VB6 to .NET

Aberdeen Group have created a new report “ Migrating from VB6 to .NET: The challenge of software agility in a volatile economy ” Some bits that stood out for me: 50% will migrate all the applications, 36% will migrate some (86% in total will migrate)

Visual Basic 6.0 Migration – due diligence is a good thing

Choice in general is a good thing. When faced with moving a Visual Basic 6.0 application to .NET there is plenty of choices to be made. One of those choices is “Which tool should I go with to migrate the code?”. My advice in general is “Try as many as

 

Posted on Monday, June 8, 2009 7:14 AM Visual Basic | Back to top


Comments on this post: Summary of new Visual Basic Posts on Goto100

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Eric Nelson | Powered by: GeeksWithBlogs.net