If you have applications that need to create objects or call code from a .NET COM dll, then you will need to make sure you have registered the dll correctly. 

To do this type in the following from the command line:


I've just spent a few hours trying to work this is out, as I was working with a classic ASP website that made a 'Server.CreateObject(...)' call to a .NET COM assembly and was getting this error:

When I registered the .NET COM dll as above and placed the dll in the working folder of the website, this problem was resolved.  Take note, that the '/codebase' switch is important, because the website still didn't work until I used this switch - the reason for this, I do not know, so please speak up if you understand and can explain what the '/codebase' switch is actually doing.

---

---