Hi Branco,
Thanks for advices, It worked... :)))
Only "assembly a strong name" and cliend dll was same directory required.
Thanks for all helps.....
Best regards,
Hakan
"Branco Medeiros" <br*************@gmail.comwrote in message
news:11**********************@k78g2000cwa.googlegr oups.com...
Hakan ÖRNEK wrote:
Armin,
Thanks for your link, but for custom binding methods required add
referance
from dll.
<Imports Simple_Type.Simple_Type>
I dont want to add referance from created object dll.
Can I use Createobject() method like a vbscript codes;
dim o as object
SET o=CreateObject("MyDll.dll","MyClass")
call o.TestMethod()
<snip>
The CreateObject() function works only with COM libraries. Therefore,
it seems you'd need to have your original .Net MyDll.dll registered in
the COM framework, first.
You need to mark the relevant class (in your case, "MyClass", although
this is a reserved name, I suppose you only used it as an example), I
was saying, you need to mark the relevant class as both "COM class" and
"COM visible" -- select the class in the project/solution explorer and
these options will become available.
Then you need to enable the "Make Assembly COM visible flag": open the
project properties and click the "Assembly Information..." button in
the Applcation tab.
Finaly, after the dll is compiled, you must register it in the COM
framework. To this, use the regasm application (I guess you can
download it with the .Net SDK):
regasm /codebase "your dll path"
Finally, inside your client application you'd use (notice that I don't
have VB.Classic installed here, so I can't confirm the syntax):
dim o as object
Set o=CreateObject("MyDll.dll.MyClass")
call o.TestMethod()
HTH.
Regards,
Branco.