UNSOLVED
C
CodeHunter1
5 Posts
0
3567
January 11th, 2010 10:00
.NET Wrapper compilation error and FPDLL.exe failed to load
Hi,
I am really having a problem in working with the .NET wrapper project and its samples and the FPSDK.dll
I have tried to compile the .NET Wrapper solution that I downloaded from http://sourceforge.net/projects/cosi-dot-net/ (FPApi.NET.3.2P4-Nov2009.zip)
When I build the project, its failing with the error 'The command "cp FPSDK.dll ..\..\" exited with the code 9009', but it was creating the FPSDK.dll and FPSDK.pdb under ...\FPSDK\bin\Debug. I copied these .dll and .pdb to .\bin folder of a new visual studio project that I have created for testing Centera SDK.
When I build this project, its throwing me an error that it failed to load FPDll.exe.
I am struggling with this error and I have tried almost all the solutions that I found when googled.
I followed all the steps in http://devcity.net/Articles/340/1/article.aspx, but that also didt work out. I have Perl PATH variables also set.
One more thing, the Samples.sln that comes bundled with the wrapper code also do not compiled. It also giving me error in compilation.
Error screens are attached.
Please help me in resoving this issue.
Thanks in advance
726
0
Posted January 12th, 2010 07:00
Sure - but the DLL was being compiled correctly, so you need to ensure that the references to it within the samples are correct. You did not do this.726
0
Posted January 12th, 2010 07:00
hmm. when I build the wrapper solution, it failed with a message, 'the command "cp FPSDK.dll ..\..\.." exited with the code 9009. but it generated the FPSDK.dll and FPSDK.pdb under the root directory. so I have referenced that new DLL to the sample solution.but again build errors.
I am using 2008 Visual Studio
726
0
Posted January 12th, 2010 07:00
Very strange. The failure of the Post Build script infers that something else may be wrong in your environment, as all this does is simply copy it from the relevant build directory (Debug or Release) up the the "root" of the project directory structure. This allows the sampes to use it with a single porint of reference independent of the build mode.
When you compile the samples, what errors are you seeing?
726
0
Posted January 12th, 2010 07:00
I am not new to .NET. If I need to reference the compiled DLL to the sample solution, first I should get the DLL from the wrapper solution. That was failing.
726
0
Posted January 12th, 2010 08:00
This is the build error screen. Remember, i gave the FPSDK.dll reference.
726
0
Posted January 12th, 2010 08:00
From those errors, it is clear that the FPSDK.dll reference is not being successfully found in the project. I suggest you try and add it manually - you should then be able to resolve those classes.726
0
Posted January 12th, 2010 08:00
So are you able to open it in Object Browser and view the class methods etc? If that is the case then they should be usable in your code.726
0
Posted January 12th, 2010 08:00
I referenced the DLL manually only.
137
0
Posted January 19th, 2010 13:00
Regarding the failure of the build Post Event, do you have cygwin (or similar) installed and available on your path?
If not, then you should change the "cp" command to use the regular DOS "copy" command. I will include this change in a future release.
gstuartemc
2 Intern
•
417 Posts
726
0
Posted January 12th, 2010 05:00
I presume from your difficulties that you are very new to .NET. The generated DLL is referenced by the sample programs in the solution, and needs to be in the root directory - that is where the post build event attempts to copy it, and that is where the sample solution reference requires it to be.
I do not know why the copy step is failing, but if you copy it manually to this location you should have no problems.
Are you using Visual Studio 2008?