[Backalaika-developers] Client/server phase complete, but hard to debug

[Nando F. <nan...@ma...>]

Backalaikers,

All 3 tiers are connected, but very hard to debug. An exception 
generated anywhere in the chain, e.g. FileServer OR BackupServer, is 
forwarded and only appears in Admin!

In order to find out where the exception comes from, you have to:
1) Start the suspicious project in M$ CLR Debugger
2) Go to menu Debug / Exceptions...
3) Set "When the exception is thrown" to "Break into the debugger".

It is also convenient to register M$ CLR Debugger as a Just-In-Time 
debugger for the CLR. This can be done in Tools - Options - Debugging - 
Just-In-Time. After this, when an exception happens, a window gives you 
the option of using the debugger. But this does not solve the exception 
forwarding problem.

If I am a debugging idiot, would someone please explain an easier way to 
do it, provided you spoiled rich children don't force me to buy Visual 
Studio. Right now it seems to me that the proper remedy for this is to 
write tests!

Time for XP...


Fabio,
The task list in #D was getting flooded with warnings about duplicate 
references. I finally found out what it was: Both BackupServer and 
FileServer projects had references to the remoting assembly in the GAC. 
These were not needed. After deleting them, it is now possible to build 
all 3 projects at once by pressing Alt-F8.

Nando