How should I debug this?

[Jeff]

..NET 2.0

I'm working on 3 projects in VS2005:
- a windows application project
- dll library project
- windows service

This works like this:
The window form call some methods in the dll library project (.net remoting)
which again calls the actual objects running in the windows service...

I have 3 VS2005 open on my pc, one for each of these projects

Now I've tested some functionality on form and it doesn't work. It is
supposed to send info over to the windows service so it can updated a table
in the database...

I've rebuilt the dll library project and installed it.... while target was
set to Debug, should I change it to Release or?

And how should I debug this.??

Any suggestions are most welcome!

Jeff

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

.NET 2.0

I'm working on 3 projects in VS2005:
- a windows application project
- dll library project
- windows service

This works like this:
The window form call some methods in the dll library project (.net
remoting) which again calls the actual objects running in the windows
service...

I have 3 VS2005 open on my pc, one for each of these projects

You do not need 3 VS, as a matter of fact you need only two, one for each
executable. Debugging the service could be a little tricky, I do not know
any way to debug the onStart method of it. What I do is start the service
from the services panel and then use Debug/Attach to process to debug the
running of the project.

 

[Chris Dunaway]

Hi,







You do not need 3 VS, as a matter of fact you need only two, one for each
executable. Debugging the service could be a little tricky, I do not know
any way to debug the onStart method of it. What I do is start the service
from the services panel and then use Debug/Attach to process to debug the
running of the project.

I've resorted to a hack to debut OnStart before. I simply put a
Thread.Sleep for about 10 seconds, enough time for me to attach the
debugger.

Chris

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

I've resorted to a hack to debut OnStart before. I simply put a
Thread.Sleep for about 10 seconds, enough time for me to attach the
debugger.

Nice, but you have to be fast, otherwise you will lose it. Also you might
forget to remove it when moved into production.

I do something similar, My OnStart just spraw a thread and then inside I do
all the work, in this case the OnStart has NO code at all.

 

[Jon Skeet [C# MVP]]

<"Ignacio Machin \( .NET/ C# MVP \)" <machin TA laceupsolutions.com>>
wrote:

I do something similar, My OnStart just spraw a thread and then inside I do
all the work, in this case the OnStart has NO code at all.

How do you manage to spawn a thread without having any code at all?

 

[Ignacio Machin \( .NET/ C# MVP \)]

<"Ignacio Machin \( .NET/ C# MVP \)" <machin TA laceupsolutions.com>>
wrote:



How do you manage to spawn a thread without having any code at all?

I talk to it nicely