But if you're using XSL transforms that take parameters, you've got a chicken + egg problem - you can only pass parameters using a freethreaded document. Time to decide which you value more - stability or features.
It has more than stability issues. You might actually cause a deadlock in IIS and your webserver will stop responding. If it is an important sit that needs a high up time I would look to see what you are doing. It might be that you can do the transfom in an out of process VB DLL installed into COM+ as a server apllication, and then pass back the transformed results. That is what I would do. No free threaded isssues then.
I got around my original problem with the invalid class sting, but I now have this extra complication of the instability. Damn.
I definetly don't have the time to create COM components, or try anything too fancy. I think I'll just have to see how I go.
My site won't have high loads, or frequent use for that matter (maybe only a few people a day) as it is an intranet application for keeping track of employees CVs in the organisation....
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.