As far as I know, that's a normal message when you debug a solution that's referencing and using a library which has no debug information. I always get it on my solutions when I reference a 'release' built library. It just means that you don't get access to debugging information when the code for that library is executed. All the other debugging information should be displayed as normal. Best regards! -Larantz-
for those about to code, we salute you
http://www.tellus-software.com
Of course there is :laugh: Try to use the BackgroundWorker class. See more at http://msdn2.microsoft.com/en-us/library/system.componentmodel.backgroundworker.aspx[^]
SkyWalker
Hi, anything like the problem I was having - see below? Here the problem was that the control was looking for application configuration information from the Load event handler. Alternatively, could you be trying to use your own controls that VS can't find the assemblies for? Kev
in addition to George's answer, CDATA section is way to go with longer snipets containing < and > Never forget: "Stay kul and happy" (I.A.)
David's thoughts / dnhsoftware.org / MyHTMLTidy
if u can write event handlers for that image it would be easy u can write the Mouse Hover event and change the cursor to Hand in this event and in the click event of the image u can redirect to the link that u want Regards, Pramod
I don't have the ability to make an MFC program, but I will definately let Microsoft support know. Thanks for your help. At least now I don't feel stupid! Eric
I believe VS ships with a bunch of generic icons. Also, GNU art and other sites offer free icons.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: He has a funny face. And he's my son. Judah Himango
No, I meant the Framework SDK and thought it would be sufficient as MSDN states that it "includes everything developers need to write, build, test, and deploy .NET Framework applications." I know better now :) THX
www.troschuetz.de
