|
|
|
date: Wed, 20 Apr 2005 15:29:38 +0800,
group: microsoft.public.dotnet.myservices
back
Re: why service reference other project can not be debuged.
It's better to debug into the class referenced from other project, but i
only want to debug
the service itself. Actually, i can debug it and write text file as long as
do not create an instance
of the referenced class.And,i don't think it's necessary to reinstalling
the service to SCM because
i install it from the build output path.
Any advice?
--alien
> (I want debug the service itself, not the dll) Maybe I don't understand
> your question. I thought you said you see no source when you drop down
> into the DLL, and that was your qualm?
>
> I can debug main service, or DLL's it calls that I make myself when
> using the second approach.
>
> I wonder if yours is an installation / configuration issue? Are you
> reinstalling the service to SCM after making a debug build? This really
> has nothing to do with VS, more so services fundamentals.
>
> - Lee
>
> alien wrote:
> > thank you for your help.
> > but,i want debug the service itself, not the dll referenced, and, i
using
> > the second way you said to reference it.
> > Do you have more suggestion.
> >
> >
> >>It has been my experience that it depends on how you add the reference
> >>to your application. Same would apply to desktop windows apps.
> >>
> >>If you
> >>1) Add reference to your app by...
> >>2) Browse to the dll binary
> >>Then you are limited by last dll project build
> >>
> >>But if you
> >>1) Add dll project to your app solution
> >>2) Add reference to your app by...
> >>3) Choose from SOLUTION PROJECTS rather than browse DLL
> >>Then your DLL is built DEBUG same as main app
> >>A number of debugging and kit building things go better
> >>
> >>HTH - Lee
date: Fri, 22 Apr 2005 09:01:04 +0800
author: alien
Re: why service reference other project can not be debuged.
This is my approach. See if you can spot the variation between it and
what you are doing...
When I add a dependent DLL project to my solution, and I go to make
references to it (for any project), I add from the PROJECTS tab, and NOT
by browsing to the DLL. ALL references for all projects in the
solution must be made via the PROJECTS tab. This subtle step is
important, or you won't be running what you think you are.
I install the service with INSTALLUTIL, or the kit I make.
I then MANUALLY edit the SCM registry so it points to the service EXE in
my project BIN folder. These steps only need be done once, at the
development workstation.
I must stop the service to compile. If it allows me to build with the
service running, then I know I don't have the service EXE location in
the SCM registry set up properly.
When I start the service again, it fires up my very latest debug build.
Stopping and starting services function is available in the IDE.
Then to debug, I ATTACH to the running service process.
When I build a solution that contains the service project, and all
dependent DLL projects in this way, and do a solution debug build, I
have full debug access to all the source code of any of the projects
which are part of the solution.
I think it sounds like you make have done part of this, but not all?
- Lee
alien wrote:
> It's better to debug into the class referenced from other project, but i
> only want to debug
> the service itself. Actually, i can debug it and write text file as long as
> do not create an instance
> of the referenced class.And,i don't think it's necessary to reinstalling
> the service to SCM because
> i install it from the build output path.
> Any advice?
> --alien
>
>
>>(I want debug the service itself, not the dll) Maybe I don't understand
>>your question. I thought you said you see no source when you drop down
>>into the DLL, and that was your qualm?
>>
>>I can debug main service, or DLL's it calls that I make myself when
>>using the second approach.
>>
>>I wonder if yours is an installation / configuration issue? Are you
>>reinstalling the service to SCM after making a debug build? This really
>>has nothing to do with VS, more so services fundamentals.
>>
>>- Lee
>>
>>alien wrote:
>>
>>>thank you for your help.
>>>but,i want debug the service itself, not the dll referenced, and, i
>
> using
>
>>>the second way you said to reference it.
>>>Do you have more suggestion.
>>>
>>>
>>>
>>>>It has been my experience that it depends on how you add the reference
>>>>to your application. Same would apply to desktop windows apps.
>>>>
>>>>If you
>>>>1) Add reference to your app by...
>>>>2) Browse to the dll binary
>>>>Then you are limited by last dll project build
>>>>
>>>>But if you
>>>>1) Add dll project to your app solution
>>>>2) Add reference to your app by...
>>>>3) Choose from SOLUTION PROJECTS rather than browse DLL
>>>>Then your DLL is built DEBUG same as main app
>>>>A number of debugging and kit building things go better
>>>>
>>>>HTH - Lee
>
>
>
date: Fri, 22 Apr 2005 07:26:52 -0700
author: Lee Gillie
|
|
