D
dbeavon
Guest
>> We are working on prioritizing this to be higher in the queue. So I'm hearing there isn't a way to troubleshoot on my end? Alternatively, how should I bundle up this issue to send it over to tech support? It happens so infrequently in in production that I will have a very hard time coming up with a consistent reproducible. I may be able to refactor our use of the CLR bridge so it doesn't happen in the PASOE connect procedures (whereby it is causing users to get error messages that appear almost identical to connectivity or authentication failures). But before I start refactoring this code and moving it around, I'd like to know where to move it so that it is less likely to raise the error messages. >> Regarding the AppDomain ... Any static members in the CLR that an ABL programmer interacts with will also affect the other ABL sessions as well. It is worth documenting this at the very least, since it might be unexpected and unintuitive to a programmer. In contrast, on the ABL side of things all the static members of ABL classes are isolated within the context of the individual ABL session.
Continue reading...
Continue reading...