works on one, but not on the other
Posted: Thu Sep 20, 2018 11:37 am
Hello-
I have a basic console app which uses the SDK to open an order, make a small edit, and then save the order.
When executed on my machine against a given order, it works. When the output folder is xcopy'd over to another dev's machine and executed against the same order it does not. The exception message is the following:
The order has unresolved errors. Any outstanding errors must be resolved before
the order can be saved.
When I modify the code to interrogate the IOrder.GetMessages() collection, I see the following:
There are outstanding order module compilation errors.
I know this validation message is typically related to CORs stuff, but since I received NO errors nor exceptions on the first machine, I'm questioning that line of thought.
I thought xcopy'ing the entire output folder of my console app would resolve any issues related to missing dll's, etc.
Thoughts appreciated.
I have a basic console app which uses the SDK to open an order, make a small edit, and then save the order.
When executed on my machine against a given order, it works. When the output folder is xcopy'd over to another dev's machine and executed against the same order it does not. The exception message is the following:
The order has unresolved errors. Any outstanding errors must be resolved before
the order can be saved.
When I modify the code to interrogate the IOrder.GetMessages() collection, I see the following:
There are outstanding order module compilation errors.
I know this validation message is typically related to CORs stuff, but since I received NO errors nor exceptions on the first machine, I'm questioning that line of thought.
I thought xcopy'ing the entire output folder of my console app would resolve any issues related to missing dll's, etc.
Thoughts appreciated.