No symbols Loaded

[Jim Heavey]

I converted (manually) my 2003 web site to 2005. When I place my break point
on the first line of code in the page load of the default page, the page does
not stop at the break point. If I hover over the break point, I see the
message "The breakpoint will not currently be hit. No symbols have been
loaded for this document". I'm not sure what this means or what I need to
do. I manually converted console applications and I have had no problem in
running the debugger on those.

My web page calls other classes from other packages, and I am allowed and
the system reacts to break points I place in that code, but it will simply
not react to any break points on the web page. I had the system re-create
the web.config file to ensure the problem was not in that file. When I
removed the config file, the system automatically generated the web.config
file with the appropriate setting which allow me to debug.

I create a new web project and that project allows me to put in break points
and the system reacts to those. SO it must be something that I must set on a
converted project.

Any Ideas?

[vMike]

"Jim Heavey" <Ji*******@discussions.microsoft.com> wrote in message
news:EC**********************************@microsof t.com...

I converted (manually) my 2003 web site to 2005. When I place my break point on the first line of code in the page load of the default page, the page does not stop at the break point. If I hover over the break point, I see the
message "The breakpoint will not currently be hit. No symbols have been
loaded for this document". I'm not sure what this means or what I need to
do. I manually converted console applications and I have had no problem in running the debugger on those.

My web page calls other classes from other packages, and I am allowed and
the system reacts to break points I place in that code, but it will simply
not react to any break points on the web page. I had the system re-create
the web.config file to ensure the problem was not in that file. When I
removed the config file, the system automatically generated the web.config
file with the appropriate setting which allow me to debug.

I create a new web project and that project allows me to put in break points and the system reacts to those. SO it must be something that I must set on a converted project.

Any Ideas?

If you have compiled any dll's you need to use the /debug option to create
the symbols file as follows.

vbc /t:library /out:c:\pathto.dll c:\pathto.vb /r:system.dll
/r:system.web.dll ... /debug

Maybe that will help
Mike

[Jim Heavey]

Thanks Mike, I gather the problem is that VS2005 is not creating my ".PDB"
file. But Why? I am guessing you have provided a way to create one for a VB
program, but I am using c# and there are many screens in this applications,
so I am guessing that the command you have provided would not suffice.

What can I do to get VS2005 to create the file?

vbc /t:library /out:c:\pathto.dll c:\pathto.vb /r:system.dll
/r:system.web.dll ... /debug

[vMike]

"Jim Heavey" <Ji*******@discussions.microsoft.com> wrote in message
news:2E**********************************@microsof t.com...

Thanks Mike, I gather the problem is that VS2005 is not creating my ".PDB"
file. But Why? I am guessing you have provided a way to create one for a
VB
program, but I am using c# and there are many screens in this
applications,
so I am guessing that the command you have provided would not suffice.

What can I do to get VS2005 to create the file?

vbc /t:library /out:c:\pathto.dll c:\pathto.vb /r:system.dll
/r:system.web.dll ... /debug

you might check in to csc.exe and related options.

[Jim Heavey]

Thanks vMike, but excuse my ignorance on this subject.. Since I have always
Visual Studio to compile my projects, I am completely unfamiliar with
compiling at the dos prompt, but I guess it is never too late.

When I VS, it creates an exe and not a dll. Is the format of the command
the same? The "/r:system.dll", should all of the dll which are reference
within the exe be referenced, with just a space in between?

csc /t:library /out:c:\pathto.dll c:\pathto.vb /r:system.dll
/r:system.web.dll ... /debug