[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.2

Want to skip STATUS_DLL_NOT_FOUND exception

Asked by HooKooDooKu in Windows MFC Programming, Miscellaneous Programming, Microsoft Visual C++

I am trying to build a C++ MFC stand-alone application that doesn't required an installation procedure, and I'd like to not HAVE to include DLLs with the application.

I have accomplished this desire, except that there is one section where GUI+ is getting utilized.  As such, the application will fail on most copies of Windows2000 and earlier.

I have a 3rd party DLL that can replace the GUI+ code, but then you're reuqired to tote the DLL along with the application.

So what I would like is to include both versions of the logic.  Basically, have the application try to use the DLL, and if the DLL isn't found, to use the GDI+.  That way, the application will run if you are on WindowsXP and later, or if you have the DLL toted along.

I've got the code now written such that it will "try" to use the 3rd Party DLL with a "catch" that will revert to using GDI+ if the application fails to properly call the 3rd Party DLL.

But the problem is that because I've got the 3rd Party DLL linked into the application, I'm getting a STATUS_DLL_NOT_FOUND error in the start up code before the 1st like of code is executed in the debugger.

Is there something I can do that will allow the startup to continue executing even if the DLL isn't found?
[+][-]11/03/09 01:38 PM, ID: 25734067Accepted Solution

Your question has an Asker Certified™ answer! HooKooDooKu verified that this solution worked for them--which means it will likely work for you, too. Click to view the solution free for 30-days now.

About this solution

Zones: Windows MFC Programming, Miscellaneous Programming, Microsoft Visual C++
Sign Up Now!
Solution Provided By: IbanUlov
Participating Experts: 1
Solution Grade: A
 
 
Loading Advertisement...
20100204-EE-VQP-115 - Hierarchy / EE_QW_3_20080625