Source Files
Brian Donahue
Posts: 6,590 Bronze 1
Hi Luke,
From what I gather, it soulds like you should be profiling IE unless the
UserControl is being run by IIS. If you've got something like an add-in, for
instance a Visual Studio add-in, you should profile the calling application,
even though it's COM-based, ignore the warning, and carry on running through
your add-in code.
Kind Regards,
Brian Donahue
Red Gate Technical Support
"Luke Burnham" <luke_burnham@idx.com> wrote in message
news:VGIBg343DHA.1904@server53...
> Please explain the project conditions/settings under which I can expect to
> see source file text in the lower profile results pane? For example, must
I
> be profiling a .Net application as opposed to a Web application or Windows
> Form? Are there other conditions? Can you also explain the conditions
under
> which the View/Locate Source Code menu option is enabled.
>
> I'm profiling a .Net UserControl within an IE host and although the
profiler
> works wonderfully, I'm unable to view source files.
>
>
From what I gather, it soulds like you should be profiling IE unless the
UserControl is being run by IIS. If you've got something like an add-in, for
instance a Visual Studio add-in, you should profile the calling application,
even though it's COM-based, ignore the warning, and carry on running through
your add-in code.
Kind Regards,
Brian Donahue
Red Gate Technical Support
"Luke Burnham" <luke_burnham@idx.com> wrote in message
news:VGIBg343DHA.1904@server53...
> Please explain the project conditions/settings under which I can expect to
> see source file text in the lower profile results pane? For example, must
I
> be profiling a .Net application as opposed to a Web application or Windows
> Form? Are there other conditions? Can you also explain the conditions
under
> which the View/Locate Source Code menu option is enabled.
>
> I'm profiling a .Net UserControl within an IE host and although the
profiler
> works wonderfully, I'm unable to view source files.
>
>
This discussion has been closed.
