Watch some penguins on the livecam!
Course Of The Month
7 days, 18 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Debug mode Visual Studio 2010 Class Project don't stop at breakpoints
Posted on 2013-11-08
I'm developing a Class Library with Visual Studio 2010 for .NET Framework 2.0 in C#. This Class import some functions from winscard.dll.
I've a web app that uses that class (dll) so in the DEBUG tab of my project properties I select START BROWSER WITH URL and select DEBUG CONFIGURATION.
In debug mode, the browser load the start page and use one function of the Class, returns a result code but, the execution never stop at the breakpoints selected in Visual Studio so i can't debug the class code.
I've test it with a C# windows exe object and the debug functions ok.
What am I missing to configure for debug using an URL?
I've a web app that uses that class (dll) so in the DEBUG tab of my project properties I select START BROWSER WITH URL and select DEBUG CONFIGURATION.
In debug mode, the browser load the start page and use one function of the Class, returns a result code but, the execution never stop at the breakpoints selected in Visual Studio so i can't debug the class code.
I've test it with a C# windows exe object and the debug functions ok.
What am I missing to configure for debug using an URL?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
5
3
3- +2
13 Comments
Active 3 days ago
Hi,
is the web app part of your Visual Studio solution?
If not afaik you would have to attach to the worker process of your web app to get the breakpoint.
is the web app part of your Visual Studio solution?
If not afaik you would have to attach to the worker process of your web app to get the breakpoint.
Well, please check if the PDB - debug information related to the line of code, is present and loaded, when the application links to the remote site. If not, there is no way to make the debugger to associate your source lines to executable code.
As stated by TheLearnedOne, on must load the debug symbols. Please take a look at
http://msdn.microsoft.com/en-us/library/vstudio/x54fht41(v=vs.100).aspx on how to do it.
As stated by TheLearnedOne, on must load the debug symbols. Please take a look at
http://msdn.microsoft.com/en-us/library/vstudio/x54fht41(v=vs.100).aspx on how to do it.
Active 1 day ago
TheLearnedOne and JoseParrot, first of all thanks for your messages. Checked that and is OK.
I've debugged various class libraries of this kind without problem, but with this dll I'm really stuffed. This is a better explanation:
I am creating a class library (dll) in C # that includes the library WINSCARD.DLL:
[DllImport("winscard.dll")
private static extern int SCardBeginTransaction(IntP
.
.
.
public int ReadUI(out string strUID)
{
.
.
resCode = SCardEstablishContext(SCAR
.
.
}
To test, in Project Properties at Debug tab, I select DEBUG CONFIGURATION and check START BROWSER WITH URL: "http://localhost/mywebapp/mysmartcard.aspx.
I put some break points (ex: at SCardEstablishContext sentence) and press F5 (start debugging). Then the browser is loaded with my start page. I press a button associated with the execution of the function READUI and I get a message generated by the function but the break-point in my c# code is ignored, never stop.
Perhaps the winscard.dll can't be found by the web-app? I really dont know what is happening with this proyect. With other proyects I've developed have no problem at debugging.
Sorry for my english...
I've debugged various class libraries of this kind without problem, but with this dll I'm really stuffed. This is a better explanation:
I am creating a class library (dll) in C # that includes the library WINSCARD.DLL:
[DllImport("winscard.dll")
private static extern int SCardBeginTransaction(IntP
.
.
.
public int ReadUI(out string strUID)
{
.
.
resCode = SCardEstablishContext(SCAR
.
.
}
To test, in Project Properties at Debug tab, I select DEBUG CONFIGURATION and check START BROWSER WITH URL: "http://localhost/mywebapp/mysmartcard.aspx.
I put some break points (ex: at SCardEstablishContext sentence) and press F5 (start debugging). Then the browser is loaded with my start page. I press a button associated with the execution of the function READUI and I get a message generated by the function but the break-point in my c# code is ignored, never stop.
Perhaps the winscard.dll can't be found by the web-app? I really dont know what is happening with this proyect. With other proyects I've developed have no problem at debugging.
Sorry for my english...
Active 1 day ago
have you tried to place a break point right at the top of your page_load event?
are you in debug or release mode (you need to be in debug)?
do you have debuggerstepthrough attributes on your methods (which prevent the debugger from entering in these methods)?
are you in debug or release mode (you need to be in debug)?
do you have debuggerstepthrough attributes on your methods (which prevent the debugger from entering in these methods)?
Active 1 day ago
emoreau, i don't understand.
I'm debugging the DLL not the web-app, so I put breakpoints in the class source code, and press F5, my web-page (external app) is loaded and consume some functions of the DLL.
If the external app is c# windows interfase then the debug works fine.
I'm debugging the DLL not the web-app, so I put breakpoints in the class source code, and press F5, my web-page (external app) is loaded and consume some functions of the DLL.
If the external app is c# windows interfase then the debug works fine.
Active 1 day ago
is your DLL project loaded into the same solution as your web application and your reference set to this instance?
When you start the debugging session, are the breakpoints solid red, or an unfilled circle? They need to be a solid red, in order for the debugger to break on the breakpoint.
Active 1 day ago
This output corresponds to START EXTERNAL PROGRAM (utestvuquest.exe win interfase). If I choose START BROWSER WITH URL (http://localhost/MPECmain/myvuquest.aspx) it shows nothing in the output.
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_M
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_M
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_M
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_M
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_M
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_M
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_M
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
The thread '<No Name>' (0x1dbc) has exited with code 0 (0x0).
The thread '<No Name>' (0x1968) has exited with code 0 (0x0).
The thread '<No Name>' (0x21fc) has exited with code 0 (0x0).
The program '[8308] utestvuquest.exe: Managed (v2.0.50727)' has exited with code 0 (0x0).
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_M
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_M
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_M
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_M
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_M
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_M
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_M
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_3
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
'utestvuquest.exe' (Managed (v2.0.50727)): Loaded 'C:\Factory\AypDesa5\VIGAT
The thread '<No Name>' (0x1dbc) has exited with code 0 (0x0).
The thread '<No Name>' (0x1968) has exited with code 0 (0x0).
The thread '<No Name>' (0x21fc) has exited with code 0 (0x0).
The program '[8308] utestvuquest.exe: Managed (v2.0.50727)' has exited with code 0 (0x0).
Featured Post
Containers are an incredibly powerful technology that can provide you and/or your engineering team with huge productivity gains. Using containers, you can deploy, back up, replicate, and move apps and their dependencies quickly and easily.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Whether you've completed a degree in computer sciences or you're a self-taught programmer, writing your first lines of code in the real world is always a challenge. Here are some of the most common pitfalls for new programmers.
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
Simple Linear Regression
Suggested Courses
Course of the Month7 days, 18 hours left to enroll
729 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.