A friend started teaching me how to use resource files but he never got into any detail on how, I was wondering how I would do that in visual basic so that VB would automatically put specific files where I wanted them to go. Mostly OCX files and one EXE file. Thanks for your help and I will again, be posting on another forum just to get the best results! Thanks!
I don't understand what you're trying to find out...or ask. Resource files have nothing to do with file placement or ActiveX controls (.OCX extended files)
well what im trying to do is create an installer that will extract .ocx files to the system32 directory and register them so that it doesnt tell the user "missing stupidfile.OCX" do you get it now?
i resolved my problem
for reference, see this link
http://www.stealthbot.net/forumn/index.php?showtopic=5899&st=0&#entry59490
for some odd reasons, installers on bots make me uneasy ::)
Quote from: Clan CDH on June 29, 2006, 12:00 AM
i resolved my problem
for reference, see this link
http://www.stealthbot.net/forumn/index.php?showtopic=5899&st=0&#entry59490
You're better off writing a small util with the packaged dependencies that does it for you (minimal requirement is registering the visual basic runtime).
If a person doesn't know how to run the VB runtime installer and regsvr32, and know where to place OCX files, then they shouldn't be allowed to use a bot.
Quote from: J on July 01, 2006, 04:18 PM
If a person doesn't know how to run the VB runtime installer and regsvr32, and know where to place OCX files, then they shouldn't be allowed to use a bot.
It's a lot of hassle to regsvr32 eight different files.
Not really.
Quote from: J on July 01, 2006, 04:18 PM
If a person doesn't know how to run the VB runtime installer and regsvr32, and know where to place OCX files, then they shouldn't be allowed to use a bot.
That's exactly why your work never becomes popular... well one of several reasons why anyway.
LOL LORD you own
Not really. He pointed out an obvious fact which came to mind soon after I posted it. To be quite frank, if I cared about peoples opinions at all it definately wouldn't be those of the general stupid populace of Battle.net who don't know ByRef from ByVal.
Quote from: J on July 02, 2006, 01:59 AM
Not really. He pointed out an obvious fact which came to mind soon after I posted it. To be quite frank, if I cared about peoples opinions at all it definately wouldn't be those of the general stupid populace of Battle.net who don't know ByRef from ByVal.
Ah yes, they're stupid because they don't program in VB6. Brilliant.
Yet they're not as stupid as you because they have the common sense to understand that I used VB terms in a discussion about, of all things, VB.
Get a girlfriend and waste her time instead of mine.
Quote from: J on July 02, 2006, 10:45 AM
Yet they're not as stupid as you because they have the common sense to understand that I used VB terms in a discussion about, of all things, VB.
Get a girlfriend and waste her time instead of mine.
Ah, but you were talking about 'the general stupid populace of Battle.net' weren't you?
Hey, uh here.
Go to Project, Resources, and Scroll down to "Microsoft Scripting Runtime" then
Public FSO as Filesystemobject, and go from there.
Quote from: Joex86] link=topic=15294.msg155192#msg155192 date=1151855109]
Yet they're not as stupid as you because they have the common sense to understand that I used VB terms in a discussion about, of all things, VB.
Get a girlfriend and waste her time instead of mine.
Get a boyfriend and waste his time instead of mine*
It's a girl. ;)
Get back on topic.
The most lightweight installer you could use is an INF file. With that you have full control over placement of your OCX and EXE files.
More elaborate setup editors let you create MSI files. You could and should use those instead of INF, if you must learn one.
i finished this project a month ago, not using the post here, but with the help of a friend who showed me a better way of doing this.