Nikita-tech-writer commented on a change in pull request #8760:
URL: https://github.com/apache/ignite/pull/8760#discussion_r572048954



##########
File path: docs/_docs/net-specific/net-deployment-options.adoc
##########
@@ -17,35 +17,47 @@
 == Overview
 
 Apache Ignite.NET consists of .NET assemblies and Java jar files. The .NET 
assemblies are referenced by your project and
-are copied to an output folder during the build automatically. The JAR files 
should be copied manually.
+are copied to an output folder during the build automatically. The JAR files 
can be handled automatically or manually, depending on the approach.
 Ignite.NET discovers them via the `IgniteHome` or `JvmClasspath` settings.
 
 This page introduces several most-commonly used deployment options of 
Ignite.NET nodes.
 
-== Full Binary Package Deployment
-
-* Copy the https://ignite.apache.org[whole Ignite distribution package, 
window=_blank] along with your application
-* Set the `IGNITE_HOME` environment variable or 
`IgniteConfiguration.IgniteHome` setting to point to that folder
-
 == NuGet Deployment
 
-The post-build event is updated automatically during the Ignite.NET NuGet 
package installation to copy jar files to
-`Libs` folder in the output directory (see link:quick-start/dotnet[Getting 
Started]).
-Make sure to include that `Libs` folder when distributing your binaries.
+`Apache.Ignite` NuGet package includes a `lib` folder with all the required 
jar files. This folder has 
+`<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>` build action, 
and is copied automatically to the output directory

Review comment:
       ```suggestion
   the `<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>` build 
action, and is copied automatically to the output directory
   ```




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to