Aug 21 2019 08:23 AM
Aug 26 2019 02:03 PM - edited Aug 26 2019 02:05 PM
SolutionFWIW: It was determined that the use of the using{} statement was the cause of the issue. It was causing the disposal of the object that was being returned to be cleared before it could be used back in calling function. It appears that this it was not fixed until .NET 4.5, which is why it did not "raise its ugly head" until now. I have removed the using{} statement and moved to calling function in those particular areas and all is good now.
Aug 26 2019 02:03 PM - edited Aug 26 2019 02:05 PM
SolutionFWIW: It was determined that the use of the using{} statement was the cause of the issue. It was causing the disposal of the object that was being returned to be cleared before it could be used back in calling function. It appears that this it was not fixed until .NET 4.5, which is why it did not "raise its ugly head" until now. I have removed the using{} statement and moved to calling function in those particular areas and all is good now.