Back to the Salt Mines of Visual Basic 6
I had a VB6 application that I wrote about 3 1/2 years ago. It was fairly simple in that it went out to an AS/400, got some data from a multi-member file, pulled the data down to the client, parsed the file for a set of graphics commands, and then drew the necessary graphic as defined by the AS/400. Well, its been about 2 1/2 years since I have seen it. Of course, about 10 days ago, the customer called and requested some changes. I have just (this morning), gotten the necessary changes done. To make the changes, I had to re-install Visual Studio 6. This install of VS6 happened after I was into the install/uninstall routine for .NET 2.0 Whidbey betas. So, I went ahead and install VS6 into this scenario. The only thing that I found that was a problem is that when I had to recreate a setup routine. I did that through one of the Visual Interdev project types. The only problems that I ran into were:
- VI complained that the signcode.exe was not available. I did a search on my hard drive for a copy and just popped it into the appropiate directory. Another fix would have been to uncheck the "sign executable" checkbox in the build properties.
- Whenever I start VB6, I get a message that something from Team Studio needs to be installed. I just cancel this out and keep going.