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.
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.
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?
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.
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.
gstuartemc
2 Intern
•
417 Posts
0
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?
gstuartemc
2 Intern
•
417 Posts
0
January 12th, 2010 07:00
CodeHunter1
5 Posts
0
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
gstuartemc
2 Intern
•
417 Posts
0
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?
CodeHunter1
5 Posts
0
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.
CodeHunter1
5 Posts
0
January 12th, 2010 08:00
This is the build error screen. Remember, i gave the FPSDK.dll reference.
gstuartemc
2 Intern
•
417 Posts
0
January 12th, 2010 08:00
gstuartemc
2 Intern
•
417 Posts
0
January 12th, 2010 08:00
CodeHunter1
5 Posts
0
January 12th, 2010 08:00
I referenced the DLL manually only.
gstuartemc
2 Intern
•
417 Posts
0
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.