no results
Brian Donahue
Posts: 6,590 Bronze 1
Hi Rick,
It depends on the nature of the dll files. Are they COM dlls, and is the
code managed or unmanaged?
Regards,
Brian Donahue
Red Gate Technical Support
"RickN" <rick@abasoftware.com> wrote in message
news:TNXLTQccDHA.1208@server53...
> I am testing your software on a C# .net solutions built w/ the latest
> version of Visual Studio and Framework 1.1 in debug mode. The solution
has
> a main exe and several dll's which get built into their own directory.
> When I run the profiler, all I get is output for a couple side threads in
> the main, like dispose and little to nothing else - nothing at all from
any
> of the referenced dll's-which is where all the action takes place. What
do
> I need to get the profiler to work.
> Thanks,
> RickN
>
>
It depends on the nature of the dll files. Are they COM dlls, and is the
code managed or unmanaged?
Regards,
Brian Donahue
Red Gate Technical Support
"RickN" <rick@abasoftware.com> wrote in message
news:TNXLTQccDHA.1208@server53...
> I am testing your software on a C# .net solutions built w/ the latest
> version of Visual Studio and Framework 1.1 in debug mode. The solution
has
> a main exe and several dll's which get built into their own directory.
> When I run the profiler, all I get is output for a couple side threads in
> the main, like dispose and little to nothing else - nothing at all from
any
> of the referenced dll's-which is where all the action takes place. What
do
> I need to get the profiler to work.
> Thanks,
> RickN
>
>
This discussion has been closed.
Comments
This depends on how the dll files are built. Are they COM components?
Are they built as managed code?
Regards,
Brian Donahue
Red Gate Technical Support
"RickN" <rick@abasoftware.com> wrote in message
news:TNXLTQccDHA.1208@server53...
> I am testing your software on a C# .net solutions built w/ the latest
> version of Visual Studio and Framework 1.1 in debug mode. The solution
has
> a main exe and several dll's which get built into their own directory.
> When I run the profiler, all I get is output for a couple side threads in
> the main, like dispose and little to nothing else - nothing at all from
any
> of the referenced dll's-which is where all the action takes place. What
do
> I need to get the profiler to work.
> Thanks,
> RickN
>
>
Have you made sure that you haven't excluded your namespaces from the
profiling session in the project properties?
Thanks,
Brian Donahue
Red Gate Technical Support
"RickN" <rick@abasoftware.com> wrote in message
news:GvbQjCZmDHA.1472@server53...
> All managed code.
> RickN
>
> "Brian Donahue (Red Gate)" <brian.donahue@red-gate.com> wrote in message
> news:2ZvchkgcDHA.1204@server53...
> > Hi Rick,
> >
> > It depends on the nature of the dll files. Are they COM dlls, and is
> the
> > code managed or unmanaged?
> >
> > Regards,
> >
> > Brian Donahue
> > Red Gate Technical Support
> >
> > "RickN" <rick@abasoftware.com> wrote in message
> > news:TNXLTQccDHA.1208@server53...
> > > I am testing your software on a C# .net solutions built w/ the latest
> > > version of Visual Studio and Framework 1.1 in debug mode. The
solution
> > has
> > > a main exe and several dll's which get built into their own directory.
> > > When I run the profiler, all I get is output for a couple side threads
> in
> > > the main, like dispose and little to nothing else - nothing at all
from
> > any
> > > of the referenced dll's-which is where all the action takes place.
What
> > do
> > > I need to get the profiler to work.
> > > Thanks,
> > > RickN
> > >
> > >
> >
> >
>
>