Worst: 1<\/td>\n <\/tbody>\n<\/table>\n","avg_line_length":34.5793650794,"max_line_length":123,"alphanum_fraction":0.5120495754}
-{"size":1083,"ext":"md","lang":"Markdown","max_stars_count":null,"content":"The MIT License (MIT)\n\nCopyright (c) 2019 Karl Schellenberg\n\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and\/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.","avg_line_length":120.3333333333,"max_line_length":460,"alphanum_fraction":0.8051708218}
-{"size":12769,"ext":"md","lang":"Markdown","max_stars_count":1.0,"content":"---\n# required metadata\n\ntitle: Create custom localized error messages for payment terminal extensions\ndescription: This topic explains how to create custom error messages for payment terminal extensions.\nauthor: Reza-Assadi\nmanager: AnnBe\nms.date: 07\/20\/2018\nms.topic: article\nms.prod: \nms.service: dynamics-365-retail\nms.technology: \n\n# optional metadata\n\n# ms.search.form: \n# ROBOTS: \naudience: Developer\n# ms.devlang: \nms.reviewer: rhaertle\nms.search.scope: Operations, Retail\n# ms.tgt_pltfrm: \nms.custom: \nms.search.region: Global\nms.search.industry: Retail\nms.author: rassadi\nms.search.validFrom: 2018-07-20\nms.dyn365.ops.version: AX 7.0.0, Retail July 2017 update\n\n---\n\n# Create custom localized error messages for payment terminal extensions\n\n[!include[banner](..\/includes\/banner.md)]\n\nThis topic explains how to create custom localized error messages for payment terminal extensions. These custom error messages are most often used so that the payment terminal can give the cashier who is using the point of sale (POS) terminal relevant information about why a specific payment was unsuccessful. For example, the external payment terminal or gateway might return unique identifiers (such as reference numbers or transaction identifiers) that are relevant for troubleshooting with the payment provider.\n\n## Key terms\n\n| Term | Description |\n|---|---|\n| Payment connector | An extension library that is written to integrate the POS with a payment terminal. |\n\n## Overview\nThe remaining sections in this topic describe the following steps for creating custom localized error messages for payment terminal extensions:\n\n- **[Create custom error messages](#create-custom-error-messages)** \u2013 This section explains how to create custom error messages in the payment connector that can be returned and shown in the POS.\n- **[Create localized error messages](#create-localized-error-messages)** \u2013 This section explains how to localize the error messages in the payment connector that are returned and shown in the POS.\n\n## Create custom error messages\nTo trigger a custom error message in the POS, you must set the appropriate error in the **Errors** property of the **paymentInfo** object that is passed to the **AuthorizePaymentTerminalDeviceResponse** object. Specifically, you must set the **isLocalized** parameter on the constructor of the **PaymentError** object to **true** to force the POS to use the custom error message instead of the built-in error message for a declined payment.\n\n``` csharp\nnamespace Contoso.Commerce.HardwareStation.PaymentSample \n{ \n \/\/\/ \n \/\/\/ Simulator<\/c> manager payment device class.\n \/\/\/ <\/summary>\n public class PaymentDeviceSample : INamedRequestHandler\n {\n \/\/\/ \n \/\/\/ Gets the collection of supported request types by this handler.\n \/\/\/ <\/summary>\n public IEnumerable SupportedRequestTypes\n {\n get\n {\n return new[]\n {\n typeof(AuthorizePaymentTerminalDeviceRequest),\n ...\n };\n }\n }\n\n \/\/\/ \n \/\/\/ Executes the payment device simulator operation based on the incoming request type.\n \/\/\/ <\/summary>\n \/\/\/ The payment terminal device simulator request message.<\/param>\n \/\/\/ Returns the payment terminal device simulator response.<\/returns>\n public Response Execute(Microsoft.Dynamics.Commerce.Runtime.Messages.Request request)\n {\n ThrowIf.Null(request, nameof(request));\n Type requestType = request.GetType();\n Response response;\n if (requestType == typeof(AuthorizePaymentTerminalDeviceRequest))\n {\n response = this.AuthorizePayment((AuthorizePaymentTerminalDeviceRequest)request);\n }\n else if (...)\n {\n ...\n }\n else\n {\n throw new NotSupportedException(string.Format(CultureInfo.InvariantCulture, \"Request '{0}' is not supported.\", request));\n }\n return response;\n }\n\n \/\/\/ \n \/\/\/ Authorize payment.\n \/\/\/ <\/summary>\n \/\/\/ The authorize payment request.<\/param>\n \/\/\/ The authorize payment response.<\/returns>\n public AuthorizePaymentTerminalDeviceResponse AuthorizePayment(AuthorizePaymentTerminalDeviceRequest request)\n {\n ThrowIf.Null(request, \"request\");\n ...\n\n \/\/ Assuming the external payment terminal\/gateway returned a decline and a reference number.\n \/\/ Construct the custom error message and set the payment error on the 'paymentInfo' object set\n \/\/ on the response.\n PaymentInfo paymentInfo = new PaymentInfo();\n bool isLocalized = true;\n string errorMessage = string.Format(\"The payment was declined. Reference number '{0}'.\", referenceNumber);\n PaymentError paymentError = new PaymentError(ErrorCode.Decline, errorMessage, isLocalized);\n paymentInfo.Errors = new PaymentError[] { paymentError };\n return new AuthorizePaymentTerminalDeviceResponse(paymentInfo);\n }\n }\n}\n```\n\nThe following illustration shows how the custom error message appears in the POS.\n\n\n\n## Create localized error messages\n\n### Create resource files for each locale\nTo return localized error messages from the payment connector to the POS, you must create localized resource files for each locale that you plan to support. To create a resource file, follow these steps.\n\n1. In Microsoft Visual Studio, right-click the connector project (or a subfolder, as required), and then select **Add \\> New Item**.\n2. In the new **Add New Item** dialog box, select **Visual C# Items** in the left pane and **Resource File** in the center pane.\n\n \n\nNote that a culture-specific postfix (for example, **en-us**) is required in the file name of every resource file that you create, so that localized satellite assemblies can be generated.\n\nWhen you've finished, the following resource files should be present in your project. Although the following illustration shows only one extra locale (**en-us**), you can add support for as many locales as you require.\n\nMake sure that a culture-neutral resources file (**Messages.resx** in this example) is defined. This file is used as a fallback if the file for a specific culture is missing.\n\n\n\nYou must also make sure that the correct properties are set for the resource files in Visual Studio, as shown in the following illustration.\n\n\n\n### Create custom localized error messages\nEvery resource file must contain every error message that you want to customize and localize. The following illustration shows an example of a resource file. Notice that the **CustomPaymentConnector_Decline** entry is referenced in the code to retrieve the appropriate message for a specific locale. Every resource file for every locale should have an identical set of localized messages.\n\n\n\n### Load the localized message in the connector code\nThe following example shows how you can use the resource files that you created earlier in your payment connector code to load a localized message. The process consists of two steps:\n\n1. Make sure that **terminalSettings** is retrieved during the **OpenPaymentTerminalDeviceRequest** request, to access the locale for the request.\n2. During the **AuthorizePaymentTerminalDeviceRequest** call (or equivalent calls), use the **Locale** property on **terminalSettings** to retrieve the correct resource file for the localized message.\n\n> [!NOTE]\n> The following example has been significantly simplified to show the mechanics of loading localized messages during the runtime of your payment connector code. However, we recommend that you introduce a new set of classes to manage loading of the appropriate resource file.\n\n``` csharp\nnamespace Contoso.Commerce.HardwareStation.PaymentSample \n{ \n \/\/\/ \n \/\/\/ Simulator<\/c> manager payment device class.\n \/\/\/ <\/summary>\n public class PaymentDeviceSample : INamedRequestHandler\n {\n \/\/ Cached version of the terminal settings retrieved during the OpenPaymentTerminalDeviceRequest call.\n private SettingsInfo terminalSettings;\n\n \/\/ Resource manager to retrieve localized messages.\n private ResourceManager messagesResourceManager;\n\n \/\/\/ \n \/\/\/ Initializes a new instance of the class.\n \/\/\/ <\/summary>\n public PaymentDeviceSample()\n {\n this.messagesResourceManager = new ResourceManager(\"Contoso.Commerce.HardwareStation.PaymentSample.PaymentDeviceSample .Resources.Messages\", typeof(PaymentDeviceSample).GetTypeInfo().Assembly);\n }\n\n \/\/\/ \n \/\/\/ Gets the collection of supported request types by this handler.\n \/\/\/ <\/summary>\n public IEnumerable SupportedRequestTypes\n {\n get\n {\n return new[]\n {\n typeof(OpenPaymentTerminalDeviceRequest),\n typeof(AuthorizePaymentTerminalDeviceRequest),\n ...\n };\n }\n }\n\n \/\/\/ \n \/\/\/ Executes the payment device simulator operation based on the incoming request type.\n \/\/\/ <\/summary>\n \/\/\/ The payment terminal device simulator request message.<\/param>\n \/\/\/ Returns the payment terminal device simulator response.<\/returns>\n public Response Execute(Microsoft.Dynamics.Commerce.Runtime.Messages.Request request)\n {\n ThrowIf.Null(request, nameof(request));\n Type requestType = request.GetType();\n Response response;\n if (requestType == typeof(OpenPaymentTerminalDeviceRequest))\n {\n response = this.Open((OpenPaymentTerminalDeviceRequest)request);\n }\n else if (requestType == typeof(AuthorizePaymentTerminalDeviceRequest))\n {\n response = this.AuthorizePayment((AuthorizePaymentTerminalDeviceRequest)request);\n }\n else if (...)\n {\n ...\n }\n else\n {\n throw new NotSupportedException(string.Format(CultureInfo.InvariantCulture, \"Request '{0}' is not supported.\", request));\n }\n return response;\n }\n\n \/\/\/ \n \/\/\/ Open the payment terminal.\n \/\/\/ <\/summary>\n \/\/\/ The open request.<\/param>\n \/\/\/ The open response.<\/returns>\n private Response Open(OpenPaymentTerminalDeviceRequest request)\n {\n this.terminalSettings = request.TerminalSettings;\n ...\n }\n\n \/\/\/ \n \/\/\/ Authorize payment.\n \/\/\/ <\/summary>\n \/\/\/ The authorize payment request.<\/param>\n \/\/\/ The authorize payment response.<\/returns>\n public AuthorizePaymentTerminalDeviceResponse AuthorizePayment(AuthorizePaymentTerminalDeviceRequest request)\n {\n ...\n\n \/\/ Assuming the external payment terminal\/gateway returned a decline and a reference number. Construct \n \/\/ the custom error message and set the payment error on the 'paymentInfo' object set on the response.\n PaymentInfo paymentInfo = new PaymentInfo();\n CultureInfo cultureInfo = new CultureInfo(this.terminalSettings.Locale);\n string localizedString = this.messagesResourceManager.GetString(\"CustomPaymentConnector_Decline\", cultureInfo);\n string errorMessage = string.Format(localizedString, referenceNumber);\n bool isLocalized = true;\n PaymentError paymentError = new PaymentError(ErrorCode.Decline, errorMessage, isLocalized);\n paymentInfo.Errors = new PaymentError[] { paymentError };\n return new AuthorizePaymentTerminalDeviceResponse(paymentInfo);\n }\n }\n}\n```\n","avg_line_length":48.0037593985,"max_line_length":516,"alphanum_fraction":0.6890907667}
-{"size":710,"ext":"md","lang":"Markdown","max_stars_count":584.0,"content":"---\ntitle: EndStyle Property\nms.prod: excel\napi_name:\n- Excel.EndStyle\nms.assetid: 2d12c0c5-7c48-41c0-b270-d5cf70eb7d47\nms.date: 06\/08\/2017\n---\n\n\n# EndStyle Property\n\nReturns or sets the end style for the error bars. Read\/write **XlEndStyleCap**.\n\n\n## \n\n\n\n|XlEndStyleCap can be one of these XlEndStyleCap constants.|\n| **xlCap**|\n| **xlNoCap**|\n _expression_. **EndStyle**\n\n _expression_ Required. An expression that returns one of the objects in the Applies To list.\n\n\n## Example\n\nThis example sets the end style for the error bars for series one. The example should be run on a 2-D line chart that has Y error bars for the first series.\n\n\n```\nmyChart.SeriesCollection(1).ErrorBars. EndStyle = xlCap\n\n```\n\n\n","avg_line_length":18.2051282051,"max_line_length":156,"alphanum_fraction":0.7295774648}
-{"size":7197,"ext":"md","lang":"Markdown","max_stars_count":1.0,"content":"# Wire1 (1-wire) Level II driver\n\n**Available for**: Linux (Kernel v2.6.29+)\n\n1-Wire sensors especially the [DS18B20](https:\/\/datasheets.maximintegrated.com\/en\/ds\/DS18B20.pdf) temperature sensor is extremely popular in the hobby community for it's ease of use. Also the possibility to have many sensors connected on one 1-wire bus is a big plus for this sensor.\n\nThe wire1 driver is built to take advantage of the 1-wire support that is available in the Linux kernel from version 2.6.29.\n\nThis driver reports temperature from any number of DS18B20 temperature sensors connected to a Linux system. The reported event is [CLASS1.MEASUREMENT, Type=6 temperature](http:\/\/docs.vscp.org\/spec\/latest\/#\/.\/class1.measurement#type6).\n\n**Driver Linux**: vscpl2_wire1.so\n\nThe configuration string has the following format\n\n NumberOfSensors\n\n##### NumberOfSensors\n\nThe parameter *NumberOfSensors* (which is optional) is the number of sensors the driver should report data from. This value can also be available as a VSCP daemon variable and if both are present the VSCP daemon variable will be used. Default is 1. \n\n | Variable name | Type | Description | \n | ------------- | ---- | ----------- | \n | _numberofsensors | integer | NumberOfSensors is the number of sensors the driver should report data from. | \n | _path[0..n] | string | Path to the lm-sensor data file. | \n | _guid[0..n] | guid | GUID to use when the data for the sensor is reported. If no GUID is used the reserved GUID for 1-wire with the unique id for the sensor will be used. | \n | _interval[0..n] | integer | Sample interval in seconds for events. Default is 30 seconds. | \n | _unit[0..n] | integer | Unit use. Allowed values 0=Kelvin,1=Celsius or 2=Fahrenheit. Default is 2 (Celsius). | \n | _index[0..n] | integer | Measurement index 0-7. Default is 0. | \n | _coding[0..n] | integer | Message coding 0-2. Default is 0. Allowed values 0=Normalized integer, 1=string, 2=floating point. | \n\nThe full variable name is built from the name you give the driver (prefix before _variablename) in vscpd.conf. So in the examples below the driver have the name **wire1** and the full variable name for the **_numberofsensors** will thus be\n\n wire11_numberofsensors\n\nIf you have another diver and name it **wire2** it will therefore instead request variable **wire2_numberofsensors**\n\nIf your driver name contains spaces, for example \u201cname of driver\u201d it will get a prefix that is \u201cname_of_driver\u201d. Leading and trailing spaces will be removed. \n\n##### Example of vscpd.conf entry for the wire1 driver.\n\n```xml\n\n wire1<\/name>\n \/usr\/local\/lib\/vscpl2_wire1.so<\/path>\n 2<\/config>\n 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00<\/guid>\n<\/driver>\n```\n\nExample for variable configuration. In this sample the temperature from two DS18B20 temperature sensors is reported every ten seconds.\n\n```xml\n\n\n\n\n\n\twire1_numberofsensors<\/name> \t\n\t2<\/value> \n<\/variable>\n\n\n\n\n\n\n\n\twire1_interval0<\/name> \t\n\t10<\/value> \n<\/variable>\n\n\n\n\n\n\n`wire1_path0`<\/name>\n`\/sys\/bus\/w1\/devices\/28-00000548476b\/w1_slave`<\/value>\n<\/variable>\n\n\n\n\n\n\n\n\n\twire1_interval1<\/name> \t\n\t10<\/value> \n<\/variable>\n\n\n \t\n\n\n\t\n\twire1_path1<\/name> \t\n\t\/sys\/bus\/w1\/devices\/28-000003e71198\/w1_slave<\/value> \n<\/variable>\n\n```\n\n\n----\n\n# Using the Level II wire1 driver\n\nThe 1-wiew support is yet quite limited on Linux systems and at the moment only memory and temperature devices are really supported. The wire1 driver currently just support temperature readings.\n\n## Loading the kernel driver\n\n**Info**\n\n* https:\/\/www.kernel.org\/doc\/Documentation\/w1\/w1.generic\n* How to configure - https:\/\/how-to.wikia.com\/wiki\/How_to_configure_the_Linux_kernel\/drivers\/w1\n\nFor the 1-wire subsystem to support you need to first add a master driver for the 1-wire bus. Popular is the now discontinued DS2490 USB adapter. To get a working system reading temperatures if you have this device you need to load the needed modules\n\n modprob ds2490\n modprob w1-term\n\nIf you have some other interface than DS2490 search for which driver to use. \n\nIf you have a Raspberry Pi you can instead use GPIO4 (pin 7) which have support for 1-Wire. You have to add a 4k7 pull up resistor to 3.3V yourself.\n\nOn the latest kernel builds on Raspberry Pi you need to add \"dtoverlay=w1-gpio\" to \/boot\/config.txt for any of this to work! \n\nTo get it all working\n\n modprob w1-gpio\n modprob w1_therm\n\nAfter this is done temperature sensor will be visible in the folder *\/sys\/bus\/w1\/devices* \n\nThe id will start with the [1-wire family code](https:\/\/github.com\/owfs\/owfs-doc\/wiki\/1Wire-Device-List) which is **10** for 18S20 and **28** for 18B20.)\n\nFor exampel\n\n \/sys\/bus\/w1\/devices\/10-00080192afa8\/w1_slave\n\nWill show have a file content of where t=4937 is the temperature * 1000\n\n 0a 00 4b 46 ff ff 0d 10 79 : crc=79 YES\n 0a 00 4b 46 ff ff 0d 10 79 t=4937 \n\nThis is the file that is read by the wire1 driver and sent to the VSCP subsystem.\n\nYou way want to add the modules to **\/etc\/modules** so that they load automatically the next time you start your system.\n\n# Hooking up a Ds18B20 to Raspberry Pi\n\n\n\nOn this picture a standard DS18B20 and a water proof sensor with a DS18B20 is connected to the Raspberry Pi. The connection is very easy.\n\n\n* Fetch power from pin 1 - 3.3V\n\n* Fetch ground from pin 6.\n\n* The reserved 1-Wire pin is GPIO4 which is on pin 4.\n\nA good pin out diagram can be found here \n\nClick to see in full size.\n\nA wiring diagram is here \n\nNote the 4k7 pullup that should be connected from 3.3V to the data line of the sensor.\n\nTo be complete we include the DS18B20 pin out also\n\n\n\n[filename](.\/bottom_copyright.md ':include')\n","avg_line_length":40.4325842697,"max_line_length":283,"alphanum_fraction":0.6733361123}
-{"size":450,"ext":"md","lang":"Markdown","max_stars_count":null,"content":"+++\ntitle = \"A roadmap for global synthesis of the plant tree of life\"\ndate = 2018-01-01\nauthors = [\"Wolf L Eiserhardt\", \"Alexandre Antonelli\", \"Dominic J Bennett\", \"Laura R Botigu\u00e9\", \"J Gordon Burleigh\", \"Steven Dodsworth\", \"Brian J Enquist\", \"F\u00e9lix Forest\", \"Jan T Kim\", \"Alexey M Kozlov\", \" others\"]\npublication_types = [\"2\"]\nabstract = \"\"\nfeatured = false\npublication = \"*American journal of botany*\"\ntags = [\"phylogenetics\", \"supersmartr\"]\n+++\n\n","avg_line_length":37.5,"max_line_length":213,"alphanum_fraction":0.6933333333}
-{"size":12700,"ext":"md","lang":"Markdown","max_stars_count":null,"content":"---\ntitle: \"<msmqTransport> | Microsoft Docs\"\nms.custom: \"\"\nms.date: \"03\/30\/2017\"\nms.prod: \".net-framework\"\nms.reviewer: \"\"\nms.suite: \"\"\nms.technology: \n - \"dotnet-clr\"\nms.tgt_pltfrm: \"\"\nms.topic: \"article\"\nms.assetid: 19d89f35-76ac-49dc-832b-e8bec2d5e33b\ncaps.latest.revision: 14\nauthor: \"Erikre\"\nms.author: \"erikre\"\nmanager: \"erikre\"\n---\n# <msmqTransport>\nCauses a channel to transfers messages on the MSMQ transport when it is included in a custom binding. \n \n \\ \n\\ \n\\ \n\\ \n\\ \n \n## Syntax \n \n```xml \n \n customDeadLetterQueue=\"Uri\" \n deadLetterQueue=\"Custom\/None\/System\" \n durable=\"Boolean\" \n exactlyOnce=\"Boolean\" \n manualAddressing=\"Boolean\" \n maxBufferPoolSize=\"Integer\" \n maxImmediateRetries=\"Integer\" \n maxPoolSize=\"Integer\" \n maxReceivedMessageSize=\"Integer\" \n maxRetryCycles=\"Integer\" \n....queueTransferProtocol=\"Native\/Srmp\/SrmpSecure\" \n rejectAfterLastRetry=\"Boolean\" \n retryCycleDelay=\"TimeSpan\" \n timeToLive=\"TimeSpan\" \n useActiveDirectory=\"Boolean\" \n useSourceJournal=\"Boolean\" \n useMsmqTracing=\"Boolean\" \n \n <\/msmqTransportSecurity> \n<\/msmqIntegration> \n``` \n \n## Attributes and Elements \n The following sections describe attributes, child elements, and parent elements. \n \n### Attributes \n \n|Attribute|Description| \n|---------------|-----------------| \n|customDeadLetterQueue|A URI that indicates the location of the per-application dead letter queue, where messages that have expired or failed to be delivered to the application are transferred.
For messages that require ExactlyOnce assurances (that is, `exactlyOnce` is set to `true`), this attribute defaults to the system-wide transactional dead-letter queue in MSMQ.
For messages that require no assurances (that is, `exactlyOnce` is set to `false`), this attribute defaults to `null`.
The value must use the net.msmq scheme. The default is `null`.
If `deadLetterQueue` is set to `None` or `System`, then this attribute must be set to `null`. If this attribute is not `null`, then `deadLetterQueue` must be set to `Custom`.| \n|deadLetterQueue|Specifies the type of dead letter queue to use.
Valid values include
- Custom: Custom deadletter queue. - None: No deadletter queue is to be used. - System: Use the system deadletter queue.
This attribute is of type DeadLetterQueue.| \n|durable|A Boolean value that specifies whether the messages processed by this binding are durable or volatile. The default is `true`.
A durable message survives a queue manager crash, while a volatile message does not. Volatile messages are useful when applications require lower latency and can tolerate occasional lost messages.
If `exactlyOnce` is set to `true`, the messages must be durable.| \n|exactlyOnce|A Boolean that specifies whether messages processed by this binding will be received exactly once. The default is `true`.
A message can be sent with or without assurances. An assurance enables an application to ensure that a sent message reached the receiving message queue, or if it did not, the application can determine this by reading the dead letter queue.
`exactlyOnce`, when set to `true`, indicates that MSMQ will ensure that a sent message is delivered to the receiving message queue once and only once, and if delivery fails, the message is sent to the dead letter queue.
Messages sent with `exactlyOnce` set to `true` must be sent to a transactional queue only.| \n|manualAddressing|A Boolean value that enables the user to take control of message addressing. This property is usually used in router scenarios, where the application determines which one of several destinations to send a message to.
When set to `true`, the channel assumes the message has already been addressed and does not add any additional information to it. The user can then address every message individually.
When set to `false`, the default Windows Communication Foundation (WCF) addressing mechanism automatically creates addresses for all messages.
The default is `false`.| \n|maxBufferPoolSize|A positive integer that specifies the maximum size of the buffer pool. The default is 524288.
Many parts of WCF use buffers. Creating and destroying buffers each time they are used is expensive, and garbage collection for buffers is also expensive. With buffer pools, you can take a buffer from the pool, use it, and return it to the pool once you are done. Thus the overhead in creating and destroying buffers is avoided.| \n|maxImmediateRetries|An integer that specifies the maximum number of immediate retry attempts on a message that is read from the application queue.. The default is 5.
If the maximum number of immediate retries for the message is attempted and the message is not consumed by the application, then the message is sent to a retry queue for retrying at some later point in time. If no retry cycles are specified, then the messages is either sent to the poison message queue, or a negative acknowledgment is sent back to the sender.| \n|maxPoolSize|A positive integer that specifies the maximum size of the pool. The default is 524288.| \n|maxReceivedMessageSize|A positive integer that specifies the maximum message size in bytes including headers. The sender of a message receives a SOAP fault when the message is too large for the receiver. The receiver drops the message and creates an entry of the event in the trace log. The default is 65536.| \n|maxRetryCycles|An integer that specifies the maximum number of retry cycles to attempt delivery of messages to the receiving application. The default is .
A single retry cycle attempts to deliver a message to an application a specified number of times. The number of attempts made is set by the `maxImmediateRetries` attribute. If the application fails to consume the message after the attempts at delivery have been exhausted, the message is sent to a retry queue. Subsequent retry cycles consist of the message being returned from the retry queue to the application queue to attempt delivery to the application again, after a delay specified by the `retryCycleDelay` attribute. The `maxRetryCycles` attribute specifies the number of retry cycles the application uses to attempt to deliver the message.| \n|queueTransferProtocol|Specifies the queued communication channel transport that this binding uses. Valid values are
- Native: Use the native MSMQ protocol. - Srmp: Use the Soap Reliable Messaging Protocol (SRMP). - SrmpSecure: Use the Soap Reliable Messaging Protocol Secure (SRMPS) transport.
This attribute is of type .
Since MSMQ does not support Active Directory addressing when using SOAP Reliable Messaging Protocol, you should not set this attribute to Srmp or Srmps when `u``seActiveDirectory` is set to `true`.| \n|rejectAfterLastRetry|A Boolean value that specifies what action to take for a message that has failed delivery after the maximum number of retries have been attempted.
`true` means that a negative acknowledgment is returned to the sender and the message is dropped; `false` means that the message is sent to the poison message queue. The default is `false`.
If the value is `false`, the receiving application can read the poison message queue to process poison messages (that is, messages that have failed delivery).
MSMQ 3.0 does not support returning a negative acknowledgment to the sender, so this attribute will be ignored in MSMQ 3.0.| \n|retryCycleDelay|A that specifies the time delay between retry cycles when attempting to deliver a message that could not be delivered immediately. The default is 00:10:00.
A single retry cycle attempts to deliver a message to a receiving application a specified number of times. The number of attempts made is specified by the `maxImmediateRetries` attribute. If the application fails to consume the message after the specified number of immediate retries, the message is sent to a retry queue. Subsequent retry cycles consist of the message being returned from the retry queue to the application queue to attempt delivery to the application again, after a delay specified by the `retryCycleDelay` attribute. The number of retry cycles is specified by `maxRetryCycles` attribute.| \n|timeToLive|A that specifies how long the messages are valid before they expired and are put in the dead-letter queue. The default is 1.00:00:00, which means 1 day.
This attribute is set to ensure that time-sensitive messages do not become stale before they are processed by the receiving applications. A message in a queue that is not consumed by the receiving application within the time interval specified is said to be expired. Expired messages are sent to special queue called the dead letter queue. The location of the dead letter queue is set with the `customDeadLetterQueue` attribute or to the appropriate default, based on assurances.| \n|UseActiveDirectory|A Boolean value that specifies whether queue addresses should be converted using Active Directory.
MSMQ queue addresses can consist of path names or direct format names. With a direct format name, MSMQ resolves the computer name using DNS, NetBIOS or IP. With a path name, MSMQ resolves the computer name using Active Directory. By default, the Windows Communication Framework (WCF) queued transport converts the URI of a message queue to a direct format name. By setting this attribute to `true`, an application can specify that the queued transport should resolve the computer name using Active Directory rather than DNS, NetBIOS, or IP.| \n|useMsmqTracing|A Boolean value that specifies whether messages processed by this binding should be traced. The default is `false`.
When tracing is enabled, report messages are created and sent to the report queue each time the message leaves or arrives at a Message Queuing computer.| \n|useSourceJournal|A Boolean value that specifies whether copies of messages processed by this binding should be stored in the source journal queue. The default is `false`.