Hello,<BR><BR>I am in the process of creating a "Data Access Layer" business object in VB.NET. I have read that these objects cannot be used in Classic ASP, but my manager is convinced otherwise. He stated that by checking "register for COM interop" in VS.NET/Configuration Properties/Build that the object will expose a COM interface that can be used by Classic ASP. Is this true? I cannot get it to work. Is there any other way to do this?Is that you can supposedly do this by using regAsm.exe. I can now reference the object in a VB6 application. However, the public methods are not exposed. I cannot instantiate the object at all in a Classic ASP environment. Please help.Try reading the following article:<BR>http://www.gotdotnet.com/quickstart/howto/doc/Interop/Building_Samples_COM2NET.aspx<BR><BR>You have to create a type library for the .NET Component so that languages like VB know which methods/properties, etc are available to the class.<BR><BR>There are also several limitations to doing this, which the article explains (via a link)<BR><BR>Hope that helps.Thanks for your help! I think piece I was missing was to use gacutil.exe to install the assembly in the global assembly cache. However, when I tried to do this, I received the following error:<BR><BR>"Failure adding assembly to the cache: Attempt to install an assembly without a strong name."<BR><BR>I am looking into the meaning of this and I am finding it to be a bit over my head. If anyone can help on this, I'd appreciate it.Dear Me,<BR><BR>I have successfully used regASM.exe, tlbExp.exe, gacUtil.exe, and the sn.exe to create a "Strong Assembly Name". Now, I can't remember what order I did it in, but it seems to be working (somewhat). Do I have to do it all again every time I change the VB.NET object that I have created? Head = Spinning <BR><BR>Love,<BR>MeOk, I have successfully created a .NET business object, created a "Strong Name" for it, and exposed a COM interface by using the regAsm and gacUtil utilites. The only problem I am left facing is that the class was pulling a connectionString from the web.config file, which failed when calling the method from classic ASP. Is there some reference I need to add for this or can it not be done?.