Hi all,
I've a got misbehaving transaction service interceptor that throws an "object reference not set to an instance of an object" when I deploy to our test environment. The requirement for this interceptor is to insert a special request for new or updated orders that meet specific criteria.
The interceptor passes my unit and integration tests. It has a dependency on a class that references the System.Data.SqlClient library, when I remove this dependency the plugin works (i.e., it doesn't throw the error). I've tried copying this system assembly into the plugin folder, as well as restarting the application pool etc. with no success.
Is anyone able to point me in the right direction?
Cheers,
Patrick.
Sorted it out. I was referencing an app config file to get my database connection string.
Adding this file to the plugin folder didn't give me any relief, but if you examine the SqlCommandHelper class from the sample service plugin project on TASK, you'll see that it references a library called Tessitura.Encryption.Util. This has a class (ConfigurationHelper) with a method that returns and decrypts the connection string in the service's web.config. Very nice.
Included this in my plugin and I'm up intercepting services all over the place!
Great! Aren't they fun! What I have found really useful are the unit tests for them. I am using the Microsoft Research's moles for mocking the the Tessitura libraries.
Jon
Hi Jon,
Interesting point about unit tests, when I think about it I'm actually just doing integration tests because my static interceptor method is tightly coupled with the SQL client and I don't currently have a way of mocking / injecting that class. How are you working around this?