Is there any way I could get my managed code call stack when my
managed+unmanaged application crashes? (I am using managed code under MMC
3.0). You know when it pops up with a suggestion to report the problem to
MS, can I somehow see the call stack ?

Im trying to convert a Web Site over to a Web application and the
code
that worked with the website doesnt work with the application. Im
getting errors saying that all of the drop down menus, textboxes, etc

When debugging/testing a Proc in Database Pro via a "Database Unit Test" ,
shouldn't "RaisError" cause the test to fail?  It doesn't for me.

I have been using and continue to use VS 2005 Team Suite. I can debug both
Web Applications and Web Services in that IDE fine.
I recently installed VS 2008 Team Developer. In that IDE I can NOT debug
either Web Applications nor Web Services. After clicking "Start Debugging

I'm one of out projects (DLL) the attach to process does not work, we must
start the process from VS to debug the code.
I'm looking for possible reasons why this project is different than others
in the solution.

I use VS 2005 Tools | Attach to process...  to debug other external
applications, such as Notepad.  However, the process being debugged
will be termined also when I "stop debugging" Visual studio.
According to MSDN, this should NOT be the case.