I'm currently making an upgrade from VB6 to VB
.NET on a client. Most of the process has been made, but because we're not ready to upgrade ASP to ASP.NET, I've rewritten a dll called by the ASP pages in VB
All testing has been done and the dll behaves perfectly well, with much better performance than the old VB6 dll. Even in a testing environment, with 100 accesses at the same time all work.
The problems start when actually calling it from ASP. If there is only 1 request it works, 2+ requests at the same time and all hell breaks loose. Either a server not found, a timeout, partial returns, mixed returns (1 client getting another's request) or, rarely, the correct reply.
This seems like an object creation mistake by IIS, and must be related to multiple threads under IIS (if called from VB
.NET it's perfectly thread-safe). I have no clue why this is happening, altough I think it's probably due to the registry settings created by regasm.