Client API 7.0 missing entities

[Thomas Linder Puls]

As a spike test to upgrading to version 7, I have tested the Client API, which we use. And found that none of the two included projects VaultClientIntegrationLibCode and CommandLineClientCode can be compiled.

Both have references to a number of non-included entities.

VaultClientIntegrationLibCode

• ..\VaultClientNetLib\VaultClientNetLib.csproj
• ..\VaultClientOperationsLib\VaultClientOperationsLib.csproj
• ..\VaultLib\VaultLib.csproj

CommandLineClientCode

• ..\Dragnet\MantisLib\MantisLib.csproj
• ..\VaultClientIntegrationLib\VaultClientIntegrationLib.csproj
• ..\VaultClientNetLib\VaultClientNetLib.csproj
• ..\VaultClientOperationsLib\VaultClientOperationsLib.csproj
• ..\VaultLib\VaultLib.csproj
• ..\VCDiff\VCDiff.csproj

[Thomas Linder Puls]

I also think the target .net framework should be version 4 (rather than 2).

[jclausius]

Thanks for the report. The APIs are meant as sample, and must have been left behind for some time as the Vault 6 API samples have the same problem.

To fix:

a) In each project, replace all "missing" references with the DLLs in the parent directory. For example, VaultLib.DLL should be referencing the DLL in the top level directory. One other caveat is there was a rename and Mantis.dll should be using DragnetLib.dll.

b) You can remove the .snk file for compilation purposes.

c) For backwards compatibility, leave the projects as .NET 2.0.

I then saved the projects and was able to recompile successfully under Visual Studio 2010 and Visual Studio 2012.

[Thomas Linder Puls]

Thank you. I guessed part of this myself.

Furthermore, the reason that I mention version 4 of the framework was because I got some warnings that some of the mentioned DLL's was target at version 4. However, it turned out that some of the references are not really need and when removed the warnings disappear.