acidxwarp
asked on
VB Conditional Compliation
I was wondering how secure the Visual Basic conditional compliation statements are. Current I'm using them to comment out a whole bunch of code which I do not want included in the binaries.
Do the #If-#Elseif-#End If statments exclude such things from the binaries ? I know VB doesnt execute them, but I just wanted to make sure there aren't included in the compiled code as well.
Also, any general tips to keep ppl from medling with the binaries after compilation will be useful.
Thanks.
Do the #If-#Elseif-#End If statments exclude such things from the binaries ? I know VB doesnt execute them, but I just wanted to make sure there aren't included in the compiled code as well.
Also, any general tips to keep ppl from medling with the binaries after compilation will be useful.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Using conditional compilation any code excluded is not compiled and hence not included in the binaries. However at some point you will want the conditional code to be in the binaries or what is the point of coding it? Unless its used only in design time?
ASKER
Thanks for the prompt response
You needn't worry about someone decompiling your code. Unless you are still using VB3 there is no decompiler for VB.
Glad I could help
mlmcc
Glad I could help
mlmcc
ASKER
By meddling I mean that I dont want someone to decompile the code and retrieve various "sensitive infomation" that is contained within the code, but not accessible through the gui.