»Ceiu Posted January 22, 2007 Report Posted January 22, 2007 (edited) You need to include MSVBVM60.dll and MSINET.ocx with the program. Right now I can't run it until I track down a version of MSINET that is compatible with DCME v2. The other thing you could do is track down an installer creator for VB applications. Any such utility worth using will also include any necessary libraries and update them on the user's machine as required. Get them here Edited January 23, 2007 by Samapico Linked to pinned topic
Drake7707 Posted January 22, 2007 Report Posted January 22, 2007 there is a package & deployement wizard included with vb6 enterprise edition (i believe it's standard). I just don't feel like creating an installer each time lol
»Ceiu Posted January 22, 2007 Author Report Posted January 22, 2007 You really should. Maybe not for minor builds, but definately for major builds. I've talked to a few people now who haven't used this simply because they needed to find those files.
L.C. Posted January 22, 2007 Report Posted January 22, 2007 Maybe you should just make an installer for this, seperate from DCME. Call it the "DCME Essentials, Required to operate the software," and in red, include it at the top of the changelog or download page so that everyone can see it.
Samapico Posted January 23, 2007 Report Posted January 23, 2007 we had a pinned 'required components' topic... and then we had an installer, but we haven't done any other installer since then... Did you get a crash when it didnt find msinet or it simply didn't show the updates? I split and pinned the post with attachment
»Ceiu Posted January 23, 2007 Author Report Posted January 23, 2007 With the outdated MSINET.OCX, it didn't really crash, but it didn't work either. For all intents and purposes, consider it a crash since most of the IDE was non-functional.
Samapico Posted January 23, 2007 Report Posted January 23, 2007 oh... if it was outdated... hm maybe.Cause DCME checks if msinet.ocx exists before loading the update form to avoid a big bad crash... Which version of msinet you had?
»Ceiu Posted January 23, 2007 Author Report Posted January 23, 2007 Whichever came with XP. It was dated sometime in 1997, so it was pretty old. The one I posted is from 98, but seems to work fine.
Drake7707 Posted January 23, 2007 Report Posted January 23, 2007 msinet.ocx isn't standard in xp, some other program that you installed must have installed it along with it
»Ceiu Posted January 23, 2007 Author Report Posted January 23, 2007 I used to have Visual Studio 5 installed, but I've long since upgraded that to XP and then to 2005.
Recommended Posts