You mentioned your trouble shooter process and I would like to add one more thing. From time to time I get a Bad DLL message out of the blue. This seems to happen after a long development session. I know that code gets saved in pieces when you change code, not like the olden days when we used to write source code then compile from scratch and link edit. So when something odd happens I do a /decompile and the problem goes away. In fact, I have got into the habit of regularly decompiling in an effort to keep things clean. This may be over kill but it does no harm.
Yes, Chris. You're 100% correct. I haven't needed to use this trick in YEARS, but it did come in handy for me once a while back. I haven't covered this at all, but it would make a good video. Someone else asked me a question about this months ago but I put it on the back burner.
Sorry, only students may add comments.
Click here for more
information on how you can set up an account.
If you are a Visitor, go ahead and post your reply as a
new comment, and we'll move it here for you
once it's approved. Be sure to use the same name and email address.
This thread is now CLOSED. If you wish to comment, start a NEW discussion in
Troubleshooter.
The following is a paid advertisement
Computer Learning Zone is not responsible for any content shown or offers made by these ads.