By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,686 Members | 1,840 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,686 IT Pros & Developers. It's quick & easy.

Definition of Frustrating...

P: n/a
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...
Nov 21 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
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

--
W.G. Ryan MVP (Windows Embedded)

TiBA Solutions
www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
"Terry Olsen" <to******@hotmail.com> wrote in message
news:eY**************@TK2MSFTNGP15.phx.gbl...
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...

Nov 21 '05 #2

P: n/a
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.
"W.G. Ryan eMVP" <Wi*********@NoSpam.gmail.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...
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

--
W.G. Ryan MVP (Windows Embedded)

TiBA Solutions
www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
"Terry Olsen" <to******@hotmail.com> wrote in message
news:eY**************@TK2MSFTNGP15.phx.gbl...
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...


Nov 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.