RE: RE: Can't get it to work
Written by Mike Malburg on January 9, 2006
Ooops. Meant to say "Root Namespace" not "Assembly Name" in the above post. You can just delete the Root Namespace if you want in the options.
RE: Can't get it to work
Written by Mike Malburg on January 9, 2006
By default in Visual Studio .Net 2003, there is a default Assembly Name that is created when you create a project. So if you named your project "CCWComponent" when creating the project and have not messed with the Assembly Name for the project (Right-click project name, properties, Common Properties > General > Assembly Name), then your fully qualified class name will be: CCWComponent.CCWComponent.CCWClass instead of CCWComponent.CCWClass. I have tested the example given and it works for me. Make sure on step 4 you substitute the actual name of the dll that is created for the "DLL_FOR_10G.dll". And to keep it simple, just rename all the TLBs with the same base name as the name of your dll, and you should be golden. Hope this helps!
RE: Can't get it to work
Written by David Darling on August 24, 2005
+I had the same problem.
+I created a VB.Net project in d:\projects\VBNet\Security.
+It was called Security.vbproj.
+I created a Password.vb class something like this.
Namespace Security
Public Class Password
Public Function Encrypt(ByVal strKey As String, ByVal strData As String) As String
End Function
Public Function Decrypt(ByVal strKey As String, ByVal strData As String) As String
End Function
End Class
End Namespace
+I then compiled everything as specified.
+I then followed the directions as specified.
+I was able to attach the D:\Projects\VBNet\Security\bin\Security.tlb via the Project References in a VB6 program.
+I was able to invoke the processing via Dim objSecurity as New Security.Password
+I was not able to invoke the processing via Set objSecurity = CreateObject("Security.Password")
+However, when I looked in the Registry using RegEdit and examined HKEY_CLASSES_ROOT, I found that my assembly had been registered as Security.Security.Password.
+I was able to invoke the processing via Set objSecurity = CreateObject("Security.Security.Password")
+Perhaps the Password.vb class having an Assembly name of Security coupled with a Root namespace of Security made the ProgId into Security.Security.Password
Can't get it to work
Written by Dermot Carey on September 29, 2004
Great clean article but when i try to call the method in asp i get:<%@ language="VBScript" %> <%@ language="VBScript" %>
<%@ language="VBScript" %>
<HTML>
<BODY>
SET OBJMSGBOX = Server.CreateObject("CCWComponent.CCWClass") Response.write OBJMSGBOX.PassStr("AND ASP")
</BODY>
</HTML>
<%@ language="VBScript" %><%@ language="VBScript" %> <% SET OBJMSGBOX = Server.CreateObject("CCWComponent.CCWClass") Response.write OBJMSGBOX.PassStr("AND ASP") %> <% SET OBJMSGBOX = Server.CreateObject("CCWComponent.CCWClass") Response.write OBJMSGBOX.PassStr("AND ASP") %> <% SET OBJMSGBOX = Server.CreateObject("CCWComponent.CCWClass") Response.write OBJMSGBOX.PassStr("AND ASP") %><%@ language="VBScript" %> <% SET OBJMSGBOX = Server.CreateObject("CCWComponent.CCWClass") Response.write OBJMSGBOX.PassStr("AND ASP") %>
Server object, ASP 0177 (0x800401F3)
Invalid class string
/testNet.asp, line 8
Any ideas why, i followed the article to the letter, and have tried it on three iis machines now.
