I am having a hard time loading up PrEngineCE.dll for Visual Basic 2005
I am currently trying to update the Visual Basic that I have to the Visual Basic 2005 that can be used for Handheld Symbol MC50. With this process, I have a problem loading up the PREngineCE.dll for Visual Basic 2005. The version for the dll file is 2.9.4.0.
I did the following steps to load up the dll file into the library:
– I manually added the dll file to the Reference Tab in the Solution Explorer.
However, I get an error "Please make sure that the file is accessible, and that it is a valid assembly or COM component."
I am wondering if the problem is with the version of the dll file. Or are there other issues that I am not aware of?
Can someone share their knowledge when it comes to these things?
Thank you!
Microsoft Visual Studio
A reference to 'C:Documents and Settingsa.lildarryDesktopLinePrinterLinePrinterlineptr.dll' could not be added.
Please make sure that the file is accessible and that it is a valid assembly or COM component.
Answered By
icore
0 points
N/A
#136508
Unable to load PrEngineCE.dll in Visual Basic 2005
You have do these things:-
First Register DLL Correctly
—————————————————————–
To do that where your dll exits register it like that:
1)Go to dos
2)Type= "regsvr32 PrEngineCE.dll" with out double comma
if your dll exists in other directory then give path also
"regsvr32 c:pathPrEngineCE.dll"
——————————————————————
Second to do:
"you have to add a reference to Intermec.Print.LinePrinter.CF2.dll
(C:Program Files (x86)IntermecDeveloper LibraryDot NET AssembliesCF 2.0Intermec.Print.LinePrinter.CF2.dll)"
Unable to load PrEngineCE.dll in Visual Basic 2005
Hi There,
You could have perform sign up DLL Appropriately. But if it is accomplished appropriately then you have to check out your Microsoft DLL. That databases all the DLL records utilized by widespread Microsoft products.
You can search through title as well as merchandise to discover which usually records are essential by way of a unique merchandise as well as which usually file was installed by way of a particular merchandise.
This can be good info for resolving model conflicts with DLL records. You can search for Procedure bands (from House windows Task Manager) as well as DLL file bands and obtain much more information about the offending file.
Hope you can solve your problem.
