Hi Joel,
The thing is happens across multiple similar dev environments when connecting to a queue. Security is host based so all that is passed are string values to the initializer.
I do understand all that you have said, but the type of exception and message (Failed to load mqe.dll) sure sounds more like an assembly binding issue, no? I can throw some asserts in there to check for empty strings but I am pretty certain this library has some other issues, whether or not its caused by some unmanaged code I am using or not.
We have replicated this across different versions in multiple environments.
Thanks a lot Joel.
The thing is happens across multiple similar dev environments when connecting to a queue. Security is host based so all that is passed are string values to the initializer.
I do understand all that you have said, but the type of exception and message (Failed to load mqe.dll) sure sounds more like an assembly binding issue, no? I can throw some asserts in there to check for empty strings but I am pretty certain this library has some other issues, whether or not its caused by some unmanaged code I am using or not.
We have replicated this across different versions in multiple environments.
Thanks a lot Joel.
No comments:
Post a Comment