Why is debugger looking here for source code? Is there a work around? How can I point it somewhere else?
C:\Users\Stephen\Documents\Repos\Superexpert\AjaxControlToolkit\Server\AjaxControlToolkit
Thanks.
Comments: Well...it's June 9, 2012 and this issue is still alive and kicking!!! I am miffed that this issue hasn't been assigned yet, and I don't agree that this has Low impact. The missing source file throws exceptions in running code, which causes me to pass through this error and possibly miss other, more troublesome code issues. I get exactly the same error description, which was initially uncovered back in late 2010! Microsoft has passed the ball on this issue, with their posting at http://msdn.microsoft.com/en-us/library/3sehk0fb%28VS.80%29.aspx. The only thing I can try is a work-around posted by Erwin Mayer here, http://erwinmayer.com/labs/visual-studio-2010-extension-disable-no-source-available-tab/, and here, http://visualstudiogallery.msdn.microsoft.com/fdbb2036-471e-40a7-b20e-31f8fd5578fa/. In my mind, letting this bug flounder for two years does not bode well for the AJAX development group! Hope to see this Issue Tracker come to life in the coming days and a solution shortly thereafter.
C:\Users\Stephen\Documents\Repos\Superexpert\AjaxControlToolkit\Server\AjaxControlToolkit
Thanks.
Comments: Well...it's June 9, 2012 and this issue is still alive and kicking!!! I am miffed that this issue hasn't been assigned yet, and I don't agree that this has Low impact. The missing source file throws exceptions in running code, which causes me to pass through this error and possibly miss other, more troublesome code issues. I get exactly the same error description, which was initially uncovered back in late 2010! Microsoft has passed the ball on this issue, with their posting at http://msdn.microsoft.com/en-us/library/3sehk0fb%28VS.80%29.aspx. The only thing I can try is a work-around posted by Erwin Mayer here, http://erwinmayer.com/labs/visual-studio-2010-extension-disable-no-source-available-tab/, and here, http://visualstudiogallery.msdn.microsoft.com/fdbb2036-471e-40a7-b20e-31f8fd5578fa/. In my mind, letting this bug flounder for two years does not bode well for the AJAX development group! Hope to see this Issue Tracker come to life in the coming days and a solution shortly thereafter.