Definition of Frustrating...

[Terry Olsen]

Creating a test app to perfect some code before putting it in a production
app. Test app works perfectly, doesn't work at all in the production app.
Can't figure out why...

 

[W.G. Ryan eMVP]

Without some more info it's hard to help but the usual culprits are 1)
connection strings 2) configuration files 3) assembly references 4) project
references of third party tools.

That's where System.Diagnostics.Trace comes in really useful

 

[Terry Olsen]

Here's the breakdown...

I wrote a class to handle a TCPListener, respond to connection requests,
etc. Compiled it into a dll. Made a quick & dirty test app to test it.
Able to connect, exchange data, etc. I do this by generating events and the
test app catching the events and acting on them. All works great.

Go to the production app, create a reference to the dll, add the "imports"
statement to the app, do all the exact same calls and event handlers that I
did in the test app, but for some reason I'm not getting any events
generated. It's supposed to generate a "ConnectionRequest" event when
there's a pending connection so I can accept the connection. Works fine in
test app...not getting an event fired in the production app. I've got to do
more digging before I get too specific. It's got to be something obvious
that I'm overlooking.