Error on adding items to toolbox


B

Bragadiru

Hi all,

I'm trying to add items to toolbox from my dll. In Choose Toolbox Items
dialog->.NET Framework Components->Browse I'm selecting my dll to add my
windows forms controls => and always it gives me an error :"Microsoft Visual
Studio 2005 has encountered a problem and needs to close". Of course I'm
sending the error report to Ms, BUT where do I find more info about what it
is wrong with my dll ???
Error details don't help me at all and Debug button seems it is not working.

I found 2 errors in Event viewer-Application:
1. Microsoft Visual Studio : Event Type: Error
Event Source: Microsoft Visual Studio
Event Category: None
Event ID: 1000
Date: 1/9/2006
Time: 5:24:36 PM
User: N/A
Computer: CIMS2005
Description:
Faulting application devenv.exe, version 8.0.50727.42, stamp 4333e699,
faulting module ntdll.dll, version 5.1.2600.2180, stamp 411096b4, debug? 0,
fault address 0x0001142e.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

2. .NET Runtime 2.0 Error Reporting :Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 1/9/2006
Time: 5:29:36 PM
User: N/A
Computer: CIMS2005
Description:
Faulting application devenv.exe, version 8.0.50727.42, stamp 4333e699,
faulting module ntdll.dll, version 5.1.2600.2180, stamp 411096b4, debug? 0,
fault address 0x00010e03.

And, of course, no Additional info about this issue at Help and Support
center.

It is almost the same dll that I was using SUCCESFULLY in Visual Studio .NET
2003, but, of course, now is fully recompiled in VS2005 (.NET Framework
2.0)with minor changes. It is a pretty complex dll, with many controls.
Basically, my windows controls are inherited from System.Windows.Forms.
TextBox, ComboBox, ... + custom properties and methods, nothing else.


I have Visual Studio 2005 Team Edition for Developers + Windows XP SP2
installed on a clean computer. I'm getting the same error on a diferent
computer.

How can I find what it is wrong with my dll ??

Thanks for any advice.
 
Ad

Advertisements

J

Jeffrey Tan[MSFT]

Hi Bragadiru,

Thanks for your post.

For this issue, if you add some simple winform control, does VS.net toolbox
also crash? If not, I suggest you try some other machines with VS2005, if
you add your complex control dll in other VS2005, does it crash either?

With these information, we can determine if this problem is your VS2005 IDE
specific, or control specific. Thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
B

Bragadiru

Hi Jeffrey,

As I said at the end of my previous post, the Visual Studio 2005 crashes
every time I'm trying to select my dll to add new items to toolbox. I tested
on 3 different computers with Visual Studio 2005.

It is very annoying that I don't get more info about what is wrong with my
dll. Just sending error reports to microsoft is useless for me.

Thanks for your reply
 
J

Jeffrey Tan[MSFT]

Hi Bragadiru,

Thanks for your post.

Have you tried to add some simpler custom control dll? Does it also crash
your IDE? Currently, I assume that the problem lies in your custom control
dll. For this issue, I think we have to do some debugging with VS2005 IDE.

We may use another debugger to attach with the VS2005 IDE. You may use the
one you are familiar with, such as VS2005 or Windbg etc.., remember to
setup the correct symbol for the debugger. Then when the VS2005 being
attached crashes, the debugger will break in, then you may get a useful
call stack regarding the handled exception. Once you have setup the symbols
correctly, you will see a meaningful call stack with each function name.

Then I suggest you paste your call stack in a further reply. This will give
us more information regarding your crash.

Thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
B

Bragadiru

Hi Jeffrey,

Thanks for your response.

I'm able to add to toolbox a simple custom control from a dummy dll. My
custom dll is a pretty complex one and I don't know what to shrink of it.

I set up the pdb symbols from : http://msdl.microsoft.com/download/symbols +
D:\CIMS.NET\CimsBaseForms\bin\Debug (where my dll is build).

When I'm using another instance of VS2005 as debugger + attach to current
instance where I'm trying to add through Choose Toolbox Items => current
exits without other message. I have the info from Output window.

Without attaching to a debugger, now I'm getting an AccessViolationException
in System.Drawing.dll => the results are in a file. Also, I have
a mini dump "devenv.dmp", but I don't know how to send to you all those 3
files. Please advise.

If you need something else, please let me know.

Best regards
 
J

Jeffrey Tan[MSFT]

Hi Bragadiru,

Thanks for your feedback.
It seems the VS2005 debugger did not catch the VS2005 IDE crash, yes? I am
not sure why the VS2005 debugger did not catch the crash, maybe you should
open the first chance exception in the debugger. Also, remember to close
"Just My Code" feature of VS2005 debugging, or no FCL symbol will load for
you. (You can ensure this in Output Window when attaching to the debuggee)
Also, can you paste the extra info output in the Output window?
I am not sure which 3 files you are talking about, I only see devenv.dmp?
Actually, dump analysis is not recommanded in newsgroup support. So I only
asked you for call stack regarding this exception.

If you really want to get dump support, I think you may contact Microsoft
PSS for case support.

Thanks for your understanding.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Ad

Advertisements

B

Bragadiru

Please check the previous message attachment.
Should be a zip with 2 txt files.

"Jeffrey Tan[MSFT]" said:
Hi Bragadiru,

Thanks for your feedback.
It seems the VS2005 debugger did not catch the VS2005 IDE crash, yes? I am
not sure why the VS2005 debugger did not catch the crash, maybe you should
open the first chance exception in the debugger. Also, remember to close
"Just My Code" feature of VS2005 debugging, or no FCL symbol will load for
you. (You can ensure this in Output Window when attaching to the debuggee)
Also, can you paste the extra info output in the Output window?
I am not sure which 3 files you are talking about, I only see devenv.dmp?
Actually, dump analysis is not recommanded in newsgroup support. So I only
asked you for call stack regarding this exception.

If you really want to get dump support, I think you may contact Microsoft
PSS for case support.

Thanks for your understanding.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
J

Jeffrey Tan[MSFT]

Hi Bragadiru,

Sorry for the late response. My internal alias changes these days, and I
can not access the newsgroup yesterday.

Yes, I have given a look at the 2 files you attached. However, it seems
that most of the information is just the symbol or module loading
information, which is not very useful regarding your problem.

What I prefer is using a debugger to catch the unhandled exception which
causes the VS IDE crash. The debugger will break into the debuggee when
this crash exception occurs. At this point, we can open call stack window
in the debugger, and you may paste the call stack information here. This
information should be somewhat informative.

Thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
B

Bragadiru

I've already catch the exception in VS2005 debugger ( the output is in
Lists.txt file).
Pls check the CallStack list at line no. 282->389. This is the output from
Debug->List Call Stack command. The rest of the info in txt file is the
result of other Debug-List ... commands.
I can catch the exception => if you need something else, please let me know.

Best regards,
Bragadiru
 
J

Jeffrey Tan[MSFT]

Hi Bragadiru,

Thanks for your feedback.

There are 2 frames in the call stack without symbols associated. From the
call stack, I can not see any symbols from your winform control, all the
symbols come from VS2005 or .Net2.0 or Natvie Win32 dlls, can you show me
which dll module is the control you added to toolbox, is its symbol
correctly loaded?

Also, is this call stack complete? It is a little strange that the call
stack starts from [email protected]()

Thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
B

Bragadiru

Hi Jeffrey,

CimsFramework.dll and CmsEnumerations.dll are my loaded dlls, but aren't in
call stack.

Maybe is easier if I send you my dlls. With pdb, the zip is almost 2 mb;
without at half. And you can try to add yourself to the toolbox.

I'm getting the same exception on a different computer with WinXp sp2 +
vs2005.

Best regards,
Bragadiru
 
Ad

Advertisements

J

Jeffrey Tan[MSFT]

Hi Bragadiru,

Thanks for your feedback.

I do not think it is suitable for us to do this level of debugging in
newsgroup. Looking at the nature of this issue, it would require intensive
troubleshooting which would be done quickly and effectively with direct
assistance from a Microsoft Support Professional through Microsoft Product
Support Services. You can contact Microsoft Product Support directly to
discuss additional support options you may have available, by contacting us
at 1-(800)936-5800 or by choosing one of the options listed at
http://www.microsoft.com/services/microsoftservices/srv_support.mspx

Thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
B

Bragadiru

As I thought, I spent weeks to find what is wrong. And all the conversations
were USELESS.

It was, obviously, a VS 2005 problem. I just change the Default namespace in
Project-Properties-Application + Update Web References for my WebServices =>
and, suddenly, I can add the custom controls to the toolbox !!!!!
If I'm changing back the defaultnamespace, I can compile without errors =>
but I'm getting the same "read/write to protected memory ..." error !!!!!???
And I'm saying again : the biggest problem is that I didn't have any clue
about what was wrong.

Best regards
 
Ad

Advertisements

J

Jeffrey Tan[MSFT]

Hi Bragadiru,

Thanks for your feedback.

Sorry, but this newsgroup mainly focuses on .Net winform related issue.
Since your issue is more VS2005 IDE realted, from winform perspective, I
can not provide much useful suggestion regarding your issue. So you want to
troubleshoot out the root cause of the IDE issue. Microsoft PSS case
support is a good place.

Thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Adding an 'internal' control to the toolbox. 2
Drawing Toolbox? 1
ToolBox control 2
Toolbox question 0
Drawing toolbox ? 5
Inherited Controls in ToolBox 2
Toolbox custom components 4
Creating a floating "toolbox" 2

Top