RE: ASP "stop" command works...additional information

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

more than just my main page includes functionality.asp. Here is the structure:

localhost/index.asp includes localhost/_include/functionality.asp
localhost/downloads/program_upgrades.asp includes
localhost/_include/functionality.asp

If you set breakpoints in functionality.asp and visit ONLY index.asp or ONLY
program_upgrades.asp, then the debugger will hit the breakpoints just fine.

But, if you visit index.asp, and then you visit program_upgrades.asp, the
breakpoints won't get hit in functionality.asp. If, at this point, you go to
the "Running Documents" window you'll see:

+ index.asp
functionality.asp
+ downloads/program_upgrades.asp
functionality.asp

How can I get the debugger to hit breakpoints in both running documents?

I also found the following post on this newsgroup, which looks like the same
problem, but no replies.

http://groups-beta.google.com/group/microsoft.public.vsnet.debugging/browse_frm/thread/33ea4e9012edf5e1/375d936a1e3ea4d5?q=author:tomas.karban@xxxxxxxxxx&rnum=1&hl=en#375d936a1e3ea4d5

Thanks...
Travis

"Travis" wrote:

> Hello...
>
> I'm using VS.NET 2003 to debug an ASP application locally. Everything
> has been working fine, until I was re-working some code. I changed the
> code to use a command object to execute a stored procedure against a
> new database. The old code used connection.Execute against a different
> database. My project was created using an empty C# web project and
> adding all my asp pages. It has no web.config, and is only configured
> for ASP debugging under Project Properties--no asp.net debugging.
>
> My main page is program_upgrades.asp which has an <!--#include
> file="functionality.asp"-->. Code below is from functionality.asp.
>
> -- SNIP --
> ' <Dim Statements Omitted>
> Set crmConnection = Session("db_conn_6") 'pre-initialized, new database
> connection
> Set paramCompCode = Server.CreateObject("ADODB.Parameter")
> Set paramPartID = Server.CreateObject("ADODB.Parameter")
> Set paramPlatform = Server.CreateObject("ADODB.Parameter")
> Set paramReturnValue = Server.CreateObject("ADODB.Parameter")
> Set command = Server.CreateObject("ADODB.Command")
>
> ' <Parameter construction statements omitted>
>
> command.Name = "IsProductModuleOwned"
> command.CommandType = adCmdStoredProc
> command.NamedParameters = True
>
> ' <Parameters.Append statements omitted>
>
> Set command.ActiveConnection = crmConnection
> Stop
> ' Next statement causes an error, which is why I'm trying to debug.
> command.Execute , , adExecuteNoRecords
> -- SNIP --
>
> If I run the app using F5 in VS.NET, it will stop at the "Stop"
> statement. At that point I can examine variables such as
> command.Parameters(0) in the watch window, but if i try to Set Next
> Statement it brings up the "Resolve Ambiguity" dialog, which has no
> locations to select from.
>
> If I remove the Stop statement and place a breakpoint at "Set
> command.ActiveConnection = crmConnection" it doesn't stop at the
> breakpoint. But it DOES break into the code when the "command.Execute
> , , adExecuteNoRecords" line causes an error. In this scenario I can
> examine variables, but again if I try to Set Next Statement it brings
> up the "Resolve Ambiguity" dialog, which again has no locations to
> select from.
>
> In either case, the Command Window does this:
> ? paramPartID.Value
> 121
> paramPartID.Value = 122
> Unable to evaluate the expression.
> command.Parameters.Refresh
> Unable to evaluate the expression.
>
> Debugging was working fine until I added the code to use the command
> object.
>
> (PS the error that the command.Execute line raises is "Microsoft OLE DB
> Provider for ODBC Drivers: [Microsoft][ODBC SQL Server Driver]Syntax
> error or access violation", but that shouldn't cause debugging not to
> work. The error, I think, can be resolved by constructing my
> parameters collection correctly, but can't check that out til I can
> debug.)
>
> Any ideas?
> Travis
>
>
.

Relevant Pages

  • VS.NET 2003, often wont stop at breakpoints, at wits end!
    ... Not stopping at breakpoints while ... debugging is a very common problem with my use of VS.NET 2003 and I'm ... their machines. ... to debug mode. ...
    (microsoft.public.vsnet.general)
  • RE: VS.NET 2003, often wont stop at breakpoints, at wits end!
    ... "Matt Greer" wrote: ... Not stopping at breakpoints while ... > debugging is a very common problem with my use of VS.NET 2003 and I'm ... > -- I am running in Debug mode ...
    (microsoft.public.vsnet.general)
  • Re: Breakpoints are not getting hit in ASP.NET (C#) project
    ... Check Machine Debug Manager is working. ... Continued to my earlier post regaring "Breakpoints are not getting hit" ... I am getting the following error while debugging any newly created ... · Very first time there was nothing selected in the "choose the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: VS .NET not breaking on breakpoints
    ... try to start debugging with F10. ... where the problematic breakpoints are set (if the application's design ... Will the proper source code be shown? ... > F5 the execution still does not break on the breakpoints. ...
    (microsoft.public.vc.debugger)
  • Re: Object reference not set to an instance of an object
    ... can't help you with the assembler code. ... Check the callstack, check parameter values ... Try debugging the design time ... >> breakpoints in your code and examine its data etc. ...
    (microsoft.public.dotnet.framework.windowsforms)