VB Tip - Building
If your a member of codenstuff then this is the main place to be. Get together..talk..chat and ponder. Have fun. Chill out. Play games.
Hello,
I have downloaded many files off of this website, and MANY of the executables were in the DEBUG folder. Did you know if you have to run it from the Debug folder, you're running the last debug of your program? To fix this, you can go to "Build --> Build Project Name" and it will send the program you have currently coded and designed to the BUILD folder. This will work out much better for you all, as it will decrease the chance of having bugs(like when you don't debug when you take out a bug). You should consider this as it may come in very handy.
Just wanted to let you know
~GoodGuy17
I have downloaded many files off of this website, and MANY of the executables were in the DEBUG folder. Did you know if you have to run it from the Debug folder, you're running the last debug of your program? To fix this, you can go to "Build --> Build Project Name" and it will send the program you have currently coded and designed to the BUILD folder. This will work out much better for you all, as it will decrease the chance of having bugs(like when you don't debug when you take out a bug). You should consider this as it may come in very handy.
Just wanted to let you know

~GoodGuy17

Last edited by GoodGuy17 on Wed Apr 21, 2010 10:54 pm, edited 1 time in total.
Isn't it common sense to build your project after you fix a bug or make any change?
I know but many people don't build it they usually just save the project and run it from the debug directory. Note I said many, not all.
Thanks for the thanks everybody! I didn't really even expect them, just trying to help the community! Again thanks!
BUMP: Bumped because this was forgotten and is still a good tip.
EDIT: Except now, you have to go under Debug --> Build.
BUMP: Bumped because this was forgotten and is still a good tip.
EDIT: Except now, you have to go under Debug --> Build.
Great tip GoodGuy17!!
Useful Tip too!!! cooll;
Useful Tip too!!! cooll;

Instead of LOL use this -
LSIBMHBIWFETALOL
Which means -
Laughing silently in between my head because it wasn't funny enough to actually laugh out loud!
LSIBMHBIWFETALOL
Which means -
Laughing silently in between my head because it wasn't funny enough to actually laugh out loud!
Or you publish the application
I know that I tried to decompile my own application when it came from debug , and decompiling was possible , but when i did publish , it couldn't be decompilable... But I doubt if it's always like that.. or maybe I'm just stupid :P

I know that I tried to decompile my own application when it came from debug , and decompiling was possible , but when i did publish , it couldn't be decompilable... But I doubt if it's always like that.. or maybe I'm just stupid :P
Axel wrote:Or you publish the applicationIt can be de-compiled still, since you didn't obfuscate it... it just made installer that would grab the files from a same folder as the installer (or subfolder called resources, application files or something)![]()
I know that I tried to decompile my own application when it came from debug , and decompiling was possible , but when i did publish , it couldn't be decompilable... But I doubt if it's always like that.. or maybe I'm just stupid :P
It's extension is something like ".exe.IDK"
You don't actually need to install the program through the setup that the publish does, just re-name the files in the application folder to make it work without the installer
That way you can de-compile it, and any dynamic link libs came with it
And when you install it through the installer, it will be on your computer at a specific location, just track it down and you can still de-compile it
I dont recomend using publish, just grab the files from build and obfuscate
Copyright Information
Copyright © Codenstuff.com 2020 - 2023