![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Anyone know how to reference a DLL which does not have a separate .tib file? I have generated the DLL using WSDL.exe and VBC.exe. It generates a single output, a dll file. It includes the information that C++ would put in a separate .tib file. However for visual basic, it is all combined together. However, Access references wants to select the .tib file. Bob |
#3
| |||
| |||
|
|
On 5/11/2011 10:01 PM, BobAlston wrote: Anyone know how to reference a DLL which does not have a separate .tib file? I have generated the DLL using WSDL.exe and VBC.exe. It generates a single output, a dll file. It includes the information that C++ would put in a separate .tib file. However for visual basic, it is all combined together. However, Access references wants to select the .tib file. Bob According to this article http://www.geeksengine.com/article/create-dll.html I need to a) make the dll "COM visible" and 2) register the assembly as a COM component in the Windows registry. I am using WSDL to generate the VB.net class code and VBC.exe to generate the dll. I do not see any option to make the dll COM visible. Other than to use Visual Studio as per the article, how can I achieve these?? You'll probably get a quicker answer in a dotnet group |
#4
| |||
| |||
|
|
On 5/11/2011 10:01 PM, BobAlston wrote: Anyone know how to reference a DLL which does not have a separate .tib file? I have generated the DLL using WSDL.exe and VBC.exe. It generates a single output, a dll file. It includes the information that C++ would put in a separate .tib file. However for visual basic, it is all combined together. However, Access references wants to select the .tib file. Bob According to this article http://www.geeksengine.com/article/create-dll.html I need to a) make the dll "COM visible" and 2) register the assembly as a COM component in the Windows registry. I am using WSDL to generate the VB.net class code and VBC.exe to generate the dll. I do not see any option to make the dll COM visible. Other than to use Visual Studio as per the article, how can I achieve these?? bob Here is a good thread on the topic. |
#5
| |||
| |||
|
|
On 5/12/2011 1:20 PM, BobAlston wrote: On 5/11/2011 10:01 PM, BobAlston wrote: Anyone know how to reference a DLL which does not have a separate .tib file? I have generated the DLL using WSDL.exe and VBC.exe. It generates a single output, a dll file. It includes the information that C++ would put in a separate .tib file. However for visual basic, it is all combined together. However, Access references wants to select the .tib file. Bob According to this article http://www.geeksengine.com/article/create-dll.html I need to a) make the dll "COM visible" and 2) register the assembly as a COM component in the Windows registry. I am using WSDL to generate the VB.net class code and VBC.exe to generate the dll. I do not see any option to make the dll COM visible. Other than to use Visual Studio as per the article, how can I achieve these?? bob Here is a good thread on the topic. http://social.msdn.microsoft.com/For...?prof=required So far it appears you can ONLY do this using Visual Studio. Surely there should be a way to do this without visual studio?? Bob This article would see to be on point |
#6
| |||
| |||
|
|
BobAlston wrote: On 5/11/2011 10:01 PM, BobAlston wrote: Anyone know how to reference a DLL which does not have a separate .tib file? I have generated the DLL using WSDL.exe and VBC.exe. It generates a single output, a dll file. It includes the information that C++ would put in a separate .tib file. However for visual basic, it is all combined together. However, Access references wants to select the .tib file. Bob According to this article http://www.geeksengine.com/article/create-dll.html I need to a) make the dll "COM visible" and 2) register the assembly as a COM component in the Windows registry. I am using WSDL to generate the VB.net class code and VBC.exe to generate the dll. I do not see any option to make the dll COM visible. Other than to use Visual Studio as per the article, how can I achieve these?? You'll probably get a quicker answer in a dotnet group Perhaps but they don't seem to know about /care about VBA clients. |
#7
| |||
| |||
|
|
Anyone know how to reference a DLL which does not have a separate .tib file? |
#8
| |||
| |||
|
|
On Wed, 11 May 2011 22:01:48 -0500, BobAlston<bobalston9 (AT) yahoo (DOT) com wrote: Anyone know how to reference a DLL which does not have a separate .tib file? Do you need the reference? Some DLLs can be used directly from within the code without a reference or registering. Although those DLLs likely need to be in the same folder as your Access FE database file. I'm thinking specifically of Leban's printer PDF DLLs and the open source Info Zip DLLs. Tony Unfortunately for this DLL, created using WSDL.exe and VBC.exe I tried |
#9
| |||
| |||
|
|
Do you need the reference? Some DLLs can be used directly from within the code without a reference or registering. Although those DLLs likely need to be in the same folder as your Access FE database file. I'm thinking specifically of Leban's printer PDF DLLs and the open source Info Zip DLLs. Tony Unfortunately for this DLL, created using WSDL.exe and VBC.exe I tried to add it to the Access References, but it fails. apparently, it is not COM visible. |
#10
| |||
| |||
|
|
On Thu, 12 May 2011 21:25:35 -0500, BobAlston<bobalston9 (AT) yahoo (DOT) com wrote: Do you need the reference? Some DLLs can be used directly from within the code without a reference or registering. Although those DLLs likely need to be in the same folder as your Access FE database file. I'm thinking specifically of Leban's printer PDF DLLs and the open source Info Zip DLLs. Tony Unfortunately for this DLL, created using WSDL.exe and VBC.exe I tried to add it to the Access References, but it fails. apparently, it is not COM visible. But did you try using it in your code without a reference? Tony I don't know how to create a reference to the proxy server method and |
![]() |
| Thread Tools | |
| Display Modes | |
| |