I am trying add OTAClient.dll (HP Quality Center) to the COM components of VS 2010. It is a 32bit dll and I have run the following on code from the SysWOW64 directory as an admin. It runs successfully and when I open VS 2010 and try to add the COM to my toolbox it is not listed. I browse for the file itself and try to add it, but it does not appear in the list. Any suggestions?
regsvr32 "C:\Program Files (x86)\HP\Quality Center Client Side\OTAClient.dll"
I tried adding the .dll as a reference and I get the following warnings:
"The reference component 'TDAPIOLELib' cound not be found."
"The specified task executable "TlbImp.exe" could not be run. The requested operation requires elevation"
"Cannot find wrapper assembly for type library "TDAPIOLELib".
Related
I have a project in visual c++ where I am referring some external DLL.
I have already included the lib directory in linker section and mention it in the input section of the linker and also included the same in c/c++ General Additional Include Directories section.
Thus the project compiles successfully but whenever I try to run it; it fails with an error "Application was unable to start correctly" but if I see the output section it seems everything is loaded correctly but against that particular Dll it says that "Cannot find or open the PDB file".
How to fix this error so that I can run my program. It is an MFC program running in Visual Studio 2010.
when I run the program through the Dependency Walker, most of the API-MS-WIN-CORE-HEAP, FILE, and EXT-MS-WIN-SESSION USERMGR -l1-1-0.dll many similar to this are unavailable. I even tried to repair the visual studio it didn't work. Is there any idea how to go about it
0x0000007b sounds familiar to me.
Most likely that is due to 32/64 bit library mixture you are linking with.
Either you are building for x64 and linking with a win32 external library or vice versa.
In your Visual Studio project settings separately configure platform architectures you are compiling for and then you can choose the profile which you are actually compiling for.
Visual Basic 6.0 IDE can not recognize DLL in subfolders
My VB6 project is using FlexNet technology. I have a DLL which is built by .NET.
This DLL is using two others dlls and I put all of them into sub folders, for example Dongle/lmgract.dll and Harddisk/lmgract.dll
I registered tlb file successfully. And then I added reference to my DLL.
When I make an executable file, it runs well without any error. Nonetheless I tried to run the Visual Basic 6.0 Project via Visual Basic IDE and got the error:
"-1Unable to load DLL 'Dongle\lmgract.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)0false". It means that Visual Basic 6.0 IDE can not recognize the directory path of subfolder.
This error still occurs when I copied the Dongle folder into Windows\System32 or Windows\SysWOW64 or the directory of Visual Studio 6.0 IDE (C:\Program Files (x86)\Microsoft Visual Studio\VB98)
I could fix this error by setting Environment Variables but my boss does not like this approach.Please help me another way to resolve this issue. Thanks.
After registering (regasm.exe) your .net DLLs in their normal subfolders, when running in the vb6 ide you also have to copy the DLLs to program files\microsoft visual studio\vb98 (program files(x86) for win 64, of course); copy the files themselves not the subfolders, also don't register the files there.
So, I've got a Visual Studio 2013 solution with two Visual C++ projects - one of them is a ComServer, which generates a .dll file, and the other is the ComClient, which relies on the ComServer.dll.
Now, when I try to register the ComServer.dll file by invoking regsvr32.exe (both from c:\Windows\System32 and c:\Windows\SysWOW64), a dialog box pops up with the following error:
"Debugging information for regsvr32.exe not found. Cannot find or open the pdb file."
The project property for ComServer.dll is as follows:
ComServer property pages ->Configuration properties ->Debugging: Command:"C:\Windows\System32\regsvr32.exe"
Command Arguments: $(TargetPath).
Is there a fix, or any possible workaround to this issue ? (I'm new to the whole COM / Windows programming scene).
The ComServer.dll contains the following functions:
DllRegisterServer
DllUnregisterServer
DllGetClassObject
The desktop software (.Net 4.0, compiled under Visual Studio 2010, target: x86) I'm developing is shipping with System.Data.SQLite (1.0.86 for x86, from system.data.sqlite.org*) for the first time.
On the development machine (And every other machine where the System.Data.SQLite-installer has run), everything works correctly.
On the testing machine however, after installation (a standard MSI setup created with the Visual Studio Installer) launching the application and showing the splash screen, before showing the GUI, the application creates an exception with the error:
System.IO.FileNotFoundException: Could not load file or assembly 'System.Data.SQLite.dll' or one of its dependencies.
The mentioned file itself is found in the application directory (correct version), along with all the other referenced DLLs.
I assume this works on the development machines because of the setup option 'Install images'. I didn't install SQLite in the GAC. The application project is directly referencing the pre-build System.Data.SQLite.dll with local copy set to true.
Are there any dependencies I'm not seeing?
Or is it a missing Microsoft Visual C++ Runtime Library (Not present in the application directory)?
Or a missing SQLite.Interop.DLL (Not present in the application directory)?
How could I fix those?
= The installer I've used: http://system.data.sqlite.org/downloads/1.0.86.0/sqlite-netFx40-setup-bundle-x86-2010-1.0.86.0.exe
Ensure that you have the latest Microsoft Visual C++ 2010 Redistributable Package installed.
http://www.microsoft.com/en-gb/download/details.aspx?id=5555
Why? The sqlite DLL has some unmanaged code embedded in it that is run directly from the assembly at runtime. This manifested for me as a bad image format exception but you never know!
I have the following scenario:
Visual Studio 2010 solution with one WPF-project, output file is "Tool.exe"
Eclipse Shared Library project, output file is "Tool.dll"
I place the dll in the same folder as the exe and then I try to debug using Visual Studio; but I get the following error:
Error while trying to run project: Could not load file or assembly 'Tool' or one of its dependencies. The module was expected to contain an assembly manifest.
I have managed to find a solution to the problem, rename the dll, apparently the exe and dll cannot have the same name. My question is, why is this error occuring in the first place? Why does the name of the dll affect Visual Studio? The error occurs before even trying to pinvoke the dll. If I run my application without Visual Studio it works perfectly, but I want to be able to debug it of course.
Right now renaming the dll is plan B, but before I do that I would like to know if there is anything else I can do to fix this problem?
Thanks in advance.
I found simple steps to solve this error.
1- change your windows.
2- install Symantec Endpoint Protection Client 12.1.6318.6100 x32 or x64 bit.
You can geting it software(32 bit) from link: (ftp://192.168.168.215/Public/Antivirus/Symantec/Symantec Endpoint Protection Client 12.1.6318.6100 x86.rar)
drag and drop it to your software(IE ,....) to work.
3- install all driver on your computer.
4- install Visual studio.
End