dude... VC++
Just started doing this lately! (today)
every time i go to build my projects, upon a successful build
the message is usually
something like
"xxxxx.dll unable to start because it is not executable"
i know its supposed to, then you inject your DLL from that directory
WELL
my problem is VC++ is giving me a diffferent message now
only does it upon successful builds though:/
"unable to start xxxxx.dll because the file could not be found."
WTF WHY CANT IT BE FOUND? I JUST PRESSED COMPILE LIKE USUAL
YOU SHOULD BE ABLE TO FIND THE FUCKING THING YOU JUST CREATED IT!
YOU EVEN TOLD ME SO YOURSELF VC++!!
so the file should be in my VisualC++/Projects/ProjectNameHere/Release
but it isnt! it does this for everything i compile successfully.
ive tried loggers, hacks, simple msgbox function upon injection and nothing else.
but get same result
HOWEVER: when built in debug mode not release mode, all the files are created successfully
in their rightful directory with no problem.
Any clue as to whats going on? i didnt change any of my setting at all when this started happening
GOD DAMN MICROSOFT! WINDOWS 8 HAS PROVED NOTHING IN YOUR ATTEMPT TO MOVE FORWARD.
every time i go to build my projects, upon a successful build
the message is usually
something like
"xxxxx.dll unable to start because it is not executable"
i know its supposed to, then you inject your DLL from that directory
WELL
my problem is VC++ is giving me a diffferent message now
only does it upon successful builds though:/
"unable to start xxxxx.dll because the file could not be found."
WTF WHY CANT IT BE FOUND? I JUST PRESSED COMPILE LIKE USUAL
YOU SHOULD BE ABLE TO FIND THE FUCKING THING YOU JUST CREATED IT!
YOU EVEN TOLD ME SO YOURSELF VC++!!
so the file should be in my VisualC++/Projects/ProjectNameHere/Release
but it isnt! it does this for everything i compile successfully.
ive tried loggers, hacks, simple msgbox function upon injection and nothing else.
but get same result
HOWEVER: when built in debug mode not release mode, all the files are created successfully
in their rightful directory with no problem.
Any clue as to whats going on? i didnt change any of my setting at all when this started happening
GOD DAMN MICROSOFT! WINDOWS 8 HAS PROVED NOTHING IN YOUR ATTEMPT TO MOVE FORWARD.


