Hi,

I've recently moved some serviced .net components from using library to
server activation. However, I'm now finding that my breakpoints are no
longer firing whilst debugging and it's therefore proving very difficult to
progress my development. Has anyone had any experience of this and know of a
resolution?

Many thanks

Al

Hi,

Just some further information....

All my code is in one solution. So projects for each dll and the client
exe.
All the projects are in seperate directories, but output to the bin
directory of the client exe project.
The entire solution is vb .net, but accesses various com objects via interop.
The exe is to be deployed on the server as an overnight process.

Thanks

Al

"Al Black" wrote:

> Hi,
>
> I've recently moved some serviced .net components from using library to
> server activation. However, I'm now finding that my breakpoints are no
> longer firing whilst debugging and it's therefore proving very difficult to
> progress my development. Has anyone had any experience of this and know of a
> resolution?
>
> Many thanks
>
> Al

Hi,

Just some further information....

All my code is in one solution. So projects for each dll and the client
exe.
All the projects are in seperate directories, but output to the bin
directory of the client exe project.
The entire solution is vb .net, but accesses various com objects via interop.
The exe is to be deployed on the server as an overnight process.

Thanks

Al

"Al Black" wrote:

> Hi,
>
> I've recently moved some serviced .net components from using library to
> server activation. However, I'm now finding that my breakpoints are no
> longer firing whilst debugging and it's therefore proving very difficult to
> progress my development. Has anyone had any experience of this and know of a
> resolution?
>
> Many thanks
>
> Al