|
Problem:First C# 2008 app did not find the location of where the executable was located for the second program.
When my company deployed my C# 2008 and 2010 applications to a test server, one of the applications did not use the configuation set for where the executable was suppose to be at? Our network administrator found where the first program thinks the second executable was at.
Thus I am trying to determine why one of the programs did not take the setting it was given.
The location the first program was looking at was at:
c:/server name/share directory name/test/app1.exe.
The only way I can think this location was picked since on a few tries, the location of the executable as was at:
//server name/share directory name/test/app1.exe
Is this accidently? Should I have the network administrator reboot the test server to see if the c:/server name/share directory name/test/app1.exe. location request goes away?
|
|
|
|
|
dcof wrote: Should I have the network administrator reboot the test server
Why? You are just guessing here. The first thing to do is to investigate what is wrong with your program.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
I think you need to learn how to debug applications. Deploy debug builds to the servers, and use remote debugging to hook up to the application you think is at fault. Actually step over the code and see what's going on, rather than expecting us to throw random guesses as to what the problem could be. Deploy and pray is not a valid testing strategy.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
