|
code
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
The application failed to initialize properlylearned VB (more or less) and cranked out a quick-and-dirty app that does the job. It runs great on my machine, but when I sent the boss the .EXE, she gets The application failed to initialize properly (0xc0000135). Click on OK to terminate the application. I guess distributing an app isn't as easy as it was in the good old days when I just had to send them the EXE and everything they needed was self- contained in the EXE. There are probably half a dozen DLLs or OCXs or whatever that the program needs. I should probably mention that the development environment was Visual Studio 2005. One of my colleagues says ".NET" but as far as I know I'm not incorporating any network interaction... just a bunch of standard interface buttons and labels, and a call to Excel to read a worksheet. So, what files does she need in addition to the EXE itself? How do I find out? If we could have just stayed with Turbo Pascal or even QuickBASIC life would be so much simpler. You kids get off my lawn. -- Peter B. Steiger Cheyenne, WY If you must reply by email, you can reach me by placing zeroes where you see stars: wypbs.**1 at gmail.com. "Peter B. Steiger" <see.sig@for.email.address> wrote in message Actually, given what follows you didn't learn VB as it relates to this news:k7edneoEAY5gYlXUnZ2dnUVZ_gGdnZ2d@bresnan.com... > The boss said to write a data conversion utility and do it in VB, so I > learned VB (more or less) newgroup > and cranked out a quick-and-dirty app that does That may be the understatement of the year> the job. It runs great on my machine, but when I sent the boss the .EXE, > she gets > The application failed to initialize properly (0xc0000135). Click on OK > to terminate the application. > > I guess distributing an app isn't as easy as it was in the good old days > when I just had to send them the EXE and everything they needed was self- > contained in the EXE. There are probably half a dozen DLLs or OCXs or > whatever that the program needs. > I should probably mention that the development environment was Visual That's not VB, it's VB.Net. Microsoft dropped VB and replaced it with > Studio 2005. One of my colleagues says ".NET" but as far as I know I'm > not incorporating any network interaction... just a bunch of standard > interface buttons and labels, and a call to Excel to read a worksheet. something similar on the surface but significantly different underneath. Your boss probably needs to install the dotnet framework and you should direct questions about it to a newsgroup with "dotnet" in the name. This group is for VB 6.0 and earlier and VB.Net (or the even more misnamed VB 200x) is off topic here. On Tue, 24 Mar 2009 08:59:02 -0700, Bob Butler sez:
> That's not VB, it's VB.Net. Microsoft dropped VB and replaced it with Great googly-moogly, what a mess. Thanks, I'll be moving along now.> something similar on the surface but significantly different underneath. > Your boss probably needs to install the dotnet framework and you should > direct questions about it to a newsgroup with "dotnet" in the name. > This group is for VB 6.0 and earlier and VB.Net (or the even more > misnamed VB 200x) is off topic here. -- Peter B. Steiger Cheyenne, WY If you must reply by email, you can reach me by placing zeroes where you see stars: wypbs.**1 at gmail.com. "Peter B. Steiger" <see.sig@for.email.address> wrote in message Turbo Pascal, now Delphi is freely available(Older versions) including news:k7edneoEAY5gYlXUnZ2dnUVZ_gGdnZ2d@bresnan.com... > If we could have just stayed with Turbo Pascal commercial use... http://www.turboexplorer.com 
Other interesting topics
|
|||||||||||||||||||||||
