C# workin with xsd file
-
I received a C# 2008 console application from a contract shop to work with. The purpose of the console application is to consume data it receives from a web service. (The contract shop that wrote the web service also wrote the console application I am suppose to work with.) My questions are the following: 1. The console application writes to a log file. The only results I can see that can come from the log file is a dos window that displays while the application is running. If this is true, can you tell me how to have the log file write to a different location? 2. When I run the console application, I sometimes see error messages that show up in the dos popup window. At first I thought the error messages came from the web service. However today I opened up an *.xsd file and I see alot of the error messages that appeared in the dos window the last few days. Thus can you tell me how to determine how the *.xsd file is wired to the application? I would like to learn how the code is called. 3. Can I step through the code that is executed from the *.xsd file? If so, how would I accomplish this task? Do I need certain debug options set?
-
I received a C# 2008 console application from a contract shop to work with. The purpose of the console application is to consume data it receives from a web service. (The contract shop that wrote the web service also wrote the console application I am suppose to work with.) My questions are the following: 1. The console application writes to a log file. The only results I can see that can come from the log file is a dos window that displays while the application is running. If this is true, can you tell me how to have the log file write to a different location? 2. When I run the console application, I sometimes see error messages that show up in the dos popup window. At first I thought the error messages came from the web service. However today I opened up an *.xsd file and I see alot of the error messages that appeared in the dos window the last few days. Thus can you tell me how to determine how the *.xsd file is wired to the application? I would like to learn how the code is called. 3. Can I step through the code that is executed from the *.xsd file? If so, how would I accomplish this task? Do I need certain debug options set?
I don't know about 2 and 3, maybe I can help with 1: ProcessCommunicator[^]
-
I received a C# 2008 console application from a contract shop to work with. The purpose of the console application is to consume data it receives from a web service. (The contract shop that wrote the web service also wrote the console application I am suppose to work with.) My questions are the following: 1. The console application writes to a log file. The only results I can see that can come from the log file is a dos window that displays while the application is running. If this is true, can you tell me how to have the log file write to a different location? 2. When I run the console application, I sometimes see error messages that show up in the dos popup window. At first I thought the error messages came from the web service. However today I opened up an *.xsd file and I see alot of the error messages that appeared in the dos window the last few days. Thus can you tell me how to determine how the *.xsd file is wired to the application? I would like to learn how the code is called. 3. Can I step through the code that is executed from the *.xsd file? If so, how would I accomplish this task? Do I need certain debug options set?
1. I'd guess they are using TraceListeners[^]. The one you're probaly after is the TextWriterTraceListener[^]. The link has a code snippet on how to implement the TextWriterTraceListener to help get started. The first link shows how to setup a listener declaratively using the config file. This is the better way to go because you can control your listeners without recompiling the application. 2. Don't know
"You get that on the big jobs."
-
I received a C# 2008 console application from a contract shop to work with. The purpose of the console application is to consume data it receives from a web service. (The contract shop that wrote the web service also wrote the console application I am suppose to work with.) My questions are the following: 1. The console application writes to a log file. The only results I can see that can come from the log file is a dos window that displays while the application is running. If this is true, can you tell me how to have the log file write to a different location? 2. When I run the console application, I sometimes see error messages that show up in the dos popup window. At first I thought the error messages came from the web service. However today I opened up an *.xsd file and I see alot of the error messages that appeared in the dos window the last few days. Thus can you tell me how to determine how the *.xsd file is wired to the application? I would like to learn how the code is called. 3. Can I step through the code that is executed from the *.xsd file? If so, how would I accomplish this task? Do I need certain debug options set?
dcof wrote:
I received a C# 2008 console application from a contract shop to work with
Meaning you got the executable or the code?
dcof wrote:
can you tell me how to have the log file write to a different location?
That depends on how they are logging. However you can run an app using the following which MIGHT work. There must NOT be a space between the 2 and >.
MyApp 2>ErrorFile.txt >Output.txt
dcof wrote:
Thus can you tell me how to determine how the *.xsd file is wired to the application? I would like to learn how the code is called.
Obviously looking at the code would tell you.
dcof wrote:
Can I step through the code that is executed from the *.xsd file?
No. You can step through the code of the application though.