From 780b92ada9afcf1d58085a83a0b9e6bc982203d1 Mon Sep 17 00:00:00 2001 From: Lorry Tar Creator Date: Tue, 17 Feb 2015 17:25:57 +0000 Subject: Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz. --- docs/installation/build_win_csharp.html | 67 +++++++++++++++++---------------- 1 file changed, 34 insertions(+), 33 deletions(-) (limited to 'docs/installation/build_win_csharp.html') diff --git a/docs/installation/build_win_csharp.html b/docs/installation/build_win_csharp.html index 7b7ce999..8e76277c 100644 --- a/docs/installation/build_win_csharp.html +++ b/docs/installation/build_win_csharp.html @@ -14,7 +14,7 @@
-

Library Version 11.2.5.3

+

Library Version 12.1.6.1

@@ -22,9 +22,7 @@ - +
Prev Chapter 5.  - Building Berkeley DB for Windows - Chapter 5.  Building Berkeley DB for Windows  Next
@@ -38,27 +36,28 @@
+

+ The C# support is built by a separate Visual Studio + solution and requires version 2.0 (or higher) of the .NET + platform. If the Berkeley DB utilities are required, build + Berkeley DB first following the instructions under Building Berkeley DB for 32 bit Windows or + Building Berkeley DB for 64-bit Windows. +

- The C# support is built by a separate Visual Studio solution and - requires version 2.0 (or higher) of the .NET platform. If the Berkeley - DB utilities are required, build Berkeley DB first following the - instructions under Building Berkeley DB for 32 bit Windows - or Building Berkeley DB for 64-bit Windows. -

+ To build the C# API in Visual Studio 2005/Visual Studio + 2008, the solution is + build_windows\BDB_dotnet.sln; in + Visual Studio 2010/Visual Studio 2012, the solution is + build_windows\BDB_dotnet_vs2010.sln. +

- To build the C# API in Visual Studio - 2005/Visual Studio 2008, the solution is - build_windows\BDB_dotnet.sln; in Visual Studio - 2010, the solution is - build_windows\BDB_dotnet_vs2010.sln. -

-

- By default, the solution will build the native libraries, the - managed assembly and all example programs. The NUnit tests need to - be built explicitly because of their dependence upon the NUnit - assembly. The native libraries will be placed in one of the - following subdirectories, depending upon the chosen configuration: -

+ By default, the solution will build the native + libraries, the managed assembly and all example programs. + The NUnit tests need to be built explicitly because of + their dependence upon the NUnit assembly. The native + libraries will be placed in one of the following + subdirectories, depending upon the chosen configuration: +

@@ -82,9 +81,10 @@

- The managed assembly and all C# example programs will be placed in one of - the following subdirectories, depending upon the chosen configuration: -

+ The managed assembly and all C# example programs will + be placed in one of the following subdirectories, + depending upon the chosen configuration: +

@@ -97,13 +97,14 @@
-

- The native libraries need to be locatable by the .NET platform, meaning - they must be copied into an application's directory, the Windows or - System directory, or their location must be added to the PATH - environment variable. The example programs demonstrate how to - programmatically edit the PATH variable. -

+

+ The native libraries need to be locatable by the .NET + platform, meaning they must be copied into an + application's directory, the Windows or System directory, + or their location must be added to the PATH environment + variable. The example programs demonstrate how to + programmatically edit the PATH variable. +

-- cgit v1.2.1