PMS.NEXO30 4.3.0

.NET Framework 3.5 This package targets .NET Framework 3.5. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package PMS.NEXO30 --version 4.3.0                

                    
                

            
NuGet\Install-Package PMS.NEXO30 -Version 4.3.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="PMS.NEXO30" Version="4.3.0">
  <PrivateAssets>all</PrivateAssets>
  <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
</PackageReference>
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add PMS.NEXO30 --version 4.3.0                

                    
                

            
#r "nuget: PMS.NEXO30, 4.3.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install PMS.NEXO30 as a Cake Addin
#addin nuget:?package=PMS.NEXO30&version=4.3.0

// Install PMS.NEXO30 as a Cake Tool
#tool nuget:?package=PMS.NEXO30&version=4.3.0

Nexo Retailer v3.0 libraries supporting all messages defined inside the specifications.
     Nexo Retailer specs can be found at https://www.nexo-standards.org/standards/nexo-retailer-protocol, subscription is free of charges.

Product Compatible and additional computed target framework versions.
.NET Framework net35 is compatible.  net40 was computed.  net403 was computed.  net45 was computed.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 is compatible.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on PMS.NEXO30:

Package Downloads
PMS.NEXOSALE31

Nexo Retailer v3.1 easy to use client interface. Nexo Retailer specs can be found at https://www.nexo-standards.org/standards/nexo-retailer-protocol, subscription is free of charges.
PMS.NEXOSALE30

Nexo Retailer v3.0 easy to use client interface. Nexo Retailer specs can be found at https://www.nexo-standards.org/standards/nexo-retailer-protocol, subscription is free of charges.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
4.6.1 472 5/13/2022
4.6.0 426 5/12/2022
4.3.0 291 1/7/2022
4.1.0 360 10/29/2021
4.0.0 374 10/29/2021
3.4.0 353 6/25/2021
3.3.1 357 6/11/2021
3.3.0 350 6/11/2021
3.2.3 336 6/8/2021
3.2.2 320 6/8/2021
3.2.1 415 6/5/2021
3.2.0 379 5/31/2021
3.1.1 347 5/27/2021
3.1.0 332 5/20/2021

4.3.0
     - PMS.COMMON 5.5.5

     4.2.0 ** never released on nuget
     - PMS.COMMON 5.4.0
     - Enhanced NexoListener capabilities: added a mode to manage concurrent access to the same POI

     4.1.0
     - PMS.COMMON 5.2.4
     - Added (nexo)Listener application for .NET 5.0

     4.0.0
     - PMS.COMMON 5.1.0
     - Updated nexo retailer base classes

     3.4.1
     - Invalid files in previous package

     3.4.0
     - The whole system now supports XML and JSON to exchange with a POI
     - NexoSimulator and NexoBuilder have been updated to support both notations

     3.3.1
     - Fixed a bug in NexoType which crashed when seting a data without a name

     3.3.0
     - Reshaped the base classes for nexo 3.0 and 3.1 to fix some bugs with data being present in the XML though empty; the classes are now theoraticlly fully autonomous
     - Fixed an exception in NexoBuilder and NexoSimulator, sometimes when setting the name of a node (no explanation why this happens)

     3.2.3
     - Fixed a bug with all POIOriginalTransactionTimestamp not initialised normally

     3.2.2
     - Fixed a bug in NexoReversal
     - Removed NexoFinancial and NexoRefund to use only NexoPayment

     3.2.1
     - Changed assembly description

     3.2.0
     - NexoBuilder now properly handles array in a nexo structure
     - New ways to specify a message to send back in NexoSimulator (using SaleID, POIID, Name, all supporting wildcards now)
     - Moved to PMS.COMMON 4.1.1

     3.1.1
     - Allowed NexoBuilder and NexoSimulator to be deployed with the package

     3.1.0
     - Updated NewtonSoft.Json library
     - Creation of a specific PMS.NEXOXX package

     3.0.3
     - Fixed NexoBuilderXX to help reuse a valid XML string when pasting it (removing undesirable characters)
     - Added inside NexoSimulatorXX the possibility to ignore some SSL errors while trying to connect to a terminal over a 3G link (specific operation valid and tested only with 1 telco operator in France)

     3.0.2
     - Fixed a bug inside nexo 3.0 and 3.1
     - Update NexoBuilder and NexoSimulator to avoid crashing when editing a response
     - Updated NexoSimulator to allow sending RAW request and managed requests from the XML entry field
     - Added a NexoBuilder31 (for nexo 3.1)

     3.0.1
     - Fixed a bug which prevented the ReponseType to be set appropriately

     3.0.0
     - All Nexo classes are now safe, no way to have a null reference if using the classes
     - Nexo simulator now is fully operational to build any message
     - Nexo simulator POI simulation can be set nexo service by nexo service to reply with a pre-defined message stored in a json file
     - Nexo Retailer 4.0 is still NOT SUPPORTED though and will be in version 4.x
     - Nexo simumulator now can use a database to store its activity

     2.0.14
     - Moved to PMS.COMMON 3.0.9

     2.0.13
     - Nexo libraries are now divided in PMS.NEXO30 (Nexo 3.0), PMS.NEXO31 (Nexo 3.1) and PMS.NEXO35 (Nexo 3.0 running .NET 3.5)
     - Simulator exists now in 2 applications, 1 for Nexo 3.0 and 1 for Nexo 3.1

     2.0.12
     - Moved to PMS.NEXO 3.0.8 minimum
     - Added a new Retailer message builder application
     - Added new features to simulator (create any Retailer message using the builder, pre-connection settings,...)

     2.0.11
     - Fixed bugs linked to Nexo server database access + added scripts to create the database
     - Moved to PMS.NEXO 3.0.4
     - Full database support for Nexo server

     2.0.10
     - Moved to PMS.COMMON 3.02

     2.0.9
     - Fixed a bug inside NexoSimpleAmount type
     - Moved to PMS.COMMON 3.0.0

     2.0.8
     - Fixed a bug of an event using the wrong type inside NexoRetailerCient
     - Updated Nuget packages dependencies
     - NexoSimulator is now installed with the DLLs

     2.0.7
     - Updated DLL version to 2.0.7

     2.0.6
     - [Failed] Missed updating COMMON minimum version to 2.0.4

     2.0.5
     - Updated COMMON nuget package

     2.0.4
     - Changes events type inside NexoRetailerClient and fixed a bug with ThreadDispatcher not well closed in certain conditions

     2.0.3
     - Updated the interfaces + bug fixes (ProtocolVersion,...)

     2.0.2
     - Modified decimal types to double for easier COM compatibility

     2.0.1
     - Adjusted version number

     2.0.0
     - Removed WMI dependency

     1.1.0
     - Adjusted version number

     1.0.6
     - Fixed a bug in case of timeout receiving the answer from the server, using Response.xxx crashed the application

     1.0.5
     - Fixed a bug preventing timeout to be raised in case of SendRequestSync in NexoRetailerClient

     1.0.4
     - Updated NexoSimulator to handle client diconnections
     - A new OnDisconnect property has been added to NexoRetailerServerSettings for that matter

     1.0.3
     - Updates to project properties

     1.0.2:
     - Made objects available to COM

     1.0.1:
     - Added support for synchronous requests sent to the server.
     - Using this mode with the simulator always makes the request to timeout as the server tries to access the application main thread already waiting an answer.
     Synchronous requests can't therefore be used against the local server within the same simulator instance, but can be used if using 2 simulator instances communicating with each other.
     This is not a bug, the simulator done like that and modifying it is not the subject. You can still run 2 simulator instances to test these synchrounous requests.

     1.0.0:
     - Creation