An interesting thing happened to me today. I'm converting an asp webpage to asp.net. One of my pages has functions from another file imported through the

<!-- include file="myfile.aspx"-->

format. When debugging, instead of stepping into the myfile.function, the debugger starts stepping through what appears to be a random segment of the code on the current page, except that it stepps in the pattern of the code on the myfile page. it steps in this bizzare manner until it has finished with the "ghost code" (which I like to call it) and returns the proper value to the original function call.

Is there a bug whereby VS .Net 2003 cannot handle debugging using include file linkage? This is not an emergency but is really curious and is a pain since I can't watch variables on the myfile code when this happens. One of the wierder things I've ever seen.

James

are you using c# or vn.net?

It's vb.net code (mostly upgraded from vbscript through a converter).