G
Guest
OK - this doesn't make a ton of sense to me. I have a solution containing an
ASP.NET 2.0 project and a class library project. In the ASP.NET application,
I create a project reference to my class library.
When I debug the web application and try to step into my class library, I
get the following message:
"The source file is different from when the module was built. Would you
like the debugger to use it anyway?" - it's like the WebDev.WebServer.EXE
process is hanging onto an older version of my class library dll.
Any thoughts??
thanks,
_howard
ASP.NET 2.0 project and a class library project. In the ASP.NET application,
I create a project reference to my class library.
When I debug the web application and try to step into my class library, I
get the following message:
"The source file is different from when the module was built. Would you
like the debugger to use it anyway?" - it's like the WebDev.WebServer.EXE
process is hanging onto an older version of my class library dll.
Any thoughts??
thanks,
_howard