diff --git a/README.md b/README.md index 7078856ad74..0e51df541fb 100644 --- a/README.md +++ b/README.md @@ -44,7 +44,6 @@ As part of a full review the following should be done: * All links are relevant. No 3rd party links have redirects or 404s. * Are there any more links that can be added to improve the content * Content is correct up to and including the current released version - * Tags are correct * Summary and title is adequate * Update reviewed date in header, even if no changes were made. @@ -74,9 +73,6 @@ For example: title: Auditing Messages summary: Provides built-in message auditing for every endpoint. versions: '[4,)' -tags: -- Auditing -- Forwarding Messages related: - samples/custom-checks/monitoring3rdparty redirects: @@ -139,28 +135,6 @@ summary: Provides built-in message auditing for every endpoint. Optional. Used for the meta description tag (``) and displaying the search results. -### Tags - -``` -tags: -- Auditing -- Forwarding Messages -``` - -Optional. Used to flag the article as being part of a group of articles. - -Tags are rendered in the articles content with the full list of tags being rendered at [https://docs.particular.net/tags](https://docs.particular.net/tags). Untagged articles will be rendered here [https://docs.particular.net/tags/untagged](https://docs.particular.net/tags/untagged) - -Tags are interpreted in two ways. - -* For inclusion in URLs: - * Tag are lower case - * Spaces are replaced with dashes (`-`) -* For display purposes: - * Tags are lower case - * Dashes (`-`) are replaced with spaces - - ### Hidden ``` @@ -249,9 +223,6 @@ To mark a page as belonging to the [Particular Software Learning Path](https://p --- title: ServiceInsight Interaction summary: 'Using ServiceInsight Together' -tags: -- Invocation -- Debugging redirects: - servicecontrol/sc-si - servicecontrol/debugging-servicecontrol diff --git a/nservicebus/architecture/scaling.md b/nservicebus/architecture/scaling.md index ce374cb7789..cb96712601f 100644 --- a/nservicebus/architecture/scaling.md +++ b/nservicebus/architecture/scaling.md @@ -1,9 +1,6 @@ --- title: Scaling with NServiceBus summary: NServiceBus provides several options to scale out a system -tags: - - scalability - - routing redirects: - transports/scale-out reviewed: 2019-06-13 @@ -66,4 +63,4 @@ Execute the following steps to upgrade an endpoint without downtime: 2. Take down one endpoint instance of `Finance` and upgrade it to version 2 of the message assembly `Finance.Messages`. During this time, `Sales` can continue sending messages and the running endpoint instance for `Finance` can continue processing them. 3. Bring the upgraded version of `Finance` back up so it can start processing version 1 messages. 4. Take down the still-running version 1 of `Finance` and upgrade it as well to version 2 of `Finance.Messages` -5. Update `Sales` to also have message assembly `Finance.Messages` version 2. +5. Update `Sales` to also have message assembly `Finance.Messages` version 2. \ No newline at end of file diff --git a/nservicebus/azure/index.md b/nservicebus/azure/index.md index d9ecb8ca90c..14109fa5aee 100644 --- a/nservicebus/azure/index.md +++ b/nservicebus/azure/index.md @@ -1,8 +1,6 @@ --- title: NServiceBus and Azure summary: Using Azure for endpoint hosting and to provide Transports and Persistence -tags: -- Azure reviewed: 2019-01-15 --- @@ -37,4 +35,4 @@ NServiceBus helps create distributed .NET systems not only on premises but also ## Cloud native extensions and samples * [Azure Blob Storage Data Bus](/samples/azure/blob-storage-databus/) - * [Azure Service Fabric Partition Aware Routing](/samples/azure/azure-service-fabric-routing/) + * [Azure Service Fabric Partition Aware Routing](/samples/azure/azure-service-fabric-routing/) \ No newline at end of file diff --git a/nservicebus/azure/understanding-transactionality-in-azure.md b/nservicebus/azure/understanding-transactionality-in-azure.md index 7520fa00344..3067627d190 100644 --- a/nservicebus/azure/understanding-transactionality-in-azure.md +++ b/nservicebus/azure/understanding-transactionality-in-azure.md @@ -1,11 +1,6 @@ --- title: Understanding Transactions in Azure summary: Things to keep in mind when using transactions with NServiceBus in Azure -tags: -- Azure -- Transactions -- Idempotency -- DTC redirects: - nservicebus/transactions - nservicebus/understanding-transactions-in-windows-azure @@ -50,4 +45,4 @@ Note that this protocol requires two communication steps for each resource manag * Using two communication steps per resource manager results in additional communication: 2 resources - 4 network calls, 4 resources - 16 calls, 100 resources - 400 calls, etc. This limits scalability. * Azure data centers consist of hundreds of thousands of machines; failure needs to be expected and all systems must be able to deal with network partitions. Network partitions result in slow or [in doubt](https://msdn.microsoft.com/en-us/library/ms681727.aspx) transactions. Therefore the requirement to wait for responses from all resource managers is problematic even if the communication overhead is manageable. -The latter is the primary reason why none of the Azure services supports distributed transactions, and the recommendation is not to use them in new designs even if it's technically possible. +The latter is the primary reason why none of the Azure services supports distributed transactions, and the recommendation is not to use them in new designs even if it's technically possible. \ No newline at end of file diff --git a/nservicebus/azure/ways-to-live-without-transactions.md b/nservicebus/azure/ways-to-live-without-transactions.md index f408a8eac3a..15c8d986ead 100644 --- a/nservicebus/azure/ways-to-live-without-transactions.md +++ b/nservicebus/azure/ways-to-live-without-transactions.md @@ -3,11 +3,6 @@ title: Avoiding Transactions in Azure summary: Options for avoiding transactions in Azure reviewed: 2020-02-20 isLearningPath: true -tags: - - Azure - - Transactions - - Idempotency - - DTC --- Some [transports](/transports/) in NServiceBus rely on the [Distributed Transaction Coordinator (DTC)](https://docs.microsoft.com/en-us/previous-versions/windows/desktop/ms684146(v=vs.85)) to make a distributed system reliable and to ensure consistency. In Azure, DTC should be avoided since many services don't support transactions, as explained in [Understanding Transactionality in Azure](understanding-transactionality-in-azure.md). @@ -158,4 +153,4 @@ Arguably this is a risky approach that can lead to subtle errors. Although it's In some systems it is possible to accept uncertainty and potential inaccuracies caused by non-idempotent messages. In some cases the data doesn't have to be consistent at all times. In other systems there might be mechanisms that allow for dealing with inconsistencies afterwards. -Although that might seem unacceptable for many programmers, in the end it is a business decision. It's always recommended to talk to business experts and double-check their expectations. +Although that might seem unacceptable for many programmers, in the end it is a business decision. It's always recommended to talk to business experts and double-check their expectations. \ No newline at end of file diff --git a/nservicebus/compliance/gdpr.md b/nservicebus/compliance/gdpr.md index 1a5b2fb69c5..0f1ef638b24 100644 --- a/nservicebus/compliance/gdpr.md +++ b/nservicebus/compliance/gdpr.md @@ -4,8 +4,6 @@ summary: Information about PII stored by NServiceBus versions: "[5,)" component: core isLearningPath: true -tags: - - Compliance reviewed: 2020-03-30 --- @@ -76,4 +74,4 @@ When this data needs to be deleted, contact [Particular Support](https://particu Data points such as "Endpoint Name" have been mentioned multiple times in this document. It's important to note that in many situations these pieces of data do not need to be considered with regards to GDPR. However, if that data has been configured to include PII, they will. It is best to avoid naming things in a manner that includes PII. -There are situations where this is not possible. For example, when using MSMQ as a transport the [computer's name will be included in the name of the queues](/transports/msmq/full-qualified-domain-name.md). This is a requirement of MSMQ and, as a result, means that queue names should receive the same vetting as machine names. +There are situations where this is not possible. For example, when using MSMQ as a transport the [computer's name will be included in the name of the queues](/transports/msmq/full-qualified-domain-name.md). This is a requirement of MSMQ and, as a result, means that queue names should receive the same vetting as machine names. \ No newline at end of file diff --git a/nservicebus/compliance/index.md b/nservicebus/compliance/index.md index a2978ed94b6..d8d6146b803 100644 --- a/nservicebus/compliance/index.md +++ b/nservicebus/compliance/index.md @@ -2,10 +2,8 @@ title: Compliance summary: Compliance Table of Contents reviewed: 2020-03-16 -tags: - - Compliance --- Systems built using NServiceBus often run in environments requiring high levels of government and/or regulatory compliance. -* [General Data Protection Regulation (GDPR)](/nservicebus/compliance/gdpr.md) +* [General Data Protection Regulation (GDPR)](/nservicebus/compliance/gdpr.md) \ No newline at end of file diff --git a/nservicebus/dependency-injection/autofac.md b/nservicebus/dependency-injection/autofac.md index af9fb662bbb..7465eadcde5 100644 --- a/nservicebus/dependency-injection/autofac.md +++ b/nservicebus/dependency-injection/autofac.md @@ -3,8 +3,6 @@ title: Autofac summary: Details on how to Configure NServiceBus to use Autofac for dependency injection. component: Autofac reviewed: 2020-02-20 -tags: - - Dependency Injection related: - samples/dependency-injection/autofac redirects: diff --git a/nservicebus/dependency-injection/castlewindsor.md b/nservicebus/dependency-injection/castlewindsor.md index af033de17d6..dc24b806ec9 100644 --- a/nservicebus/dependency-injection/castlewindsor.md +++ b/nservicebus/dependency-injection/castlewindsor.md @@ -3,8 +3,6 @@ title: Castle Windsor summary: Details on how to Configure NServiceBus to use Castle Windsor for dependency injection. component: Castle reviewed: 2020-02-20 -tags: - - Dependency Injection related: - samples/dependency-injection/castle redirects: diff --git a/nservicebus/dependency-injection/extensions-dependencyinjection.md b/nservicebus/dependency-injection/extensions-dependencyinjection.md index f0a7152e817..cccec0b274f 100644 --- a/nservicebus/dependency-injection/extensions-dependencyinjection.md +++ b/nservicebus/dependency-injection/extensions-dependencyinjection.md @@ -3,8 +3,6 @@ title: NServiceBus.Extensions.DependencyInjection summary: Provides integration with the Microsoft.Extensions.DependencyInjection abstraction reviewed: 2020-02-17 component: Extensions.DependencyInjection -tags: - - Dependency Injection related: - samples/dependency-injection/extensions-dependency-injection - samples/hosting/generic-host @@ -69,4 +67,4 @@ The `NServiceBus.Extensions.DependencyInjection` package does not support proper The package allows the container to be used in [externally managed mode](/nservicebus/dependency-injection/#externally-managed-mode) for full control of the dependency injection container via the `EndpointWithExternallyManagedServiceProvider` extension point: -snippet: externally-managed-mode +snippet: externally-managed-mode \ No newline at end of file diff --git a/nservicebus/dependency-injection/index.md b/nservicebus/dependency-injection/index.md index d942a302f51..ad0149b96e5 100644 --- a/nservicebus/dependency-injection/index.md +++ b/nservicebus/dependency-injection/index.md @@ -4,8 +4,6 @@ summary: NServiceBus automatically registers components, handlers, and sagas. component: Core isLearningPath: true reviewed: 2019-09-11 -tags: - - Dependency Injection redirects: - nservicebus/containers - nservicebus/dependency-injection/msdependencyinjection @@ -14,4 +12,4 @@ related: --- NServiceBus automatically registers and invokes message handlers, sagas, and other user-provided extension points using a dependency injection container. -partial: ownership +partial: ownership \ No newline at end of file diff --git a/nservicebus/dependency-injection/ninject.md b/nservicebus/dependency-injection/ninject.md index 43e26ae37d1..aec2855e836 100644 --- a/nservicebus/dependency-injection/ninject.md +++ b/nservicebus/dependency-injection/ninject.md @@ -3,8 +3,6 @@ title: Ninject summary: Configure NServiceBus to use Ninject for dependency injection. reviewed: 2018-12-05 component: Ninject -tags: - - Dependency Injection related: - samples/dependency-injection/ninject - nservicebus/dependency-injection/child-lifetime diff --git a/nservicebus/dependency-injection/simpleinjector.md b/nservicebus/dependency-injection/simpleinjector.md index 72297e5bcc7..fa708d88c34 100644 --- a/nservicebus/dependency-injection/simpleinjector.md +++ b/nservicebus/dependency-injection/simpleinjector.md @@ -3,8 +3,6 @@ title: Simple Injector summary: Configure NServiceBus to use Simple Injector for dependency injection. component: SimpleInjector reviewed: 2018-12-05 -tags: - - Dependency Injection related: - samples/dependency-injection/simpleinjector redirects: diff --git a/nservicebus/dependency-injection/spring.md b/nservicebus/dependency-injection/spring.md index 79ff030a1f4..ec6cb156109 100644 --- a/nservicebus/dependency-injection/spring.md +++ b/nservicebus/dependency-injection/spring.md @@ -3,8 +3,6 @@ title: Spring summary: Details on how to Configure NServiceBus to use Spring for dependency injection. Includes usage examples as well as lifecycle mappings. component: Spring reviewed: 2018-12-05 -tags: - - Dependency Injection related: - samples/dependency-injection/spring redirects: diff --git a/nservicebus/dependency-injection/structuremap.md b/nservicebus/dependency-injection/structuremap.md index 8b11213e7b9..cc32ff40eaa 100644 --- a/nservicebus/dependency-injection/structuremap.md +++ b/nservicebus/dependency-injection/structuremap.md @@ -3,8 +3,6 @@ title: StructureMap summary: Details on how to Configure NServiceBus to use StructureMap for dependency injection. component: StructureMap reviewed: 2020-02-20 -tags: - - Dependency Injection redirects: - nservicebus/containers/structuremap related: diff --git a/nservicebus/dependency-injection/unity.md b/nservicebus/dependency-injection/unity.md index de87a87b86d..6d3c681ae9f 100644 --- a/nservicebus/dependency-injection/unity.md +++ b/nservicebus/dependency-injection/unity.md @@ -3,8 +3,6 @@ title: Unity summary: Details on how to Configure NServiceBus to use Unity for dependency injection. component: Unity reviewed: 2020-02-20 -tags: - - Dependency Injection related: - samples/dependency-injection/unity redirects: @@ -24,4 +22,4 @@ partial: usage | [SingleInstance](/nservicebus/dependency-injection/) | [`ContainerControlledLifetimeManager`](https://msdn.microsoft.com/en-us/library/microsoft.practices.unity.containercontrolledlifetimemanager.aspx) | -include: property-injection +include: property-injection \ No newline at end of file diff --git a/nservicebus/endpoints/decommissioning-endpoints.md b/nservicebus/endpoints/decommissioning-endpoints.md index 346c19d3bc7..001d94caff9 100644 --- a/nservicebus/endpoints/decommissioning-endpoints.md +++ b/nservicebus/endpoints/decommissioning-endpoints.md @@ -2,9 +2,6 @@ title: Decommissioning Endpoints summary: Describes the process of permanently shutting down endpoints reviewed: 2020-03-23 -tags: - - Endpoint - - Endpoint Instance related: - samples/endpoint-configuration @@ -21,4 +18,4 @@ When decommissioning endpoints, several aspects should be considered: 1. Routing should be adjusted to make sure that no new messages will be delivered to that endpoint. 1. All messages should be processed from the endpoint's queue. 1. [Timeouts should be rerouted to other endpoint instances](/persistence/ravendb/reroute-existing-timeouts.md). - 1. If any errors are discovered in the ServicePulse/ServiceControl tools, [redirect functionality](/servicepulse/redirect.md) can be used to reroute messages to another endpoint instance. + 1. If any errors are discovered in the ServicePulse/ServiceControl tools, [redirect functionality](/servicepulse/redirect.md) can be used to reroute messages to another endpoint instance. \ No newline at end of file diff --git a/nservicebus/endpoints/index.md b/nservicebus/endpoints/index.md index 5079b1872e0..967fd8f10c8 100644 --- a/nservicebus/endpoints/index.md +++ b/nservicebus/endpoints/index.md @@ -3,9 +3,6 @@ title: Endpoints summary: Describe the concepts of Endpoint and Endpoint Instance. reviewed: 2019-07-18 component: Core -tags: -- Endpoint -- Endpoint Instance related: - samples/endpoint-configuration redirects: @@ -14,4 +11,4 @@ redirects: An _endpoint_ is a logical entity that communicates with other endpoints via [_messaging_](/nservicebus/messaging). Each endpoint has an identifying name and contains a collection of [_message handlers_](/nservicebus/handlers/) and [_sagas_](/nservicebus/sagas/). An endpoint can be deployed to a number of machines and environments. Each deployment of an endpoint is an instance. Each endpoint instance has an input queue which contains messages for the endpoint instance to process. -It is common for each endpoint to have a single endpoint instance. As endpoints need to [scale-out](/nservicebus/architecture/scaling.md), additional endpoint instances can be added. This collection of endpoint instances still represents a single logical endpoint. +It is common for each endpoint to have a single endpoint instance. As endpoints need to [scale-out](/nservicebus/architecture/scaling.md), additional endpoint instances can be added. This collection of endpoint instances still represents a single logical endpoint. \ No newline at end of file diff --git a/nservicebus/endpoints/specify-endpoint-name.md b/nservicebus/endpoints/specify-endpoint-name.md index 1c3f2af07a4..78fb8427b72 100644 --- a/nservicebus/endpoints/specify-endpoint-name.md +++ b/nservicebus/endpoints/specify-endpoint-name.md @@ -3,8 +3,6 @@ title: Specify Endpoint Name summary: Describes the ways in which to specify an endpoint name reviewed: 2019-12-25 component: Core -tags: -- Convention redirects: - nservicebus/how-to-specify-your-input-queue-name - nservicebus/messaging/specify-input-queue-name diff --git a/nservicebus/gateway/scale-out.md b/nservicebus/gateway/scale-out.md index 27580916c49..f2e26051092 100644 --- a/nservicebus/gateway/scale-out.md +++ b/nservicebus/gateway/scale-out.md @@ -1,8 +1,6 @@ --- title: Scale out reviewed: 2019-07-18 -tags: - - scalability related: - samples/gateway --- @@ -30,4 +28,4 @@ Handle HA requirements by setting the LB to fail over to another endpoint instan ## Caveats -[Callbacks](/nservicebus/messaging/callbacks.md) through the gateway are not supported on scaled-out endpoints. +[Callbacks](/nservicebus/messaging/callbacks.md) through the gateway are not supported on scaled-out endpoints. \ No newline at end of file diff --git a/nservicebus/handlers/accessing-data.md b/nservicebus/handlers/accessing-data.md index 3e28f1a6ff1..7017bf798f1 100644 --- a/nservicebus/handlers/accessing-data.md +++ b/nservicebus/handlers/accessing-data.md @@ -9,9 +9,6 @@ related: - persistence/sql/accessing-data - persistence/mongodb - persistence/ravendb -tags: - - Persistence - - Saga --- In most cases [handlers](/nservicebus/handlers/) are meant to modify the internal state of an application based on the received message. In a messaging system it is critical to make sure the state change is persisted exactly once. The scenarios below discuss in detail how NServiceBus transaction and persistence settings affect the way business data is stored. @@ -86,4 +83,3 @@ and think about the behavior of the message processing: - If re-sending messages is implemented, multiple copies of the same message may be sent to the downstream endpoints - If message identity is used for de-duplication, message IDs must be generated in a deterministic manner - If outgoing messages depend on the application state, **the code above is incorrect when messages can get re-ordered** (e.g. by infrastructure failures, [recoverability](/nservicebus/recoverability) or competing consumers) - diff --git a/nservicebus/hosting/azure-functions/index.md b/nservicebus/hosting/azure-functions/index.md index 659973703d3..a20311f6f74 100644 --- a/nservicebus/hosting/azure-functions/index.md +++ b/nservicebus/hosting/azure-functions/index.md @@ -1,8 +1,6 @@ --- title: Azure Functions summary: Hosting NServiceBus in Azure Functions -tags: - - Hosting related: - samples/azure/functions reviewed: 2020-05-12 @@ -30,4 +28,4 @@ When using Azure Functions with Azure Service Bus (ASB) or Azure Storage Queues - The NServiceBus `ILog` logging abstraction and the Azure Functions `ILogger` are not wired to work together. - When using the default recoverability or specifying custom number of immediate retries, the number of delivery attempts specified on the underlying queue (ASB) or Azure Functions host (ASB) must be more than then number of the immediate retries. The Azure Functions defaults are 10 (`MaxDeliveryCount`) for the ASB trigger and 5 (`DequeueCount`) for the ASQ trigger. - Delayed Retries are supported only with Azure Service Bus, and not with Azure Storage Queues. -- Message handlers have to be included in the the Azure Functions assembly. +- Message handlers have to be included in the the Azure Functions assembly. \ No newline at end of file diff --git a/nservicebus/hosting/cloud-services-host/configuration.md b/nservicebus/hosting/cloud-services-host/configuration.md index e3dcd9c8b79..9e2c9ecf80e 100644 --- a/nservicebus/hosting/cloud-services-host/configuration.md +++ b/nservicebus/hosting/cloud-services-host/configuration.md @@ -1,8 +1,6 @@ --- title: Configuration summary: Configuring the endpoint when hosting in Azure cloud services -tags: -- Azure reviewed: 2020-02-27 --- @@ -81,4 +79,4 @@ Azure cloud services allow changing the configuration settings from within the A If configuration changes should result in a reconfiguration of the endpoint, consider instructing the `RoleEnvironment` to restart the role instances by subscribing to the [RoleEnvironment.Changing event](https://msdn.microsoft.com/en-us/library/microsoft.windowsazure.serviceruntime.roleenvironment.changing.aspx) and setting `e.Cancel = true;` -If at least two role instances are running, this will result in a configuration change without inflicting downtime on the overall system. Each instance may reboot individually in the process, but this is orchestrated across update and fault domains so that at any point in time an instance is operational. +If at least two role instances are running, this will result in a configuration change without inflicting downtime on the overall system. Each instance may reboot individually in the process, but this is orchestrated across update and fault domains so that at any point in time an instance is operational. \ No newline at end of file diff --git a/nservicebus/hosting/cloud-services-host/critical.md b/nservicebus/hosting/cloud-services-host/critical.md index 731505fbedf..3cbd9139c8a 100644 --- a/nservicebus/hosting/cloud-services-host/critical.md +++ b/nservicebus/hosting/cloud-services-host/critical.md @@ -3,9 +3,6 @@ title: Critical Error Behavior summary: Handling Critical errors in Azure Cloud Services component: CloudServicesHost reviewed: 2019-11-04 -tags: - - Hosting - - Azure --- include: cloudserviceshost-deprecated-warning @@ -23,4 +20,4 @@ The Azure host is terminated on critical errors by default. When the host is ter The Azure host is not terminated on critical errors by default and only shuts down the bus. This would cause the role not to process messages until the role host is restarted. To address this (probably undesired) behavior, implement a critical errors action that shuts down the host process instead. -snippet: DefineCriticalErrorActionForAzureHost +snippet: DefineCriticalErrorActionForAzureHost \ No newline at end of file diff --git a/nservicebus/hosting/cloud-services-host/faq.md b/nservicebus/hosting/cloud-services-host/faq.md index 651dbc78a71..9866dfc9b03 100644 --- a/nservicebus/hosting/cloud-services-host/faq.md +++ b/nservicebus/hosting/cloud-services-host/faq.md @@ -2,9 +2,6 @@ title: Azure Cloud Services Host FAQ summary: Frequently asked questions related to the Azure Cloud Services host. component: CloudServicesHost -tags: -- Azure -- Hosting reviewed: 2020-05-05 --- @@ -42,4 +39,4 @@ snippet: EndpointNameInCodeForAzureHost The cloud services role entry point takes care of updating these values, used for identification of the endpoint instance in ServiceControl, automatically, i.e. the `$.diagnostics.hostdisplayname` defaults to the role name and the `$.diagnostics.hostid` contains the instance ID. -In web roles these values must be set manually, refer to [Override Host Id](/nservicebus/hosting/override-hostid.md) for more information on this topic. +In web roles these values must be set manually, refer to [Override Host Id](/nservicebus/hosting/override-hostid.md) for more information on this topic. \ No newline at end of file diff --git a/nservicebus/hosting/cloud-services-host/index.md b/nservicebus/hosting/cloud-services-host/index.md index 4ef1798cf19..0eb2320f632 100644 --- a/nservicebus/hosting/cloud-services-host/index.md +++ b/nservicebus/hosting/cloud-services-host/index.md @@ -2,10 +2,6 @@ title: Hosting in Azure Cloud Services summary: Using Azure Cloud Services to host NServiceBus. component: CloudServicesHost -tags: - - Hosting - - Azure - - Logging redirects: - nservicebus/hosting-nservicebus-in-windows-azure-cloud-services - nservicebus/azure/hosting-nservicebus-in-windows-azure-cloud-services @@ -55,4 +51,4 @@ Partial: Web ## When endpoint instance starts and stops -snippet: CloudServicesStartAndStop +snippet: CloudServicesStartAndStop \ No newline at end of file diff --git a/nservicebus/hosting/cloud-services-host/logging.md b/nservicebus/hosting/cloud-services-host/logging.md index 714487bef85..27ad6941d57 100644 --- a/nservicebus/hosting/cloud-services-host/logging.md +++ b/nservicebus/hosting/cloud-services-host/logging.md @@ -3,9 +3,6 @@ title: Logging summary: Setting up logging in Azure Cloud Services. component: CloudServicesHost versions: '[6,)' -tags: - - Azure - - Logging reviewed: 2020-04-30 related: - nservicebus/logging @@ -19,4 +16,4 @@ Azure tooling for Visual Studio will set up the Azure Diagnostics Service and NS snippet: DiagnosticMonitorTraceListener -Logging settings can than be controlled by configuring the Azure diagnostics service itself using a `.wadcfg` or `.wadcfgx` file. For more information refer to the [Configuring Diagnostics for Azure Cloud Services and Virtual Machines](https://docs.microsoft.com/en-us/azure/vs-azure-tools-diagnostics-for-cloud-services-and-virtual-machines) or [Use the Azure Diagnostics Configuration File in Azure SDK 2.4 and earlier](https://msdn.microsoft.com/library/azure/hh411551.aspx) articles. +Logging settings can than be controlled by configuring the Azure diagnostics service itself using a `.wadcfg` or `.wadcfgx` file. For more information refer to the [Configuring Diagnostics for Azure Cloud Services and Virtual Machines](https://docs.microsoft.com/en-us/azure/vs-azure-tools-diagnostics-for-cloud-services-and-virtual-machines) or [Use the Azure Diagnostics Configuration File in Azure SDK 2.4 and earlier](https://msdn.microsoft.com/library/azure/hh411551.aspx) articles. \ No newline at end of file diff --git a/nservicebus/hosting/cloud-services-host/shared-hosting.md b/nservicebus/hosting/cloud-services-host/shared-hosting.md index 31644135aa6..463d2ac31ef 100644 --- a/nservicebus/hosting/cloud-services-host/shared-hosting.md +++ b/nservicebus/hosting/cloud-services-host/shared-hosting.md @@ -1,9 +1,6 @@ --- title: Shared Hosting in Azure summary: Using Azure cloud services to host multiple NServiceBus endpoints on a shared pool of machines. -tags: -- Azure -- Hosting related: - samples/azure/shared-host redirects: @@ -85,4 +82,4 @@ Other configuration settings are available as well if one needs more fine-graine The Azure configuration system applies to all instances of all roles. It has a built-in way to separate role types, but not role instance and there is no separation for processes on those instances. This means that a configuration override put in the service configuration file will automatically apply to all endpoints hosted on those roles. This is obviously not desirable and can be dealt with in 2 ways: * Put the configuration settings in the app.config. As auto-update is available, it can be managed this way as changing a configuration means uploading a new zip to the Azure storage account and the hosts will update themselves automatically. (This is the default) - * Separate the configuration settings in the service configuration file by convention. The `.AzureConfigurationSource(prefix)` overload allows setting a prefix in every endpoint that will be prepended to its configuration settings. Call this configuration method with a prefix of choice and use the configuration settings file for the hosted endpoints. + * Separate the configuration settings in the service configuration file by convention. The `.AzureConfigurationSource(prefix)` overload allows setting a prefix in every endpoint that will be prepended to its configuration settings. Call this configuration method with a prefix of choice and use the configuration settings file for the hosted endpoints. \ No newline at end of file diff --git a/nservicebus/hosting/cloud-services-host/startup.md b/nservicebus/hosting/cloud-services-host/startup.md index 71de88db656..3194f36f88e 100644 --- a/nservicebus/hosting/cloud-services-host/startup.md +++ b/nservicebus/hosting/cloud-services-host/startup.md @@ -2,12 +2,9 @@ title: Startup Behavior summary: Running code at startup when hosting in Azure Cloud Services. component: CloudServicesHost -tags: - - Hosting - - Azure reviewed: 2018-09-19 --- include: cloudserviceshost-deprecated-warning -include: host-startup +include: host-startup \ No newline at end of file diff --git a/nservicebus/hosting/critical-errors.md b/nservicebus/hosting/critical-errors.md index a744cd4481e..669d1eda45c 100644 --- a/nservicebus/hosting/critical-errors.md +++ b/nservicebus/hosting/critical-errors.md @@ -3,9 +3,6 @@ title: Critical Errors summary: How to handle critical errors which adversely affect messaging in an endpoint. reviewed: 2019-04-17 component: Core -tags: -- Hosting -- Logging --- NServiceBus has built-in [recoverability](/nservicebus/recoverability/) but in certain scenarios, it is not possible to handle errors in a graceful way. The reason for this is that NServiceBus does not have enough context to make a sensible decision on how to proceed after these errors have occurred. Examples of these **critical errors** include: @@ -67,4 +64,4 @@ snippet: InvokeCriticalError ## Heartbeat functionality -The [Heartbeat functionality](/monitoring/heartbeats/) is configured to start pinging ServiceControl immediately after the endpoint starts. It only stops when the process exits. The only way for a critical error to result in a heartbeat failure in ServicePulse/ServiceControl is for the critical error to kill the process. +The [Heartbeat functionality](/monitoring/heartbeats/) is configured to start pinging ServiceControl immediately after the endpoint starts. It only stops when the process exits. The only way for a critical error to result in a heartbeat failure in ServicePulse/ServiceControl is for the critical error to kill the process. \ No newline at end of file diff --git a/nservicebus/hosting/docker-host/index.md b/nservicebus/hosting/docker-host/index.md index d4b0876da16..ff84e962a56 100644 --- a/nservicebus/hosting/docker-host/index.md +++ b/nservicebus/hosting/docker-host/index.md @@ -1,8 +1,6 @@ --- title: Docker Container Host summary: Take advantage of process isolation by hosting endpoints in Docker containers -tags: - - Hosting related: - nservicebus/dotnet-templates - nservicebus/licensing @@ -56,4 +54,3 @@ ENTRYPOINT ["dotnet", "MyEndpoint.dll"] partial: program - diff --git a/nservicebus/hosting/extensions-hosting.md b/nservicebus/hosting/extensions-hosting.md index 41887ec3304..f9f4a53a8a2 100644 --- a/nservicebus/hosting/extensions-hosting.md +++ b/nservicebus/hosting/extensions-hosting.md @@ -3,8 +3,6 @@ title: NServiceBus.Extensions.Hosting summary: NServiceBus integration with Microsoft.Extensions.Hosting component: Extensions.Hosting reviewed: 2019-11-08 -tags: - - Hosting related: - samples/hosting/generic-host - samples/dependency-injection/aspnetcore @@ -26,4 +24,4 @@ WARNING: `UseNServiceBus` must be specified before any other service (e.g. `Conf NServiceBus endpoints hosted as part of the generic host automatically use the provided `IServiceCollection` and `IServiceProvider` dependency injection infrastructure. Message handlers can resolve dependencies which are registered in the `IServiceCollection`. -`UseNServiceBus` automatically registers an `IMessageSession` with the container which can be resolved from the `IServiceProvider` or via dependency injection during runtime. +`UseNServiceBus` automatically registers an `IMessageSession` with the container which can be resolved from the `IServiceProvider` or via dependency injection during runtime. \ No newline at end of file diff --git a/nservicebus/hosting/index.md b/nservicebus/hosting/index.md index a75af836039..c7e7d43f8e4 100644 --- a/nservicebus/hosting/index.md +++ b/nservicebus/hosting/index.md @@ -3,8 +3,6 @@ title: Hosting summary: Describes the various approaches to endpoint hosting component: Core reviewed: 2020-01-03 -tags: -- Hosting redirects: - nservicebus/hosting/self-hosting - nservicebus/hosting/self-hosting-v4.x @@ -157,4 +155,4 @@ Since NServiceBus makes assumptions on aspects like assembly names, ILMerging an NServiceBus endpoints have certain requirements on the hosting environment: * The endpoint process needs write access to write log files. See the [logging documentation](/nservicebus/logging) for more details about the default log file location and how to configure logging. -* The endpoint process needs write access to write the startup diagnostics file. See the [startup diagnostics documentation](/nservicebus/hosting/startup-diagnostics.md) for more details about the diagnostic file. +* The endpoint process needs write access to write the startup diagnostics file. See the [startup diagnostics documentation](/nservicebus/hosting/startup-diagnostics.md) for more details about the diagnostic file. \ No newline at end of file diff --git a/nservicebus/hosting/nservicebus-host/index.md b/nservicebus/hosting/nservicebus-host/index.md index f7d4379b69a..b4ada4fadf3 100644 --- a/nservicebus/hosting/nservicebus-host/index.md +++ b/nservicebus/hosting/nservicebus-host/index.md @@ -1,9 +1,6 @@ --- title: NServiceBus Host summary: Avoid writing repeat configuration code, host the endpoints in a Windows Service, and change technologies without code. -tags: - - Hosting - - Logging redirects: - nservicebus/the-nservicebus-host related: @@ -126,4 +123,4 @@ The NServiceBus.Host is compiled against .NET Framework 4.5.2. The [Transport La -``` +``` \ No newline at end of file diff --git a/nservicebus/hosting/nservicebus-host/installation.md b/nservicebus/hosting/nservicebus-host/installation.md index 56b26e49e2d..6b39d60205d 100644 --- a/nservicebus/hosting/nservicebus-host/installation.md +++ b/nservicebus/hosting/nservicebus-host/installation.md @@ -1,8 +1,6 @@ --- title: Installation summary: How to install the NServiceBus.Host as a Windows service -tags: -- Hosting reviewed: 2020-04-30 --- @@ -153,4 +151,4 @@ For example: ```dos NServiceBus.Host.exe /uninstall /serviceName:"MyPublisher" -``` +``` \ No newline at end of file diff --git a/nservicebus/hosting/nservicebus-host/profiles-customization.md b/nservicebus/hosting/nservicebus-host/profiles-customization.md index f5f212af220..8b64ab2ff5d 100644 --- a/nservicebus/hosting/nservicebus-host/profiles-customization.md +++ b/nservicebus/hosting/nservicebus-host/profiles-customization.md @@ -1,11 +1,6 @@ --- title: NServiceBus Host Profiles Customization summary: 'Create custom NServiceBus host profiles and customize default NServiceBus host profiles.' -tags: -- Profiles -- Hosting -- Logging -- Persistence component: Host reviewed: 2019-01-09 --- @@ -58,4 +53,4 @@ For example, NServiceBus Host uses this information to configure publishers. End Endpoint configuration can be accessed to customize profile behaviors as follows: -snippet: dependent_profile +snippet: dependent_profile \ No newline at end of file diff --git a/nservicebus/hosting/nservicebus-host/profiles.md b/nservicebus/hosting/nservicebus-host/profiles.md index 0dee70ab250..54cba54dcd1 100644 --- a/nservicebus/hosting/nservicebus-host/profiles.md +++ b/nservicebus/hosting/nservicebus-host/profiles.md @@ -1,11 +1,6 @@ --- title: NServiceBus Host Profiles summary: 'Profiles ease the configuration process. There are three profiles out of the box: Lite, Integration, and Production.' -tags: -- Profiles -- Hosting -- Logging -- Persistence redirects: - nservicebus/profiles-for-nservicebus-host - nservicebus/more-on-profiles @@ -110,4 +105,4 @@ The built-in profiles use the following default persistence settings: | Gateway |In-Memory |As configured |As configured | | Distributor |- |- |- | -In the Lite profile, NServiceBus Host will always use the in-memory persistence. In the Integration and Production profiles, the host verifies if a specific persistence mechanism is provided, e.g., in the endpoint configuration. If not specified otherwise, then RavenDB persistence will be used by default. +In the Lite profile, NServiceBus Host will always use the in-memory persistence. In the Integration and Production profiles, the host verifies if a specific persistence mechanism is provided, e.g., in the endpoint configuration. If not specified otherwise, then RavenDB persistence will be used by default. \ No newline at end of file diff --git a/nservicebus/hosting/publishing-from-web-applications.md b/nservicebus/hosting/publishing-from-web-applications.md index 382b22ae7be..bfae177cfe5 100644 --- a/nservicebus/hosting/publishing-from-web-applications.md +++ b/nservicebus/hosting/publishing-from-web-applications.md @@ -2,10 +2,6 @@ title: Publishing from Web Applications summary: Guidelines for publishing messages from within web applications component: core -tags: -- event -- scalability -- publish subscribe related: - samples/web reviewed: 2018-10-18 @@ -91,4 +87,4 @@ It can be useful to publish events from a web application. Always keep the follo * Don't publish from the web tier if an exception before the event is published could lead to data loss. * For storage-driven transports, all web application instances must share the same subscription storage. - * Never use an individual web server name to identify the source of an event being published, which would interfere with effective scale out. + * Never use an individual web server name to identify the source of an event being published, which would interfere with effective scale out. \ No newline at end of file diff --git a/nservicebus/hosting/web-application.md b/nservicebus/hosting/web-application.md index d62282f9de4..c4bbb168ce5 100644 --- a/nservicebus/hosting/web-application.md +++ b/nservicebus/hosting/web-application.md @@ -3,8 +3,6 @@ title: Web Application Hosting summary: Hosting NServiceBus in a Web Site or Web Service reviewed: 2019-11-27 isLearningPath: true -tags: -- Hosting related: - samples/web - nservicebus/lifecycle @@ -45,4 +43,4 @@ The recommended approach to handle this is to have two dependency injection inst 1. Any service which is registered with both dependency injection instances can be resolved in both web request handlers and NServiceBus message bus handlers _but_: 1. these will be different objects with different lifetimes. 1. even if the services are registered with a singleton lifetime, there will still be one created for each dependency injection instance - 1. if a service needs to be shared and a single instance, it must be created externally during the web application host startup, and that specific instance must be registered in both dependency injection instances. + 1. if a service needs to be shared and a single instance, it must be created externally during the web application host startup, and that specific instance must be registered in both dependency injection instances. \ No newline at end of file diff --git a/nservicebus/hosting/windows-service.md b/nservicebus/hosting/windows-service.md index e9cdaa00702..b45fbe08c36 100644 --- a/nservicebus/hosting/windows-service.md +++ b/nservicebus/hosting/windows-service.md @@ -4,8 +4,6 @@ summary: How to install an NServiceBus endpoint as a Windows service reviewed: 2018-11-22 component: Core isLearningPath: true -tags: - - Hosting related: - nservicebus/dotnet-templates - nservicebus/lifecycle @@ -125,4 +123,4 @@ A Windows Service can be uninstalled using the [sc delete](https://technet.micro ```dos sc.exe delete [ServiceName] sc.exe delete SalesEndpoint -``` +``` \ No newline at end of file diff --git a/nservicebus/lifecycle/endpointstartandstop.md b/nservicebus/lifecycle/endpointstartandstop.md index 1d01af0fd0b..41ef2f6119b 100644 --- a/nservicebus/lifecycle/endpointstartandstop.md +++ b/nservicebus/lifecycle/endpointstartandstop.md @@ -3,8 +3,6 @@ title: When Endpoint Instance Starts and Stops summary: How to hook into the startup and shutdown sequence of an endpoint instance. reviewed: 2018-10-29 component: core -tags: - - lifecycle related: - samples/startup-shutdown-sequence redirects: diff --git a/nservicebus/lifecycle/ineedinitialization.md b/nservicebus/lifecycle/ineedinitialization.md index 6c6caf2107b..b4f0611014d 100644 --- a/nservicebus/lifecycle/ineedinitialization.md +++ b/nservicebus/lifecycle/ineedinitialization.md @@ -3,8 +3,6 @@ title: Initialization summary: An interface that supports hooking into the very beginning of the bus creation sequence of NServiceBus. component: Core reviewed: 2019-07-18 -tags: - - lifecycle related: - samples/startup-shutdown-sequence --- @@ -29,4 +27,4 @@ Exceptions thrown by instances of `INeedInitialization` are not handled by NServ NOTE: Instances of `INeedInitialization` are created after type-scanning has occurred. Do not attempt to alter the types to be scanned from an instance of `INeedInitialization`. -snippet: lifecycle-ineedinitialization +snippet: lifecycle-ineedinitialization \ No newline at end of file diff --git a/nservicebus/lifecycle/iwanttorunbeforeconfigurationisfinalized.md b/nservicebus/lifecycle/iwanttorunbeforeconfigurationisfinalized.md index 2147ff59ae6..9d96216ad09 100644 --- a/nservicebus/lifecycle/iwanttorunbeforeconfigurationisfinalized.md +++ b/nservicebus/lifecycle/iwanttorunbeforeconfigurationisfinalized.md @@ -3,8 +3,6 @@ title: Before Configuration Finalized summary: An interface that allows hooking into the configuration sequence of NServiceBus. component: Core reviewed: 2019-07-22 -tags: - - lifecycle related: - samples/startup-shutdown-sequence --- @@ -25,4 +23,4 @@ Once created `Run(...)` is called on each instance. These calls are made sequent Exceptions thrown by instances of `IWantToRunBeforeConfigurationIsFinalized` are unhandled by NServiceBus. These will bubble up to the caller creating the bus. -snippet: lifecycle-iwanttorunbeforeconfigurationisfinalized +snippet: lifecycle-iwanttorunbeforeconfigurationisfinalized \ No newline at end of file diff --git a/nservicebus/lifecycle/iwanttorunwhenconfigurationiscomplete.md b/nservicebus/lifecycle/iwanttorunwhenconfigurationiscomplete.md index 2c6549a46ca..22c5173b865 100644 --- a/nservicebus/lifecycle/iwanttorunwhenconfigurationiscomplete.md +++ b/nservicebus/lifecycle/iwanttorunwhenconfigurationiscomplete.md @@ -4,8 +4,6 @@ summary: An interface that supports hooking into the configuration sequence of N reviewed: 2019-12-20 component: Core versions: '[,6.0)' -tags: - - lifecycle related: - samples/startup-shutdown-sequence --- @@ -30,4 +28,4 @@ Once created `Run(...)` is called on each instance. These calls are made sequent Exceptions thrown by instances of `IWantToRunWhenConfigurationIsComplete` are not handled by NServiceBus. These will bubble up to the creator of the bus. -snippet: lifecycle-iwanttorunwhenconfigurationiscomplete +snippet: lifecycle-iwanttorunwhenconfigurationiscomplete \ No newline at end of file diff --git a/nservicebus/logging/eventsourcelogging.md b/nservicebus/logging/eventsourcelogging.md index 061e332f1ed..c80f987487a 100644 --- a/nservicebus/logging/eventsourcelogging.md +++ b/nservicebus/logging/eventsourcelogging.md @@ -3,8 +3,6 @@ title: Event Tracing for Windows summary: Logging to Event Tracing for Windows (ETW) reviewed: 2019-07-29 component: EventSourceLogging -tags: -- Logging related: - samples/logging/eventsourcelogging --- @@ -15,4 +13,3 @@ Support for writing all NServiceBus log entries to [event tracing for Windows (E include: eventsourcelogging - diff --git a/nservicebus/logging/extensions-logging.md b/nservicebus/logging/extensions-logging.md index 1772de213c7..0c762fc0700 100644 --- a/nservicebus/logging/extensions-logging.md +++ b/nservicebus/logging/extensions-logging.md @@ -3,8 +3,6 @@ title: NServiceBus.Extensions.Logging summary: Logging with Microsoft.Extensions.Logging reviewed: 2020-03-20 component: Extensions.Logging -tags: -- Logging related: - samples/logging/extensions-logging --- @@ -49,4 +47,4 @@ Microsoft.Extensions.Logging abstractions provide a generic interface that allow Configure NServiceBus to use Microsoft.Extensions.Logging -snippet: ExtensionsLogging +snippet: ExtensionsLogging \ No newline at end of file diff --git a/nservicebus/logging/index.md b/nservicebus/logging/index.md index da6ece14eed..f0e60226d58 100644 --- a/nservicebus/logging/index.md +++ b/nservicebus/logging/index.md @@ -4,8 +4,6 @@ summary: NServiceBus logging reviewed: 2019-07-29 component: Core isLearningPath: true -tags: -- Logging redirects: - nservicebus/logging-in-nservicebus related: @@ -85,4 +83,4 @@ partial: exception-data ## Unit testing -Unit testing of logging is supported by [the `NServiceBus.Testing` library](/nservicebus/testing/#testing-logging-behavior). +Unit testing of logging is supported by [the `NServiceBus.Testing` library](/nservicebus/testing/#testing-logging-behavior). \ No newline at end of file diff --git a/nservicebus/logging/message-contents.md b/nservicebus/logging/message-contents.md index c380bf08a10..d62c8c47a5a 100644 --- a/nservicebus/logging/message-contents.md +++ b/nservicebus/logging/message-contents.md @@ -3,8 +3,6 @@ title: Logging message contents summary: How to output message contents to the log reviewed: 2019-07-22 component: Core -tags: -- Logging redirects: - nservicebus/logging-message-contents --- @@ -13,4 +11,4 @@ When NServiceBus sends a message, it writes the result of the `ToString()` metho snippet: MessageWithToStringLogged -NOTE: NServiceBus only makes these calls at a log threshold of DEBUG or lower. +NOTE: NServiceBus only makes these calls at a log threshold of DEBUG or lower. \ No newline at end of file diff --git a/nservicebus/logging/nlog.md b/nservicebus/logging/nlog.md index b36eeefad6b..bc5696285cd 100644 --- a/nservicebus/logging/nlog.md +++ b/nservicebus/logging/nlog.md @@ -3,8 +3,6 @@ title: NLog summary: Logging to NLog reviewed: 2019-07-29 component: NLog -tags: -- Logging related: - samples/logging/nlog-custom --- @@ -25,4 +23,4 @@ Here is a code configuration example for adding a [Rule](https://github.com/nlog snippet: NLogFiltering -partial: nlog-exception-data +partial: nlog-exception-data \ No newline at end of file diff --git a/nservicebus/logging/usage.md b/nservicebus/logging/usage.md index 2e1a27b76d7..5ad6eddcbf6 100644 --- a/nservicebus/logging/usage.md +++ b/nservicebus/logging/usage.md @@ -2,8 +2,6 @@ title: Logging from the user code reviewed: 2019-07-29 component: Core -tags: -- Logging redirects: - nservicebus/logging-writing --- @@ -18,4 +16,4 @@ WARNING: Make sure that logging is correctly initialized before resolving the `I NOTE: To avoid unnecessary processing, especially when logging more verbose messages, such as `Debug`, make sure to first check if logging at that level is enabled. -NOTE: Since `LogManager.GetLogger(..);` is an expensive call, it is important that the field is `static` so that the call happens only once per class and has the best possible performance. +NOTE: Since `LogManager.GetLogger(..);` is an expensive call, it is important that the field is `static` so that the call happens only once per class and has the best possible performance. \ No newline at end of file diff --git a/nservicebus/messaging/best-practice-enforcement.md b/nservicebus/messaging/best-practice-enforcement.md index f0b464f51de..ea149e29c52 100644 --- a/nservicebus/messaging/best-practice-enforcement.md +++ b/nservicebus/messaging/best-practice-enforcement.md @@ -4,10 +4,6 @@ summary: How to enable/disable the enforcement of messaging best practices based component: Core reviewed: 2018-09-21 versions: '[6.0,)' -tags: - - Convention - - Command - - Event --- By default, [messaging best practices](messages-events-commands.md) are enforced for messages defined as either commands or events. @@ -20,4 +16,4 @@ snippet: DisableBestPracticeEnforcementPerEndpoint or at the message level using: -snippet: DisableBestPracticeEnforcementPerMessage +snippet: DisableBestPracticeEnforcementPerMessage \ No newline at end of file diff --git a/nservicebus/messaging/conventions.md b/nservicebus/messaging/conventions.md index 5d9b3cad27a..9a8fc651281 100644 --- a/nservicebus/messaging/conventions.md +++ b/nservicebus/messaging/conventions.md @@ -1,9 +1,6 @@ --- title: Conventions summary: Custom conventions for defining how certain things are detected -tags: -- Unobtrusive -- Convention component: Core reviewed: 2019-09-03 related: @@ -39,4 +36,3 @@ snippet: MessageConventionsDual ## Attributes If attributes are preferred over marker interfaces then this can be achieved via the [NServiceBus.AttributeConventions](https://www.nuget.org/packages/NServiceBus.AttributeConventions) community package exists that allows using attributes instead of interfaces. - diff --git a/nservicebus/messaging/databus/azure-blob-storage.md b/nservicebus/messaging/databus/azure-blob-storage.md index e4ce905ee29..90b6f4e54f0 100644 --- a/nservicebus/messaging/databus/azure-blob-storage.md +++ b/nservicebus/messaging/databus/azure-blob-storage.md @@ -3,8 +3,6 @@ title: Azure Blob Storage Data Bus summary: The Azure Blob Storage implementation of databus reviewed: 2020-03-04 component: ABSDataBus -tags: - - DataBus related: - samples/azure/blob-storage-databus - samples/azure/blob-storage-databus-cleanup-function @@ -51,4 +49,4 @@ partial: settings Setting the `CleanupInterval` to `0` will disable blob cleanup. -snippet: AzureDataBusDisableCleanup +snippet: AzureDataBusDisableCleanup \ No newline at end of file diff --git a/nservicebus/messaging/databus/custom.md b/nservicebus/messaging/databus/custom.md index 5e1ee06af52..c5c03b38031 100644 --- a/nservicebus/messaging/databus/custom.md +++ b/nservicebus/messaging/databus/custom.md @@ -3,8 +3,6 @@ title: Custom Data Bus Implementation summary: Details how to register and plug in a custom data bus implementation into an endpoint. component: Core reviewed: 2019-05-12 -tags: -- DataBus redirects: - nservicebus/plugin-custom-databus related: @@ -13,4 +11,4 @@ related: Endpoints support sending and receiving large chunks of data via the [data bus](./). -partial: content +partial: content \ No newline at end of file diff --git a/nservicebus/messaging/databus/file-share.md b/nservicebus/messaging/databus/file-share.md index b2b24c00fd9..3994dfe4e94 100644 --- a/nservicebus/messaging/databus/file-share.md +++ b/nservicebus/messaging/databus/file-share.md @@ -3,8 +3,6 @@ title: File Share Data Bus summary: An implementation of data bus using file shares reviewed: 2020-01-03 component: FileShareDataBus -tags: - - DataBus related: - samples/file-share-databus --- @@ -33,4 +31,4 @@ This same location should be used when performing the cleanup. For example, this path can be used in a Handler for a message containing data bus properties. -snippet: HandlerThatCleansUpDatabus +snippet: HandlerThatCleansUpDatabus \ No newline at end of file diff --git a/nservicebus/messaging/databus/index.md b/nservicebus/messaging/databus/index.md index 3a857c75426..bc2bbf75100 100644 --- a/nservicebus/messaging/databus/index.md +++ b/nservicebus/messaging/databus/index.md @@ -3,8 +3,6 @@ title: Data Bus summary: How to handle messages that are too large to be sent by a transport natively component: Core reviewed: 2019-01-27 -tags: - - DataBus redirects: - nservicebus/databus related: @@ -103,4 +101,4 @@ The storage location for data bus blobs is critical to the operation of endpoint ### Auditing -The data stored in data bus blobs may be considered part of an audit record. In these cases data bus blobs should be archived alongside messages for as long as the audit record is required. +The data stored in data bus blobs may be considered part of an audit record. In these cases data bus blobs should be archived alongside messages for as long as the audit record is required. \ No newline at end of file diff --git a/nservicebus/messaging/delayed-delivery.md b/nservicebus/messaging/delayed-delivery.md index a4a39401914..81b06097bc2 100644 --- a/nservicebus/messaging/delayed-delivery.md +++ b/nservicebus/messaging/delayed-delivery.md @@ -3,8 +3,6 @@ title: Delayed Delivery summary: Delay delivery of messages until a later time. component: core reviewed: 2018-10-29 -tags: - - Defer related: - samples/delayed-delivery --- @@ -59,4 +57,4 @@ NOTE: If specifying a time that is in the past then the message will still be sl ## How it works -NServiceBus provides delayed delivery feature for transports that don't have native support for delayed message delivery. All Transports except MSMQ support delayed message delivery natively and therefore don't require persistence to store timeouts. To learn more about NServiceBus delayed message store refer to the [Timeout Manager](/nservicebus/messaging/timeout-manager.md) article. +NServiceBus provides delayed delivery feature for transports that don't have native support for delayed message delivery. All Transports except MSMQ support delayed message delivery natively and therefore don't require persistence to store timeouts. To learn more about NServiceBus delayed message store refer to the [Timeout Manager](/nservicebus/messaging/timeout-manager.md) article. \ No newline at end of file diff --git a/nservicebus/messaging/file-based-routing.md b/nservicebus/messaging/file-based-routing.md index 56ad56f5118..ea9d26cbc9b 100644 --- a/nservicebus/messaging/file-based-routing.md +++ b/nservicebus/messaging/file-based-routing.md @@ -3,8 +3,6 @@ title: Centralized file-based routing summary: How NServiceBus message routing can be configured via a file that can be shared between all endpoints reviewed: 2018-11-14 component: FileBasedRouting -tags: -- routing related: - nservicebus/messaging/routing-extensibility - nservicebus/messaging/routing @@ -63,4 +61,4 @@ In order to allow centralized configuration of the routing file, the file needs ## Scaling out -It's possible to use sender-side distribution to scale out messages and events to multiple instances of the same logical endpoint. This is done with the [instance mapping file](/transports/msmq/routing.md). +It's possible to use sender-side distribution to scale out messages and events to multiple instances of the same logical endpoint. This is done with the [instance mapping file](/transports/msmq/routing.md). \ No newline at end of file diff --git a/nservicebus/messaging/header-manipulation.md b/nservicebus/messaging/header-manipulation.md index 8b7c2c4d4d5..4f8fee8ed3b 100644 --- a/nservicebus/messaging/header-manipulation.md +++ b/nservicebus/messaging/header-manipulation.md @@ -3,8 +3,6 @@ title: Manipulating message headers summary: Access and manipulate the built-in NServiceBus headers or add custom headers reviewed: 2020-01-03 component: Core -tags: -- Header redirects: - nservicebus/how-do-i-get-technical-information-about-a-message related: @@ -81,4 +79,4 @@ NServiceBus supports registering headers at configuration time that are then add snippet: header-static-endpoint -partial: threadsafe +partial: threadsafe \ No newline at end of file diff --git a/nservicebus/messaging/headers.md b/nservicebus/messaging/headers.md index 2928522ae3a..e7bcff1baff 100644 --- a/nservicebus/messaging/headers.md +++ b/nservicebus/messaging/headers.md @@ -4,8 +4,6 @@ summary: List of built-in NServiceBus message headers. reviewed: 2019-10-04 component: Core versions: '[5.0,)' -tags: - - Header redirects: - nservicebus/message-headers - nservicebus/messaging/headers @@ -473,4 +471,4 @@ snippet: HeaderWriterDataBusConvention #### Example body -snippet: HeaderWriterDataBusConventionBody +snippet: HeaderWriterDataBusConventionBody \ No newline at end of file diff --git a/nservicebus/messaging/messages-events-commands.md b/nservicebus/messaging/messages-events-commands.md index 5a2e2800e0a..894f009def6 100644 --- a/nservicebus/messaging/messages-events-commands.md +++ b/nservicebus/messaging/messages-events-commands.md @@ -3,9 +3,6 @@ title: Messages, events and commands summary: Messages, events, and commands and how to define them. component: Core reviewed: 2018-12-28 -tags: - - Unobtrusive - - Convention related: - nservicebus/messaging/conventions - nservicebus/messaging/unobtrusive-mode @@ -80,4 +77,4 @@ public class MyMessage : IMessage { } ### Conventions -To avoid having message contract assemblies reference the NServiceBus assembly, [custom conventions](/nservicebus/messaging/conventions.md) can be used to identify the types used as contracts for messages, commands, and events. This is known as [unobtrusive mode](unobtrusive-mode.md). +To avoid having message contract assemblies reference the NServiceBus assembly, [custom conventions](/nservicebus/messaging/conventions.md) can be used to identify the types used as contracts for messages, commands, and events. This is known as [unobtrusive mode](unobtrusive-mode.md). \ No newline at end of file diff --git a/nservicebus/messaging/publish-subscribe/controlling-what-is-subscribed.md b/nservicebus/messaging/publish-subscribe/controlling-what-is-subscribed.md index 6304f360c34..ed00eab100d 100644 --- a/nservicebus/messaging/publish-subscribe/controlling-what-is-subscribed.md +++ b/nservicebus/messaging/publish-subscribe/controlling-what-is-subscribed.md @@ -2,8 +2,6 @@ title: Controlling What Is Subscribed summary: When applying the publish-subscribe pattern, there are several ways to control what messages are subscribed to component: Core -tags: -- Publish Subscribe reviewed: 2020-05-27 --- @@ -57,4 +55,3 @@ Events can manually be subscribed and unsubscribed to: snippet: ExplicitSubscribe partial: manualsubscriptions - diff --git a/nservicebus/messaging/publish-subscribe/index.md b/nservicebus/messaging/publish-subscribe/index.md index 6cf2508a49f..98190f6eb6d 100644 --- a/nservicebus/messaging/publish-subscribe/index.md +++ b/nservicebus/messaging/publish-subscribe/index.md @@ -3,9 +3,6 @@ title: Publish-Subscribe summary: Subscribers tell the publisher they are interested. Publishers store addresses for sending messages. reviewed: 2019-12-23 component: Core -tags: -- Publish Subscribe -- Messaging Patterns redirects: - nservicebus/how-pub-sub-works - nservicebus/messaging/publish-subscribe/how-to-pub-sub @@ -142,4 +139,4 @@ Note over Publisher: Publish Message1 occurs Publisher ->> Transport: Sends Message1 Transport ->> Subscriber1: Send Message1 Transport ->> Subscriber2: Send Message1 -``` +``` \ No newline at end of file diff --git a/nservicebus/messaging/publish-subscribe/publish-handle-event.md b/nservicebus/messaging/publish-subscribe/publish-handle-event.md index 8c67f2c6d49..9e2ec467ef4 100644 --- a/nservicebus/messaging/publish-subscribe/publish-handle-event.md +++ b/nservicebus/messaging/publish-subscribe/publish-handle-event.md @@ -3,8 +3,6 @@ title: Publish and Handle an Event summary: How to define, publish, and handle events component: Core reviewed: 2019-01-09 -tags: -- Publish Subscribe related: - samples/pubsub - tutorials/nservicebus-step-by-step diff --git a/nservicebus/messaging/routing-extensibility.md b/nservicebus/messaging/routing-extensibility.md index 0ef444c970e..90ef7da25ed 100644 --- a/nservicebus/messaging/routing-extensibility.md +++ b/nservicebus/messaging/routing-extensibility.md @@ -3,8 +3,6 @@ title: Routing system extensibility points summary: How NServiceBus routing can be extended reviewed: 2020-03-30 component: Core -tags: - - routing related: - nservicebus/messaging/routing --- @@ -17,4 +15,4 @@ Extending the [NServiceBus routing subsystem](/nservicebus/messaging/routing.md) partial: content -partial: endpoint-mappings +partial: endpoint-mappings \ No newline at end of file diff --git a/nservicebus/messaging/routing.md b/nservicebus/messaging/routing.md index 4dd8c218c5e..7d89695a46c 100644 --- a/nservicebus/messaging/routing.md +++ b/nservicebus/messaging/routing.md @@ -4,8 +4,6 @@ summary: How NServiceBus routes messages between endpoints. reviewed: 2019-12-23 component: Core isLearningPath: true -tags: -- routing redirects: - nservicebus/how-do-i-specify-to-which-destination-a-message-will-be-sent - nservicebus/messaging/specify-message-destination @@ -98,4 +96,4 @@ Recommendations: - Avoid hard-coding the discriminator when sending messages. - Avoid using `MakeInstanceUniquelyAddressable` for priority queues. -- Consider using [routing extensibility](/nservicebus/messaging/routing-extensibility.md) for routing to specific instances. +- Consider using [routing extensibility](/nservicebus/messaging/routing-extensibility.md) for routing to specific instances. \ No newline at end of file diff --git a/nservicebus/messaging/timeout-manager.md b/nservicebus/messaging/timeout-manager.md index ec497c76acd..2258d33761e 100644 --- a/nservicebus/messaging/timeout-manager.md +++ b/nservicebus/messaging/timeout-manager.md @@ -3,8 +3,6 @@ title: Timeout Manager summary: NServiceBus persistent delayed message store component: core reviewed: 2018-11-09 -tags: - - Defer related: - samples/delayed-delivery - nservicebus/messaging/delayed-delivery @@ -51,4 +49,3 @@ When this happens the following critical error message will be raised: If the NServiceBus.Host is used then the host will execute a fail-fast as documented in the [default critical error behavior for the NServiceBus.Host](/nservicebus/hosting/nservicebus-host/#endpoint-configuration-default-critical-error-action). - diff --git a/nservicebus/messaging/unobtrusive-mode.md b/nservicebus/messaging/unobtrusive-mode.md index b4fe2de77d9..58bab90891a 100644 --- a/nservicebus/messaging/unobtrusive-mode.md +++ b/nservicebus/messaging/unobtrusive-mode.md @@ -2,8 +2,6 @@ title: Unobtrusive Mode Messages summary: How to avoid referencing NServiceBus assemblies from message assemblies. reviewed: 2019-09-03 -tags: -- Convention related: - nservicebus/messaging/messages-events-commands - nservicebus/messaging/conventions @@ -30,4 +28,4 @@ There are a couple of ways this can be solved. ## Unobtrusive mode -NServiceBus allows defining custom [message conventions](conventions.md) instead of using the `IMessage`, `ICommand` or `IEvent` interfaces and attributes like `TimeToBeReceivedAttribute` and `ExpressAttribute`. NServiceBus also supports conventions for encrypted properties, express messages, databus properties and time to be received. With these conventions combined a reference to NServiceBus can be avoided. +NServiceBus allows defining custom [message conventions](conventions.md) instead of using the `IMessage`, `ICommand` or `IEvent` interfaces and attributes like `TimeToBeReceivedAttribute` and `ExpressAttribute`. NServiceBus also supports conventions for encrypted properties, express messages, databus properties and time to be received. With these conventions combined a reference to NServiceBus can be avoided. \ No newline at end of file diff --git a/nservicebus/operations/auditing.md b/nservicebus/operations/auditing.md index 9f0bed0b3d7..b1d55d80cfe 100644 --- a/nservicebus/operations/auditing.md +++ b/nservicebus/operations/auditing.md @@ -3,8 +3,6 @@ title: Auditing Messages summary: Configure where to send messages and it provides built-in message auditing for every endpoint. component: Core reviewed: 2019-07-22 -tags: - - Audit related: - nservicebus/operations - nservicebus/messaging/headers @@ -108,4 +106,4 @@ Auditing works by sending an exact copy of the received message to the audit que For sensitive properties, e.g. credit card numbers or passwords, use [message property encryption](/nservicebus/security/property-encryption.md). For large properties, consider [streaming](/samples/pipeline/stream-properties/) them instead to avoid including the actual payload in the audited message. -partial: additional-data +partial: additional-data \ No newline at end of file diff --git a/nservicebus/operations/dotnet-framework-version-requirements.md b/nservicebus/operations/dotnet-framework-version-requirements.md index 86caef8fd5e..0a5ac88590f 100644 --- a/nservicebus/operations/dotnet-framework-version-requirements.md +++ b/nservicebus/operations/dotnet-framework-version-requirements.md @@ -4,7 +4,6 @@ summary: List of the .NET Framework requirements for NServiceBus. reviewed: 2019-08-06 related: - nservicebus/operations -tags: redirects: - nservicebus/nservicebus-net-framework-version-requirements --- @@ -33,4 +32,4 @@ Requires [.NET Framework Version 4.0](https://www.microsoft.com/en-au/download/d NServiceBus targets a specific version of the .NET Framework but that does not mean user code must be targeting the same version. This only indicates the *minimum* required .NET Framework. The actual framework used at runtime is determined by the application. -See [Targeting and running .NET Framework apps for version 4.5 and later](https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies#targeting-and-running-net-framework-apps-for-version-45-and-later) and [Version compatibility in the .NET Framework](https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/version-compatibility) for more information. +See [Targeting and running .NET Framework apps for version 4.5 and later](https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies#targeting-and-running-net-framework-apps-for-version-45-and-later) and [Version compatibility in the .NET Framework](https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/version-compatibility) for more information. \ No newline at end of file diff --git a/nservicebus/operations/installers.md b/nservicebus/operations/installers.md index 078edb7b353..616c449b3ed 100644 --- a/nservicebus/operations/installers.md +++ b/nservicebus/operations/installers.md @@ -5,8 +5,6 @@ reviewed: 2020-05-20 component: core related: - nservicebus/operations -tags: - - Installation redirects: - nservicebus/nservicebus-installers --- @@ -50,4 +48,3 @@ Implement the `INeedToInstallSomething` interface to create a custom installer: snippet: InstallSomething Assemblies in the runtime directory are scanned for installers so no code is needed to register them. - diff --git a/nservicebus/operations/management-using-powershell.md b/nservicebus/operations/management-using-powershell.md index 047347a219e..f9d729f43f2 100644 --- a/nservicebus/operations/management-using-powershell.md +++ b/nservicebus/operations/management-using-powershell.md @@ -5,9 +5,6 @@ reviewed: 2018-11-20 isLearningPath: true related: - nservicebus/operations -tags: -- PowerShell -- installation redirects: - nservicebus/managing-nservicebus-using-powershell --- @@ -54,4 +51,4 @@ A list of available cmdlets can be found by issuing the following PowerShell com Get-Command -Module NServiceBus.PowerShell ``` -Help for each cmdlet is incorporated within the module. Help can be accessed via the standard [PowerShell Get-Help Command](https://technet.microsoft.com/en-us/library/ee176848.aspx), e.g. `Get-Help Set-NServiceBusLocalMachineSettings`. +Help for each cmdlet is incorporated within the module. Help can be accessed via the standard [PowerShell Get-Help Command](https://technet.microsoft.com/en-us/library/ee176848.aspx), e.g. `Get-Help Set-NServiceBusLocalMachineSettings`. \ No newline at end of file diff --git a/nservicebus/operations/tuning.md b/nservicebus/operations/tuning.md index 43e9fd03965..305024e8426 100644 --- a/nservicebus/operations/tuning.md +++ b/nservicebus/operations/tuning.md @@ -8,10 +8,6 @@ redirects: - nservicebus/how-to-reduce-throughput-of-an-endpoint - nservicebus/operations/reducing-throughput - nservicebus/operations/throughput -tags: - - performance - - throttling - - concurrency reviewed: 2018-10-10 --- diff --git a/nservicebus/outbox/index.md b/nservicebus/outbox/index.md index a45bfdf5be3..51264c5d9d9 100644 --- a/nservicebus/outbox/index.md +++ b/nservicebus/outbox/index.md @@ -5,8 +5,6 @@ reviewed: 2019-11-25 component: Core isLearningPath: true versions: "[5,)" -tags: -- DTC redirects: - nservicebus/no-dtc related: @@ -113,4 +111,4 @@ For more information on the outbox persistence options available refer to the de - [NHibernate](/persistence/nhibernate/outbox.md) - [RavenDB](/persistence/ravendb/outbox.md) - [SQL](/persistence/sql/outbox.md) -- [ServiceFabric](/persistence/service-fabric/outbox.md) +- [ServiceFabric](/persistence/service-fabric/outbox.md) \ No newline at end of file diff --git a/nservicebus/pipeline/aborting.md b/nservicebus/pipeline/aborting.md index 6cd6340bac2..0019c21a467 100644 --- a/nservicebus/pipeline/aborting.md +++ b/nservicebus/pipeline/aborting.md @@ -3,9 +3,6 @@ title: Aborting Pipeline execution summary: How to tell NServiceBus to abort processing any more handlers in the pipeline component: Core reviewed: 2019-01-15 -tags: -- Pipeline -- Security --- @@ -26,4 +23,4 @@ The pipeline can also be aborted by injecting a custom Behavior that, with some snippet: AbortPipelineWithBehavior -For more information about creating and where to inject a behavior see [customizing the pipeline](/nservicebus/pipeline/manipulate-with-behaviors.md). +For more information about creating and where to inject a behavior see [customizing the pipeline](/nservicebus/pipeline/manipulate-with-behaviors.md). \ No newline at end of file diff --git a/nservicebus/pipeline/events.md b/nservicebus/pipeline/events.md index 0a7b476edab..bb8b6e5007a 100644 --- a/nservicebus/pipeline/events.md +++ b/nservicebus/pipeline/events.md @@ -4,9 +4,6 @@ summary: Subscribe to events raised by the pipeline component: Core reviewed: 2019-01-15 versions: '[6,)' -tags: -- Pipeline -- Notifications related: - nservicebus/recoverability --- @@ -26,4 +23,4 @@ Subscribing from a [feature](/nservicebus/pipeline/features.md) is shown below: snippet: ReceivePipelineCompletedSubscriptionFromFeature -NOTE: A `ReceivePipelineCompleted` event being raised does not guarantee that the message has been removed from the incoming queue. Infrastructure exceptions can still cause the message to be rolled back and reprocessed. +NOTE: A `ReceivePipelineCompleted` event being raised does not guarantee that the message has been removed from the incoming queue. Infrastructure exceptions can still cause the message to be rolled back and reprocessed. \ No newline at end of file diff --git a/nservicebus/pipeline/features.md b/nservicebus/pipeline/features.md index e402277d867..1fbce2c7720 100644 --- a/nservicebus/pipeline/features.md +++ b/nservicebus/pipeline/features.md @@ -4,9 +4,6 @@ summary: Implement a Feature for advanced extension of NServiceBus. reviewed: 2019-02-04 component: Core versions: '[5.0,)' -tags: - - feature - - pipeline related: - samples/feature - samples/header-manipulation @@ -143,4 +140,4 @@ The task will only be created and called if the feature is enabled. The `Feature Note: Avoid long-running operations which will delay the endpoint startup time. -partial: endpointinstance +partial: endpointinstance \ No newline at end of file diff --git a/nservicebus/pipeline/index.md b/nservicebus/pipeline/index.md index 10aa27d456b..af7c4f624d7 100644 --- a/nservicebus/pipeline/index.md +++ b/nservicebus/pipeline/index.md @@ -2,8 +2,6 @@ title: Message Handling Pipeline summary: Overview of the message handling pipeline reviewed: 2020-05-07 -tags: -- Pipeline redirects: - nservicebus/nservicebus-pipeline-intro related: @@ -29,4 +27,4 @@ There are several ways to customize this pipeline with varying levels of complex * [Data Bus](/nservicebus/messaging/databus/) * [Message Property Encryption](/nservicebus/security/property-encryption.md) -* [Recoverability](/nservicebus/recoverability/) +* [Recoverability](/nservicebus/recoverability/) \ No newline at end of file diff --git a/nservicebus/pipeline/manipulate-with-behaviors.md b/nservicebus/pipeline/manipulate-with-behaviors.md index 3ca929a7057..3c610689347 100644 --- a/nservicebus/pipeline/manipulate-with-behaviors.md +++ b/nservicebus/pipeline/manipulate-with-behaviors.md @@ -4,8 +4,6 @@ summary: Manipulating the message-handling pipeline with behaviors component: Core versions: '[4.0,)' reviewed: 2020-05-20 -tags: -- Pipeline related: - nservicebus/pipeline/steps-stages-connectors redirects: @@ -71,4 +69,4 @@ Note: Contexts are not concurrency-safe. partial: sharedcontext -include: mutators-versus-behaviors +include: mutators-versus-behaviors \ No newline at end of file diff --git a/nservicebus/pipeline/message-mutators.md b/nservicebus/pipeline/message-mutators.md index 99bb2473b32..a443f2ce584 100644 --- a/nservicebus/pipeline/message-mutators.md +++ b/nservicebus/pipeline/message-mutators.md @@ -3,8 +3,6 @@ title: Message Mutators summary: Message Mutators allow mutation of messages in the pipeline component: Core reviewed: 2019-09-16 -tags: - - Mutator redirects: - nservicebus/pipeline-management-using-message-mutators related: @@ -73,4 +71,4 @@ If an outgoing mutator throws an exception, the exception bubbles up to the meth partial: nonnulltask -include: mutators-versus-behaviors +include: mutators-versus-behaviors \ No newline at end of file diff --git a/nservicebus/pipeline/steps-stages-connectors.md b/nservicebus/pipeline/steps-stages-connectors.md index c48b7acf81e..83c1251adfd 100644 --- a/nservicebus/pipeline/steps-stages-connectors.md +++ b/nservicebus/pipeline/steps-stages-connectors.md @@ -3,8 +3,6 @@ title: Steps, Stages and Connectors summary: The pipeline is composed of a number of Stages that communicate via Connectors component: Core reviewed: 2019-02-04 -tags: -- Pipeline related: - nservicebus/pipeline/manipulate-with-behaviors --- @@ -15,4 +13,4 @@ There are two explicit pipelines: one for the outgoing messages and one for the Each pipeline is composed of *steps*. A step is an identifiable value in the pipeline used to programmatically define order of execution. Each step represents a behavior which will be executed at the given place within the pipeline. To add additional behavior to the pipeline by registering a new step or replace the behavior of an existing step with the custom implementation. -partial: extra +partial: extra \ No newline at end of file diff --git a/nservicebus/recoverability/configure-delayed-retries.md b/nservicebus/recoverability/configure-delayed-retries.md index 3f937273424..ba6ed71bd7d 100644 --- a/nservicebus/recoverability/configure-delayed-retries.md +++ b/nservicebus/recoverability/configure-delayed-retries.md @@ -3,12 +3,6 @@ title: Configure delayed retries summary: How to configure delayed retries as a second stage of recoverability. component: Core reviewed: 2020-04-26 -tags: - - Error Handling - - Exceptions - - Retry - - Recoverability - - Delayed Retries redirects: - nservicebus/second-level-retries related: @@ -48,4 +42,4 @@ Sometimes the number of retries or the delay interval might depend on the error snippet: DelayedRetriesCustomExceptionPolicyHandler -partial: legacy +partial: legacy \ No newline at end of file diff --git a/nservicebus/recoverability/configure-error-handling.md b/nservicebus/recoverability/configure-error-handling.md index 975aea0d6d9..c0598f4f220 100644 --- a/nservicebus/recoverability/configure-error-handling.md +++ b/nservicebus/recoverability/configure-error-handling.md @@ -3,11 +3,6 @@ title: Configure error handling summary: Error handler configuration when messages are forwarded to the error queue after failing a certain number of times component: Core reviewed: 2020-05-05 -tags: - - Error Handling - - Exceptions - - Retry - - Recoverability redirects: - nservicebus/configure-error-queue related: @@ -43,4 +38,4 @@ If either ServicePulse or ServiceInsight are not available in the environment, t * [MSMQ Scripting](/transports/msmq/operations-scripting.md) * [RabbitMQ Scripting](/transports/rabbitmq/operations-scripting.md) - * [SQL Server Scripting](/transports/sql/operations-scripting.md) + * [SQL Server Scripting](/transports/sql/operations-scripting.md) \ No newline at end of file diff --git a/nservicebus/recoverability/configure-immediate-retries.md b/nservicebus/recoverability/configure-immediate-retries.md index d2df24d642e..3e5ced73894 100644 --- a/nservicebus/recoverability/configure-immediate-retries.md +++ b/nservicebus/recoverability/configure-immediate-retries.md @@ -3,11 +3,6 @@ title: Configure immediate retries summary: Shows how to configure immediate retries which happen as a first stage of the default recoverability behavior. component: Core reviewed: 2018-12-11 -tags: - - Error Handling - - Exceptions - - Retry - - Recoverability related: - samples/faulttolerance --- diff --git a/nservicebus/recoverability/custom-recoverability-policy.md b/nservicebus/recoverability/custom-recoverability-policy.md index 19b09285bd3..57f514ad9bf 100644 --- a/nservicebus/recoverability/custom-recoverability-policy.md +++ b/nservicebus/recoverability/custom-recoverability-policy.md @@ -4,11 +4,6 @@ summary: Shows how to take full control over Recoverability by implementing a Re component: Core reviewed: 2020-01-29 versions: '[6.0,)' -tags: - - Error Handling - - Exceptions - - Retry - - Recoverability related: - samples/faulttolerance --- @@ -96,4 +91,4 @@ partial: fullconfig Note that the `RecoverabilityConfig` will be passed into the custom policy so the code can be fine-tuned based on the configured values. -NOTE: The custom error queue specified by `MoveToError` will not be created by NServiceBus and must be manually created. +NOTE: The custom error queue specified by `MoveToError` will not be created by NServiceBus and must be manually created. \ No newline at end of file diff --git a/nservicebus/recoverability/exception-caveats.md b/nservicebus/recoverability/exception-caveats.md index 150429db518..4984c6fd02e 100644 --- a/nservicebus/recoverability/exception-caveats.md +++ b/nservicebus/recoverability/exception-caveats.md @@ -3,9 +3,6 @@ title: Exception caveats summary: NServiceBus cannot guarantee the handling of certain types of exceptions. component: core reviewed: 2018-12-28 -tags: - - Exceptions - - Error Handling redirects: - nservicebus/errors/exception-caveats --- @@ -31,4 +28,4 @@ If a [`StackOverflowException`](https://docs.microsoft.com/en-us/dotnet/api/syst ## `OutOfMemoryException` -If an [`OutOfMemoryException`](https://docs.microsoft.com/en-us/dotnet/api/system.outofmemoryexception) is thrown, the process may terminate. This is because, even though this exception type is handled in the same way as all others, if the lack of sufficient memory persists, another instance of `OutOfMemoryException` may be thrown while the original exception is being handled. +If an [`OutOfMemoryException`](https://docs.microsoft.com/en-us/dotnet/api/system.outofmemoryexception) is thrown, the process may terminate. This is because, even though this exception type is handled in the same way as all others, if the lack of sufficient memory persists, another instance of `OutOfMemoryException` may be thrown while the original exception is being handled. \ No newline at end of file diff --git a/nservicebus/recoverability/index.md b/nservicebus/recoverability/index.md index 4d7b40402a1..99fe7fa624e 100644 --- a/nservicebus/recoverability/index.md +++ b/nservicebus/recoverability/index.md @@ -3,11 +3,6 @@ title: Recoverability summary: Explains how exceptions are handled, and actions retried, during message processing component: Core isLearningPath: true -tags: - - Exceptions - - Error Handling - - Retry - - Recoverability reviewed: 2018-10-29 redirects: - nservicebus/how-do-i-handle-exceptions @@ -104,4 +99,4 @@ partial: exceptionincluded ## Recoverability memory consumption -MSMQ and SQL Server transport need to cache exceptions in memory for retries. Therefore, exceptions with a large memory footprint can cause high memory usage of the NServiceBus process. NServiceBus can cache up to 1,000 exceptions, capping the potential memory consumption to 1,000 x ``. Refer to [this guide](/nservicebus/recoverability/lru-memory-consumption.md) to resolve problems due to execessive memory consumption. +MSMQ and SQL Server transport need to cache exceptions in memory for retries. Therefore, exceptions with a large memory footprint can cause high memory usage of the NServiceBus process. NServiceBus can cache up to 1,000 exceptions, capping the potential memory consumption to 1,000 x ``. Refer to [this guide](/nservicebus/recoverability/lru-memory-consumption.md) to resolve problems due to execessive memory consumption. \ No newline at end of file diff --git a/nservicebus/recoverability/lru-memory-consumption.md b/nservicebus/recoverability/lru-memory-consumption.md index 41d83910a13..4cd7177a9db 100644 --- a/nservicebus/recoverability/lru-memory-consumption.md +++ b/nservicebus/recoverability/lru-memory-consumption.md @@ -3,11 +3,6 @@ title: Avoiding excessive memory consumption summary: Explains how to avoid excessive memory consumption due to recoverability exception caching component: Core versions: '[6, )' -tags: - - Exceptions - - Error Handling - - Retry - - Recoverability reviewed: 2019-09-09 --- @@ -21,4 +16,4 @@ For example, disposing the response body contained in a `WebException` may signi snippet: dispose-large-exceptions -See [pipeline customization documentation](/nservicebus/pipeline/manipulate-with-behaviors.md) for more details. +See [pipeline customization documentation](/nservicebus/pipeline/manipulate-with-behaviors.md) for more details. \ No newline at end of file diff --git a/nservicebus/sagas/concurrency.md b/nservicebus/sagas/concurrency.md index a003af6e8a7..3b375684ea6 100644 --- a/nservicebus/sagas/concurrency.md +++ b/nservicebus/sagas/concurrency.md @@ -2,8 +2,6 @@ title: Saga concurrency summary: NServiceBus ensures consistency between saga state and messaging. component: Core -tags: -- Saga redirects: - nservicebus/nservicebus-sagas-and-concurrency reviewed: 2019-09-24 @@ -165,4 +163,4 @@ For more methods of redesigning sagas to reduce data contention, see _[Reducing Sometimes, the methods of reducing data contention described above may not be enough. It may be necessary to write a custom saga implementation, where message processing is specifically optimized for the given saga model. For example, append-only models can only be implemented with a custom NHibernate mapping. With a custom implementation, an append-only model could be implemented with other storage types. -A custom saga implementation could simply be a class with multiple message handlers, each of which manages the storage of state in a way that is optimized for the specific use case. +A custom saga implementation could simply be a class with multiple message handlers, each of which manages the storage of state in a way that is optimized for the specific use case. \ No newline at end of file diff --git a/nservicebus/sagas/index.md b/nservicebus/sagas/index.md index 545b23fce14..02ae67bb1e8 100644 --- a/nservicebus/sagas/index.md +++ b/nservicebus/sagas/index.md @@ -3,8 +3,6 @@ title: Sagas summary: NServiceBus uses event-driven architecture to include fault-tolerance and scalability in long-term business processes. component: Core reviewed: 2019-09-16 -tags: -- Saga redirects: - nservicebus/sagas-in-nservicebus related: @@ -195,4 +193,4 @@ Saga state is read immediately before a message processing method is invoked, an - The method of maintaining consistency with respect to concurrent message processing depends on the persister being used. Some may use a transactional lock, and others may perform an atomic change with optimistic concurrency control. - Saga state reads and writes do not occur during a stage. They occur during invocation in the `Invoke Handlers` stage and cannot be intercepted. -If multiple saga types are invoked for the same message, each read, invoke, write cycle will occur sequentially, for each saga type. +If multiple saga types are invoked for the same message, each read, invoke, write cycle will occur sequentially, for each saga type. \ No newline at end of file diff --git a/nservicebus/sagas/message-correlation.md b/nservicebus/sagas/message-correlation.md index db38863cd72..be8ff644294 100644 --- a/nservicebus/sagas/message-correlation.md +++ b/nservicebus/sagas/message-correlation.md @@ -3,8 +3,6 @@ title: Message Correlation summary: Correlation is needed in order to find existing saga instances based on data in the incoming message component: Core reviewed: 2020-01-24 -tags: - - Saga related: - nservicebus/sagas/concurrency --- @@ -50,4 +48,4 @@ NServiceBus will make sure that all properties used for correlation are unique a Mapping a single message to multiple saga instances is not supported. This can be simulated by using a message handler that looks up all saga instance affected and send a separate message targeting each of those instances using the regular correlation described above. -partial: unique +partial: unique \ No newline at end of file diff --git a/nservicebus/sagas/saga-finding.md b/nservicebus/sagas/saga-finding.md index 9333eb16c16..67d18655160 100644 --- a/nservicebus/sagas/saga-finding.md +++ b/nservicebus/sagas/saga-finding.md @@ -3,8 +3,6 @@ title: Complex saga finding logic summary: Use IFindSaga to write custom code that resolves sagas. reviewed: 2019-10-24 component: Core -tags: -- Saga related: - samples/saga/nh-custom-sagafinder - samples/saga/sql-sagafinder @@ -27,4 +25,4 @@ Many finders may exist for a given saga or message type. If a saga can't be foun When using custom saga finders, users are expected to configure any additional indexes needed to handle [concurrent access to saga instances](/nservicebus/sagas/concurrency.md) properly using the tooling of the selected storage engine. Due to this constraint, persisters are not all able to support custom saga finders to the same degree. In instances where saga correlation requires data from more than one property on an incoming message, a better alternative is to use a [message property expression](/nservicebus/sagas/message-correlation.md#message-property-expression) instead of the overhead of a custom saga finder. -}} +}} \ No newline at end of file diff --git a/nservicebus/sagas/saga-not-found.md b/nservicebus/sagas/saga-not-found.md index 179b0dcc3d5..f373f5d81b8 100644 --- a/nservicebus/sagas/saga-not-found.md +++ b/nservicebus/sagas/saga-not-found.md @@ -3,8 +3,6 @@ title: Sagas Not Found summary: How a message is handled when it could be executed by a saga but no saga could be found. component: Core reviewed: 2019-07-17 -tags: -- Saga related: - samples/saga --- @@ -21,4 +19,4 @@ The ability to provide an implementation for `IHandleSagaNotFound` is especially For example, the saga might be used for managing the registration process on the website. After somebody registers, they receive an email with a confirmation link. The system will wait for confirmation for a specific period of time, e.g. 24 hours. If the user doesn't click the link within 24 hours, their data is removed from the system and saga is completed. However, they might decide to click the confirmation link a few days later. In such a case the related saga instance can't be found and an exception will be thrown. By implementing `IHandleSagaNotFound` it is possible to handle the situation differently, e.g. redirect the user to the registration website and ask to fill the form again. -The implementation of `IHandleSagaNotFound` should be driven by the business requirements for a specific situation. In some cases the message might be ignored, in others, it might be useful to track whenever that situation happens (e.g. by logging or sending another message), yet in others, it might make sense to perform a custom compensating action. +The implementation of `IHandleSagaNotFound` should be driven by the business requirements for a specific situation. In some cases the message might be ignored, in others, it might be useful to track whenever that situation happens (e.g. by logging or sending another message), yet in others, it might make sense to perform a custom compensating action. \ No newline at end of file diff --git a/nservicebus/sagas/timeouts.md b/nservicebus/sagas/timeouts.md index cc2cb05a48f..0777be29faf 100644 --- a/nservicebus/sagas/timeouts.md +++ b/nservicebus/sagas/timeouts.md @@ -3,8 +3,6 @@ title: Saga Timeouts summary: Call back into a saga after a defined period of time. reviewed: 2019-12-24 component: Core -tags: -- Saga related: - samples/saga - nservicebus/sagas @@ -69,4 +67,4 @@ Some form of [Persistence](/persistence/) is required to store the timestamp and WARNING: A durable persistence (i.e. NOT [InMemory](/persistence/in-memory/) or [Learning Persistence](/persistence/learning/)) should be chosen before moving to production. -In order to learn how delayed delivery works in more detail, refer to the [Delayed Delivery - How it works](/nservicebus/messaging/delayed-delivery.md#how-it-works) section. +In order to learn how delayed delivery works in more detail, refer to the [Delayed Delivery - How it works](/nservicebus/messaging/delayed-delivery.md#how-it-works) section. \ No newline at end of file diff --git a/nservicebus/security/body-encryption.md b/nservicebus/security/body-encryption.md index 4f175e26418..9a97d5eebad 100644 --- a/nservicebus/security/body-encryption.md +++ b/nservicebus/security/body-encryption.md @@ -3,9 +3,6 @@ title: Message Body Encryption summary: Storing message bodies fully encrypted in the queueing infrastructure component: Core reviewed: 2018-10-11 -tags: -- Encryption -- Security related: - samples/encryption - nservicebus/security @@ -22,4 +19,4 @@ snippet: MessageBodyEncryptor The encrypting mutator must be injected via dependency injection: -snippet: UsingMessageBodyEncryptor +snippet: UsingMessageBodyEncryptor \ No newline at end of file diff --git a/nservicebus/security/generating-encryption-keys.md b/nservicebus/security/generating-encryption-keys.md index acaccfa1f34..58a8112d361 100644 --- a/nservicebus/security/generating-encryption-keys.md +++ b/nservicebus/security/generating-encryption-keys.md @@ -1,9 +1,6 @@ --- title: Generating secure random strong encryption keys summary: Options for generating secure random strong encryption keys -tags: - - Encryption - - Security reviewed: 2018-10-18 related: - nservicebus/security diff --git a/nservicebus/security/index.md b/nservicebus/security/index.md index 06585253046..8282234046e 100644 --- a/nservicebus/security/index.md +++ b/nservicebus/security/index.md @@ -3,9 +3,6 @@ title: Security summary: Security features for messages, transports, and persisters reviewed: 2018-10-11 isLearningPath: true -tags: - - Encryption - - Security redirects: - nservicebus/security/encryption --- @@ -94,4 +91,4 @@ As NServiceBus is layered over the top of existing data stores and queuing techn ## Security Advisories -All releases that are security related are listed under [Security Advisories](/security-advisories/). +All releases that are security related are listed under [Security Advisories](/security-advisories/). \ No newline at end of file diff --git a/nservicebus/security/property-encryption.md b/nservicebus/security/property-encryption.md index 6c469e168ba..39ec1f8e4a1 100644 --- a/nservicebus/security/property-encryption.md +++ b/nservicebus/security/property-encryption.md @@ -3,9 +3,6 @@ title: Message Property Encryption summary: Encrypt message fragments using property encryption component: PropertyEncryption reviewed: 2018-10-11 -tags: -- Encryption -- Security redirects: - nservicebus/encryption related: @@ -155,4 +152,4 @@ This allows explicit handling of the encryption and decryption of each value. So snippet: EncryptionFromIEncryptionService -snippet: EncryptionService +snippet: EncryptionService \ No newline at end of file diff --git a/nservicebus/serialization/custom-serializer.md b/nservicebus/serialization/custom-serializer.md index e5f73f5d3cd..469529fecd9 100644 --- a/nservicebus/serialization/custom-serializer.md +++ b/nservicebus/serialization/custom-serializer.md @@ -4,8 +4,6 @@ summary: How to create and register custom serializer for NServiceBus. component: Core versions: '[5,)' reviewed: 2019-12-25 -tags: -- serialization redirects: - nservicebus/how-to-register-a-custom-serializer --- @@ -26,4 +24,4 @@ To use the customer serializer it must be registered as part of the endpoint con snippet: RegisterCustomSerializer -Note: When using multiple deserializers make sure that there's only one type registered per given `ContentType`. +Note: When using multiple deserializers make sure that there's only one type registered per given `ContentType`. \ No newline at end of file diff --git a/nservicebus/wcf/index.md b/nservicebus/wcf/index.md index 158f01d6c76..d6c4c6975d2 100644 --- a/nservicebus/wcf/index.md +++ b/nservicebus/wcf/index.md @@ -2,8 +2,6 @@ title: Exposing Endpoints via WCF summary: Receiving and processing messages which pass through Windows Communication Foundation component: Wcf -tags: - - Hosting redirects: - nservicebus/how-do-i-expose-an-nservicebus-endpoint-as-a-web-wcf-service - nservicebus/hosting/expose-an-endpoint-as-a-web-wcf-service @@ -88,4 +86,4 @@ When invoke a Web/WCF service as a part of message handling logic, where that lo If no response is required from the Web/WCF service then use [publish-subscribe](/nservicebus/messaging/publish-subscribe/). Have the first endpoint publish an event, to which the second endpoint subscribes, and have the second endpoint call the Web/WCF service. -If a response is required from the Web/WCF service, turn the first endpoint into a [saga](/nservicebus/sagas/) that sends (_not_ publishes) a message to the second endpoint, which calls the Web/WCF service and [replies](/nservicebus/messaging/reply-to-a-message.md) with a response that is handled by the saga in the first endpoint. +If a response is required from the Web/WCF service, turn the first endpoint into a [saga](/nservicebus/sagas/) that sends (_not_ publishes) a message to the second endpoint, which calls the Web/WCF service and [replies](/nservicebus/messaging/reply-to-a-message.md) with a response that is handled by the saga in the first endpoint. \ No newline at end of file diff --git a/persistence/azure-storage/configuration.md b/persistence/azure-storage/configuration.md index 5409f4bddae..284ae825775 100644 --- a/persistence/azure-storage/configuration.md +++ b/persistence/azure-storage/configuration.md @@ -2,9 +2,6 @@ title: Configuration component: ASP summary: Configuring Azure Storage as persistence -tags: - - Azure - - Persistence reviewed: 2019-12-05 redirects: - nservicebus/azure-storage-persistence/configuration @@ -42,4 +39,4 @@ The following settings are available for changing the behavior of subscription p partial: timeouts -For more information on connection string configuration see [Configuring Azure Connection Strings](https://docs.microsoft.com/en-us/azure/storage/storage-configure-connection-string). +For more information on connection string configuration see [Configuring Azure Connection Strings](https://docs.microsoft.com/en-us/azure/storage/storage-configure-connection-string). \ No newline at end of file diff --git a/persistence/azure-storage/index.md b/persistence/azure-storage/index.md index 24f4c026846..5358bf7f9ee 100644 --- a/persistence/azure-storage/index.md +++ b/persistence/azure-storage/index.md @@ -3,11 +3,6 @@ title: Azure Storage Persistence summary: Using Azure Storage as persistence reviewed: 2019-10-01 component: ASP -tags: - - Azure - - Persistence - - Performance - - Hosting related: - persistence/upgrades/asp-saga-deduplication - persistence/upgrades/asp-saga-pruning @@ -82,4 +77,4 @@ partial: saga-property-types Saga correlation property values are subject to the underlying Azure Storage table `PartitionKey` and `RowKey` restrictions: * Up to 1KB in size -* Cannot contain [invalid characters](https://docs.microsoft.com/en-us/rest/api/storageservices/Understanding-the-Table-Service-Data-Model#tables-entities-and-properties) +* Cannot contain [invalid characters](https://docs.microsoft.com/en-us/rest/api/storageservices/Understanding-the-Table-Service-Data-Model#tables-entities-and-properties) \ No newline at end of file diff --git a/persistence/azure-storage/performance-tuning.md b/persistence/azure-storage/performance-tuning.md index e6c63139c92..73217dad1fc 100644 --- a/persistence/azure-storage/performance-tuning.md +++ b/persistence/azure-storage/performance-tuning.md @@ -7,10 +7,6 @@ related: - nservicebus/operations redirects: - nservicebus/azure-storage-persistence/performance-tuning -tags: - - Azure - - Persistence - - Performance --- ## General guidelines @@ -19,4 +15,4 @@ Microsoft's [Azure Storage Performance Checklist](https://docs.microsoft.com/en- ## Disabled secondary index scanning when creating new sagas -A secondary index record was not created by the persister contained in the `NServiceBus.Azure` package. To provide backward compatibility, the `NServiceBus.Persistence.AzureStorage` package performs a full table scan across all partitions for secondary index records before creating a new saga. For systems that have only used the `NServiceBus.Persistence.AzureStorage` library, or have verified that all saga instances have a secondary index record, full table scans can be safely disabled by using the [AssumeSecondaryIndicesExist](/persistence/azure-storage/configuration.md#configuration-properties-saga-configuration) setting. +A secondary index record was not created by the persister contained in the `NServiceBus.Azure` package. To provide backward compatibility, the `NServiceBus.Persistence.AzureStorage` package performs a full table scan across all partitions for secondary index records before creating a new saga. For systems that have only used the `NServiceBus.Persistence.AzureStorage` library, or have verified that all saga instances have a secondary index record, full table scans can be safely disabled by using the [AssumeSecondaryIndicesExist](/persistence/azure-storage/configuration.md#configuration-properties-saga-configuration) setting. \ No newline at end of file diff --git a/persistence/azure-storage/scripting.md b/persistence/azure-storage/scripting.md index b13bdaca423..88a57126633 100644 --- a/persistence/azure-storage/scripting.md +++ b/persistence/azure-storage/scripting.md @@ -7,9 +7,6 @@ related: - nservicebus/operations redirects: - nservicebus/azure-storage-persistence/scripting -tags: -- Azure -- Persistence --- ## Removing subscriptions @@ -83,4 +80,4 @@ Where: * `` is the name of the storage account containing the subscription storage * `` is a key to access the storage account * `` is the configured subscription table. By default this is `Subscription`. This parameter is optional. - * `` is the address of the subscriber which should be removed from the subscription storage + * `` is the address of the subscriber which should be removed from the subscription storage \ No newline at end of file diff --git a/persistence/in-memory/gateway-deduplication.md b/persistence/in-memory/gateway-deduplication.md index f6c46f74fb5..dfa96af7f97 100644 --- a/persistence/in-memory/gateway-deduplication.md +++ b/persistence/in-memory/gateway-deduplication.md @@ -4,12 +4,10 @@ summary: In-memory gateway persistence stores data in a non-durable manner for d component: Gateway versions: '[3.1,)' reviewed: 2019-12-17 -tags: -- Persistence --- DANGER: All information stored is discarded when the process ends. This can result in more-than-once message delivery. The in-memory gateway deduplication persistence uses a least-recently-used (LRU) cache. By default this cache can contain up to 10,000 items. The maximum size can be changed using the following API: -snippet: InMemoryDeduplicationConfigurationCacheSize +snippet: InMemoryDeduplicationConfigurationCacheSize \ No newline at end of file diff --git a/persistence/in-memory/index.md b/persistence/in-memory/index.md index b44a3fda51c..9043dfa2e4d 100644 --- a/persistence/in-memory/index.md +++ b/persistence/in-memory/index.md @@ -5,8 +5,6 @@ component: InMemoryPersistence reviewed: 2019-12-17 redirects: - nservicebus/persistence/in-memory -tags: -- Persistence --- Some scenarios require an in-memory persistence such as the development environment or a lightweight client not interested in durability across restarts: @@ -39,4 +37,4 @@ Example exception: ``` System.Exception: InMemorySagaPersister concurrency violation: saga entity Id[a15a31fd-4f25-4dc3-b556-aad200e52dcb] already saved. -``` +``` \ No newline at end of file diff --git a/persistence/mongodb/document-version.md b/persistence/mongodb/document-version.md index 68e4c870c21..fe76efdf49c 100644 --- a/persistence/mongodb/document-version.md +++ b/persistence/mongodb/document-version.md @@ -3,8 +3,6 @@ title: How document versioning works summary: How the NServiceBus.Storage.MongoDB packages implements concurrency control component: mongodb versions: '[2,)' -tags: - - Persistence related: - persistence/mongodb reviewed: 2019-10-24 @@ -18,4 +16,4 @@ By updating the document with a filter specifying the expected current version v This pattern requires an element in the `BsonDocument` to store the current version value. Instead of requiring the user provide this as a property of their saga data type, this package uses the MongoDB client's BSON serializer to add a version element to the serialized saga data as it is initially created and stored in the collection. When the saga data serialized `BsonDocument` is later fetched, the version element's current value is retrieved before deserializing to the saga data type. The current value is then retained for the lifetime of saga message processing and is used to create the update filter. -By default, the `BsonDocument` element is named `_version`. +By default, the `BsonDocument` element is named `_version`. \ No newline at end of file diff --git a/persistence/mongodb/index.md b/persistence/mongodb/index.md index 5e91569fdfb..6f4228240de 100644 --- a/persistence/mongodb/index.md +++ b/persistence/mongodb/index.md @@ -2,8 +2,6 @@ title: MongoDB Persistence component: mongodb versions: '[2,)' -tags: -- Persistence related: - samples/mongodb redirects: @@ -108,4 +106,4 @@ Example exception: MongoDB.Driver.MongoCommandException: Command update failed: WriteConflict. ``` -include: saga-concurrency +include: saga-concurrency \ No newline at end of file diff --git a/persistence/mongodb/migrating-from-sbmako.md b/persistence/mongodb/migrating-from-sbmako.md index 681b8c533b6..76b955b1b32 100644 --- a/persistence/mongodb/migrating-from-sbmako.md +++ b/persistence/mongodb/migrating-from-sbmako.md @@ -2,8 +2,6 @@ title: Migrating from NServiceBus.MongoDB component: mongodb versions: '[1,)' -tags: - - Persistence related: - persistence/mongodb/migrating-from-tekmaven reviewed: 2019-05-29 diff --git a/persistence/mongodb/migrating-from-tekmaven.md b/persistence/mongodb/migrating-from-tekmaven.md index 7869909af55..424d24af1ba 100644 --- a/persistence/mongodb/migrating-from-tekmaven.md +++ b/persistence/mongodb/migrating-from-tekmaven.md @@ -2,8 +2,6 @@ title: Migrating from NServiceBus.Persistence.MongoDB component: mongodb versions: '[1,)' -tags: - - Persistence related: - persistence/mongodb/migrating-from-sbmako reviewed: 2019-05-29 diff --git a/persistence/nhibernate/accessing-data.md b/persistence/nhibernate/accessing-data.md index 4d7ddcba6e3..2df5e3722b4 100644 --- a/persistence/nhibernate/accessing-data.md +++ b/persistence/nhibernate/accessing-data.md @@ -8,8 +8,6 @@ related: - nservicebus/handlers/accessing-data redirects: - nservicebus/nhibernate/accessing-data -tags: - - Saga --- NHibernate persistence supports a mechanism that allows using the same data context used by NServiceBus internals to also store business data. This ensures atomicity of changes done across multiple handlers and sagas involved in processing of the same message. See [accessing data](/nservicebus/handlers/accessing-data.md) to learn more about other ways of accessing the data in the handlers. diff --git a/persistence/nhibernate/outbox.md b/persistence/nhibernate/outbox.md index ec22a1e78e6..559c6fc7413 100644 --- a/persistence/nhibernate/outbox.md +++ b/persistence/nhibernate/outbox.md @@ -4,8 +4,6 @@ summary: How to use the outbox with NHibernate versions: '[6.0,)' component: NHibernate reviewed: 2020-02-18 -tags: - - Outbox related: - nservicebus/outbox redirects: @@ -31,4 +29,4 @@ snippet: OutboxNHibernateTimeToKeep By specifying a value of `-00:00:00.001` (i.e. 1 millisecond, the value of `Timeout.InfiniteTimeSpan`) for the `NServiceBus/Outbox/NHibernate/FrequencyToRunDeduplicationDataCleanup` app settings, the cleanup task is disabled. This is useful when an endpoint is scaled out and instances are competing to run the cleanup task. -NOTE: It is advised to run the cleanup task on only one NServiceBus endpoint instance per database. Disable the cleanup task on all other NServiceBus endpoint instances for the most efficient cleanup execution. +NOTE: It is advised to run the cleanup task on only one NServiceBus endpoint instance per database. Disable the cleanup task on all other NServiceBus endpoint instances for the most efficient cleanup execution. \ No newline at end of file diff --git a/persistence/nhibernate/saga-concurrency.md b/persistence/nhibernate/saga-concurrency.md index 87e9bedbd01..01edae4c525 100644 --- a/persistence/nhibernate/saga-concurrency.md +++ b/persistence/nhibernate/saga-concurrency.md @@ -4,9 +4,6 @@ summary: How to control concurrency in sagas with the NHibernate persistence component: NHibernate versions: '[6,]' reviewed: 2020-04-07 -tags: - - Persistence - - Saga related: - nservicebus/sagas/concurrency redirects: @@ -57,4 +54,4 @@ snippet: NHibernateConcurrencyLockMode ### Customizing the optimistic concurrency handling -In order to customize or switch off optimistic concurrency handling, the `optimistic-lock` NHibernate attribute has to be specified in a custom mapping. The [custom mapping sample](/samples/nhibernate/custom-mappings) explains how to override the default mapping with a custom one. +In order to customize or switch off optimistic concurrency handling, the `optimistic-lock` NHibernate attribute has to be specified in a custom mapping. The [custom mapping sample](/samples/nhibernate/custom-mappings) explains how to override the default mapping with a custom one. \ No newline at end of file diff --git a/persistence/nhibernate/sql-azure.md b/persistence/nhibernate/sql-azure.md index 613657cd60a..4e985c6aaf0 100644 --- a/persistence/nhibernate/sql-azure.md +++ b/persistence/nhibernate/sql-azure.md @@ -4,8 +4,6 @@ summary: How to configure the NHibernate-based persistence for NServiceBus when component: NHibernate versions: '[6,]' reviewed: 2020-03-20 -tags: - - Persistence related: - persistence/nhibernate/accessing-data redirects: @@ -40,4 +38,4 @@ There are two choices of package for this library. After installation of the package, enable the driver by setting the NHibernate `connection.driver_class` property: -snippet: SqlAzureNHibernateDriverConfiguration +snippet: SqlAzureNHibernateDriverConfiguration \ No newline at end of file diff --git a/persistence/order.md b/persistence/order.md index 33578d2424d..ad17e659c86 100644 --- a/persistence/order.md +++ b/persistence/order.md @@ -4,8 +4,6 @@ summary: When configuring persistence, order is important component: Core reviewed: 2018-10-26 versions: '[5.0,)' -tags: -- Persistence redirects: - nservicebus/persistence-order - nservicebus/persistence/order @@ -32,4 +30,4 @@ snippet: PersistenceOrder_Explicit Instead of explicitly defining all storage types, the generic persistence option can specified before the explicit overwrites. In this example, RavenDB persistence will be used for all storage types except for the outbox and subscriptions. -snippet: PersistenceOrder_Correct +snippet: PersistenceOrder_Correct \ No newline at end of file diff --git a/persistence/ravendb/connection.md b/persistence/ravendb/connection.md index a6dec80934f..dc168de6809 100644 --- a/persistence/ravendb/connection.md +++ b/persistence/ravendb/connection.md @@ -1,8 +1,6 @@ --- title: Connection Options component: raven -tags: - - Persistence related: - samples/ravendb redirects: @@ -35,4 +33,4 @@ After connecting to a RavenDB server, decide which database to use. Unless NServ See also [How to specify endpoint name](/nservicebus/endpoints/specify-endpoint-name.md). -partial: caveats +partial: caveats \ No newline at end of file diff --git a/persistence/ravendb/index.md b/persistence/ravendb/index.md index 6cdfa06bfae..76e4947997d 100644 --- a/persistence/ravendb/index.md +++ b/persistence/ravendb/index.md @@ -2,8 +2,6 @@ title: RavenDB Persistence component: raven versions: '[2,)' -tags: - - Persistence related: - samples/ravendb - samples/multi-tenant/ravendb @@ -78,4 +76,4 @@ partial: subscription-versioning ## Viewing the data -Open a web browser and type the URL of the RavenDB server. This opens the [RavenDB Studio](https://ravendb.net/docs/search/latest/csharp?searchTerm=management-studio). +Open a web browser and type the URL of the RavenDB server. This opens the [RavenDB Studio](https://ravendb.net/docs/search/latest/csharp?searchTerm=management-studio). \ No newline at end of file diff --git a/persistence/ravendb/installation.md b/persistence/ravendb/installation.md index 75f5c96058f..fc0c9193593 100644 --- a/persistence/ravendb/installation.md +++ b/persistence/ravendb/installation.md @@ -3,8 +3,6 @@ title: Installing RavenDB summary: How to install RavenDB when using RavenDB persistence for various versions of NServiceBus. component: core versions: "[3,)" -tags: - - Persistence reviewed: 2019-06-10 related: - nservicebus/operations @@ -26,4 +24,3 @@ RavenDB should only be used for NServiceBus persistence when the endpoint's busi To upgrade an existing RavenDB installation, refer to the [RavenDB upgrade process](https://ravendb.net/docs/search/latest/csharp?searchTerm=server-administration%20upgrade). It is strongly recommended to backup all databases before upgrading. - diff --git a/persistence/ravendb/manual-dtc-settings.md b/persistence/ravendb/manual-dtc-settings.md index 6bcea4c4706..24000a03080 100644 --- a/persistence/ravendb/manual-dtc-settings.md +++ b/persistence/ravendb/manual-dtc-settings.md @@ -3,8 +3,6 @@ title: Configuring RavenDB DTC summary: Guidance on how to change the RavenDB ResourceManagerID and TransactionRecoveryStorage. versions: '[,5)' component: Raven -tags: - - Persistence related: - nservicebus/operations redirects: @@ -77,4 +75,4 @@ The exact convention used must be appropriately defined to match the deployment If an endpoint terminates unexpectedly for any reason, data can be left behind in the transaction recovery storage which represents transactions not yet committed to the RavenDB database, but which may be recovered when the endpoint restarts. -In order to avoid losing data, it is important to ensure that endpoints that are decommissioned are taken offline gracefully, i.e. stopped at the request of the Service Control Manager, and not terminated from the Task Manager. Then, the transaction recovery storage directory should be inspected to ensure it is empty. If any files remain, the endpoint should be started again briefly so that RavenDB can perform a recovery. +In order to avoid losing data, it is important to ensure that endpoints that are decommissioned are taken offline gracefully, i.e. stopped at the request of the Service Control Manager, and not terminated from the Task Manager. Then, the transaction recovery storage directory should be inspected to ensure it is empty. If any files remain, the endpoint should be started again briefly so that RavenDB can perform a recovery. \ No newline at end of file diff --git a/persistence/ravendb/outbox.md b/persistence/ravendb/outbox.md index 26bf2e5d3f5..b4b2b844904 100644 --- a/persistence/ravendb/outbox.md +++ b/persistence/ravendb/outbox.md @@ -3,8 +3,6 @@ title: Outbox with RavenDB persistence component: Raven reviewed: 2019-06-10 versions: '[2.0,)' -tags: - - Outbox related: - nservicebus/outbox redirects: @@ -31,4 +29,4 @@ snippet: OutboxRavendBTimeToKeep partial: cleanup -partial: effect-on-docstore +partial: effect-on-docstore \ No newline at end of file diff --git a/persistence/ravendb/reroute-existing-timeouts.md b/persistence/ravendb/reroute-existing-timeouts.md index 7ca28831a37..ab34859a9cd 100644 --- a/persistence/ravendb/reroute-existing-timeouts.md +++ b/persistence/ravendb/reroute-existing-timeouts.md @@ -4,8 +4,6 @@ summary: How to reroute existing timeouts in the Raven persister when an endpoin component: Raven versions: '[3,)' reviewed: 2019-06-10 -tags: - - Persistence related: - nservicebus/endpoints/decommissioning-endpoints redirects: @@ -16,4 +14,4 @@ include: dtc-warning After moving an endpoint from one machine to another or changing an endpoint's name, existing timeouts must be manually modified to end up in the new endpoint. To do that, follow these steps: -partial: fields +partial: fields \ No newline at end of file diff --git a/persistence/ravendb/subscription-versioning.md b/persistence/ravendb/subscription-versioning.md index e5cebe92d73..5215ecb11aa 100644 --- a/persistence/ravendb/subscription-versioning.md +++ b/persistence/ravendb/subscription-versioning.md @@ -2,9 +2,6 @@ title: Subscription versioning component: raven versions: '[3,6)' -tags: - - Persistence - - Subscription reviewed: 2019-06-10 redirects: - nservicebus/ravendb/subscription-versioning @@ -38,4 +35,4 @@ Because the version has been baked in to the RavenDB document id since the very 1. If possible, do not version message assemblies at all. Design message contracts to be backward and forward compatible so that explicit versioning is not required. 1. Instead of versioning with the [AssemblyVersionAttribute](https://msdn.microsoft.com/en-us/library/system.reflection.assemblyversionattribute.aspx), use the [AssemblyFileVersionAttribute](https://msdn.microsoft.com/en-us/library/system.reflection.assemblyfileversionattribute.aspx) or [AssemblyInformationalVersionAttribute](https://msdn.microsoft.com/en-us/library/system.reflection.assemblyinformationalversionattribute.aspx) instead, while leaving the `AssemblyVersionAttribute` fixed. The RavenDB persister only uses the Major version of the `AssemblyVersionAttribute` as part of the subscription document id. -partial: non-versioned-subscriptions +partial: non-versioned-subscriptions \ No newline at end of file diff --git a/persistence/ravendb/uninstalling-v4.md b/persistence/ravendb/uninstalling-v4.md index bc7de41197e..56a9ede2bed 100644 --- a/persistence/ravendb/uninstalling-v4.md +++ b/persistence/ravendb/uninstalling-v4.md @@ -1,8 +1,6 @@ --- title: Uninstall RavenDB v2.0 summary: Uninstalling RavenDB instances that were installed by previous versions of the Platform Installer. -tags: -- Persistence reviewed: 2019-06-10 redirects: - nservicebus/using-ravendb-uninstalling-v4 @@ -52,4 +50,4 @@ The following PowerShell command will list the directory which can be safely del ```dos dir ("{0}\lib" -f $env:ChocolateyInstall) -Filter *RavenDB* | Select -ExpandProperty FullName -``` +``` \ No newline at end of file diff --git a/persistence/ravendb/version-compatibility.md b/persistence/ravendb/version-compatibility.md index 9427752aa08..161c8df3a10 100644 --- a/persistence/ravendb/version-compatibility.md +++ b/persistence/ravendb/version-compatibility.md @@ -1,8 +1,6 @@ --- title: RavenDB Version Compatibility summary: The various approaches used by different versions of NServiceBus when integrating with RavenDB -tags: -- Persistence reviewed: 2019-06-10 redirects: - nservicebus/ravendb/version-compatibility @@ -100,4 +98,4 @@ In NServiceBus Version 3 the default persistence was changed from NHibernate to ### ILMerged RavenDB client versions * Versions 3.0-3.2 of NServiceBus were shipped with version 1.0.616 of RavenDB ILMerged. - * Version 3.3 of NServiceBus shipped with version 1.0.992 of RavenDB ILMerged. + * Version 3.3 of NServiceBus shipped with version 1.0.992 of RavenDB ILMerged. \ No newline at end of file diff --git a/persistence/sql/installer-workflow.md b/persistence/sql/installer-workflow.md index 75ef5823945..2d1595714ad 100644 --- a/persistence/sql/installer-workflow.md +++ b/persistence/sql/installer-workflow.md @@ -1,8 +1,6 @@ --- title: Installer Workflow component: SqlPersistence -tags: - - Persistence related: - nservicebus/operations - samples/sql-persistence @@ -72,4 +70,4 @@ A sample workflow in that kind of environment can consist of the following steps 1. Scripts are copied to a deployment package along with the output assemblies. 1. Scripts are reviewed by a DBA or QA team and approved. 1. Scripts are executed in higher environment as part of the existing deployment pipeline. Required settings, such as schemas or table prefixes, have different values in each environment. They are passed to scripts together with other configuration settings, such as connection string. - 1. The endpoint is deployed and started. + 1. The endpoint is deployed and started. \ No newline at end of file diff --git a/persistence/sql/outbox.md b/persistence/sql/outbox.md index 4860800d373..3fe02b66b52 100644 --- a/persistence/sql/outbox.md +++ b/persistence/sql/outbox.md @@ -2,8 +2,6 @@ title: Outbox with SQL persistence component: SqlPersistence reviewed: 2020-03-09 -tags: - - Outbox related: - nservicebus/outbox --- @@ -22,4 +20,4 @@ See scripts used for table creation to learn more: [MS SQL Server](/persistence/ By default, the SQL persistence implementation keeps deduplication records for 7 days and runs the purge every minute. -partial: settings +partial: settings \ No newline at end of file diff --git a/samples/azure/blob-storage-databus-cleanup-function/sample.md b/samples/azure/blob-storage-databus-cleanup-function/sample.md index 2a762308f5a..23cd848b661 100644 --- a/samples/azure/blob-storage-databus-cleanup-function/sample.md +++ b/samples/azure/blob-storage-databus-cleanup-function/sample.md @@ -3,9 +3,6 @@ title: Azure Blob Storage Data Bus Cleanup with Azure Functions summary: Using an Azure Function instead of the built in blob cleanup capabilities. component: ABSDataBus reviewed: 2020-04-07 -tags: -- Azure -- DataBus related: - nservicebus/messaging/databus --- @@ -104,4 +101,4 @@ The project sends the `MessageWithLargePayload` message to itself, utilizing the The built-in data bus cleanup functionality for the endpoint is disabled by setting `CleanupInterval` to `0`. -snippet: DisablingDataBusCleanupOnEndpoint +snippet: DisablingDataBusCleanupOnEndpoint \ No newline at end of file diff --git a/samples/azure/blob-storage-databus/sample.md b/samples/azure/blob-storage-databus/sample.md index 6cdf891036d..9f9f9601dd7 100644 --- a/samples/azure/blob-storage-databus/sample.md +++ b/samples/azure/blob-storage-databus/sample.md @@ -3,9 +3,6 @@ title: Azure Blob Storage DataBus summary: Sending large attachments with NServiceBus over Azure blob storage. component: ABSDataBus reviewed: 2018-12-03 -tags: -- Azure -- DataBus related: - nservicebus/messaging/databus - samples/azure/blob-storage-databus-cleanup-function @@ -74,4 +71,4 @@ Go to the `Receiver` project to see the receiving application. Following is the receiving message handler: -snippet: MessageWithLargePayloadHandler +snippet: MessageWithLargePayloadHandler \ No newline at end of file diff --git a/samples/azure/self-host/sample.md b/samples/azure/self-host/sample.md index 4bdb3f51905..7f25b72019c 100644 --- a/samples/azure/self-host/sample.md +++ b/samples/azure/self-host/sample.md @@ -3,9 +3,6 @@ title: Self-Hosting in Azure Cloud Services summary: Using the NServiceBus self-hosting capability to host an endpoint in an Azure instance. component: Core reviewed: 2019-07-02 -tags: -- Azure -- Hosting related: - nservicebus/hosting/cloud-services-host/shared-hosting --- @@ -78,4 +75,4 @@ snippet: AzureSelfHosting_CloudServiceDefinition Values provided to execute the sample against local Azure Storage emulator -snippet: AzureSelfHosting_CloudServiceConfiguration +snippet: AzureSelfHosting_CloudServiceConfiguration \ No newline at end of file diff --git a/samples/azure/shared-host/sample.md b/samples/azure/shared-host/sample.md index 2840c49c69e..b0369aac8f1 100644 --- a/samples/azure/shared-host/sample.md +++ b/samples/azure/shared-host/sample.md @@ -3,9 +3,6 @@ title: Shared Hosting in Azure Cloud Services summary: Uses the NServiceBus Hosting Azure HostProcess to achieve shared hosting of multiple NServiceBus endpoints in an Azure instance. component: CloudServicesHost reviewed: 2019-03-05 -tags: -- Azure -- Hosting related: - nservicebus/hosting/cloud-services-host/shared-hosting --- @@ -103,4 +100,4 @@ snippet: AzureSharedHosting_CloudServiceDefinition Values provided to execute sample against local Azure Storage emulator -snippet: AzureSharedHosting_CloudServiceConfiguration +snippet: AzureSharedHosting_CloudServiceConfiguration \ No newline at end of file diff --git a/samples/azure/storage-persistence/sample.md b/samples/azure/storage-persistence/sample.md index ed82f688f72..f130def3771 100644 --- a/samples/azure/storage-persistence/sample.md +++ b/samples/azure/storage-persistence/sample.md @@ -3,10 +3,6 @@ title: Azure Storage Persistence summary: Using Azure Storage to store Sagas, Timeouts and Subscriptions. component: ASP reviewed: 2019-07-15 -tags: -- Saga -- Timeout -- Subscription related: - nservicebus/sagas - nservicebus/azure @@ -100,4 +96,4 @@ partial: timeouts The Client endpoint registered in the `Subscription` table contents -partial: subscriptions +partial: subscriptions \ No newline at end of file diff --git a/samples/azure/webjob-host/sample.md b/samples/azure/webjob-host/sample.md index a71f7219719..f976e5414fc 100644 --- a/samples/azure/webjob-host/sample.md +++ b/samples/azure/webjob-host/sample.md @@ -4,9 +4,6 @@ summary: Uses NServiceBus the self-hosting capability to host an endpoint in an component: Core reviewed: 2020-02-26 isLearningPath: true -tags: -- Azure -- Hosting related: - samples/dependency-injection/aspnetcore @@ -39,4 +36,4 @@ A critical error action must be defined to restart the host when a critical erro snippet: WebJobHost_CriticalError -When the WebJob host stops, the endpoint endpoint is automatically stopped with the host. This is taken care off by the hosting extension. +When the WebJob host stops, the endpoint endpoint is automatically stopped with the host. This is taken care off by the hosting extension. \ No newline at end of file diff --git a/samples/databus/custom-serializer/sample.md b/samples/databus/custom-serializer/sample.md index 39fb1a366b6..67025cfa633 100644 --- a/samples/databus/custom-serializer/sample.md +++ b/samples/databus/custom-serializer/sample.md @@ -2,8 +2,6 @@ title: Custom Serializer for Data Bus reviewed: 2019-12-11 component: Core -tags: - - DataBus related: - nservicebus/messaging/databus --- @@ -43,4 +41,4 @@ snippet: ConfigureSenderCustomDataBusSerializer The endpoint in the Receiver project must be configured to use the same custom data bus serializer in order to read data bus properties sent by the Sender endpoint: -snippet: ConfigureReceiverCustomDataBusSerializer +snippet: ConfigureReceiverCustomDataBusSerializer \ No newline at end of file diff --git a/samples/databus/index.md b/samples/databus/index.md index 23563f6acef..7b17c1e0f69 100644 --- a/samples/databus/index.md +++ b/samples/databus/index.md @@ -2,8 +2,6 @@ title: Data Bus Samples reviewed: 2019-04-09 component: Core -tags: - - DataBus related: - nservicebus/messaging/databus ---- +--- \ No newline at end of file diff --git a/samples/delayed-delivery/sample.md b/samples/delayed-delivery/sample.md index 10304f2e6d1..c525a87597a 100644 --- a/samples/delayed-delivery/sample.md +++ b/samples/delayed-delivery/sample.md @@ -3,8 +3,6 @@ title: Delayed Delivery summary: A simple ordering system that defers handling or delivery of a message reviewed: 2019-08-20 component: Core -tags: -- Defer related: - nservicebus/messaging/delayed-delivery --- @@ -74,4 +72,4 @@ partial: HandleDefer The `Server` project processes an Order. It receives `PlaceDelayedOrder` sent from `Client` and processes it normally. -snippet: PlaceDelayedOrderHandler +snippet: PlaceDelayedOrderHandler \ No newline at end of file diff --git a/samples/dependency-injection/aspnetcore/sample.md b/samples/dependency-injection/aspnetcore/sample.md index c6fede1c7b7..0cec8c28fc8 100644 --- a/samples/dependency-injection/aspnetcore/sample.md +++ b/samples/dependency-injection/aspnetcore/sample.md @@ -2,8 +2,6 @@ title: ASP.NET Core 3 Dependency Injection Integration component: Extensions.Hosting reviewed: 2020-02-24 -tags: - - dependency injection related: - nservicebus/dependency-injection --- @@ -38,4 +36,4 @@ Then, `Startup` can use Autofac natively to configures services: snippet: ContainerConfigurationAutofac -The [`ConfigureServices` method](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/startup#the-configureservices-method) is called by .NET Core at [application startup time](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/startup) to register additional services. The `ConfigureContainer` method registers the components in the container using the container's native APIs. +The [`ConfigureServices` method](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/startup#the-configureservices-method) is called by .NET Core at [application startup time](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/startup) to register additional services. The `ConfigureContainer` method registers the components in the container using the container's native APIs. \ No newline at end of file diff --git a/samples/dependency-injection/autofac/sample.md b/samples/dependency-injection/autofac/sample.md index fa0e55473eb..54fecf53d79 100644 --- a/samples/dependency-injection/autofac/sample.md +++ b/samples/dependency-injection/autofac/sample.md @@ -2,8 +2,6 @@ title: Autofac Dependency Injection Usage component: Autofac reviewed: 2019-09-10 -tags: - - dependency injection related: - nservicebus/dependency-injection - nservicebus/dependency-injection/autofac @@ -18,4 +16,4 @@ snippet: ContainerConfiguration ### Injecting the dependency in the handler -snippet: InjectingDependency +snippet: InjectingDependency \ No newline at end of file diff --git a/samples/dependency-injection/castle/sample.md b/samples/dependency-injection/castle/sample.md index e8a85ba17af..5619e251fb1 100644 --- a/samples/dependency-injection/castle/sample.md +++ b/samples/dependency-injection/castle/sample.md @@ -2,8 +2,6 @@ title: Windsor Dependency Injection Usage component: Castle reviewed: 2019-09-11 -tags: - - dependency injection related: - nservicebus/dependency-injection - nservicebus/dependency-injection/castlewindsor @@ -18,4 +16,4 @@ snippet: ContainerConfiguration ### Injecting the dependency in the handler -snippet: InjectingDependency +snippet: InjectingDependency \ No newline at end of file diff --git a/samples/dependency-injection/extensions-dependency-injection/sample.md b/samples/dependency-injection/extensions-dependency-injection/sample.md index 12286b4ece6..dadd5c72336 100644 --- a/samples/dependency-injection/extensions-dependency-injection/sample.md +++ b/samples/dependency-injection/extensions-dependency-injection/sample.md @@ -3,8 +3,6 @@ title: NServiceBus.Extensions.DependencyInjection Usage summary: A sample that uses Microsoft's built-in dependency injection container component: Extensions.DependencyInjection reviewed: 2020-02-20 -tags: - - dependency injection related: - nservicebus/dependency-injection - nservicebus/dependency-injection/extensions-dependencyinjection @@ -19,4 +17,4 @@ snippet: ContainerConfiguration ### Injecting the dependency in the handler -snippet: InjectingDependency +snippet: InjectingDependency \ No newline at end of file diff --git a/samples/dependency-injection/ninject/sample.md b/samples/dependency-injection/ninject/sample.md index 4e30962eaf5..95339eb8fad 100644 --- a/samples/dependency-injection/ninject/sample.md +++ b/samples/dependency-injection/ninject/sample.md @@ -2,8 +2,6 @@ title: Ninject Dependency Injection Usage component: Ninject reviewed: 2019-09-11 -tags: - - dependency injection related: - nservicebus/dependency-injection - nservicebus/dependency-injection/ninject @@ -18,4 +16,4 @@ snippet: ContainerConfiguration ### Injecting the dependency in the handler -snippet: InjectingDependency +snippet: InjectingDependency \ No newline at end of file diff --git a/samples/dependency-injection/simpleinjector/sample.md b/samples/dependency-injection/simpleinjector/sample.md index aaf479fc997..d3ead0d3683 100644 --- a/samples/dependency-injection/simpleinjector/sample.md +++ b/samples/dependency-injection/simpleinjector/sample.md @@ -2,8 +2,6 @@ title: SimpleInjector Dependency Injection Usage component: SimpleInjector reviewed: 2019-02-06 -tags: - - dependency injection related: - nservicebus/dependency-injection - nservicebus/dependency-injection/simpleinjector @@ -18,4 +16,4 @@ snippet: ContainerConfiguration ### Injecting the dependency in the handler -snippet: InjectingDependency +snippet: InjectingDependency \ No newline at end of file diff --git a/samples/dependency-injection/spring/sample.md b/samples/dependency-injection/spring/sample.md index 395c4b96fc5..c1d849403ac 100644 --- a/samples/dependency-injection/spring/sample.md +++ b/samples/dependency-injection/spring/sample.md @@ -2,8 +2,6 @@ title: Spring Dependency Injection Usage component: Spring reviewed: 2019-09-11 -tags: - - dependency injection related: - nservicebus/dependency-injection - nservicebus/dependency-injection/spring @@ -18,4 +16,4 @@ snippet: ContainerConfiguration ### Injecting the dependency in the handler -snippet: InjectingDependency +snippet: InjectingDependency \ No newline at end of file diff --git a/samples/dependency-injection/structuremap/sample.md b/samples/dependency-injection/structuremap/sample.md index fa3a5cc59c5..929c8232a14 100644 --- a/samples/dependency-injection/structuremap/sample.md +++ b/samples/dependency-injection/structuremap/sample.md @@ -2,8 +2,6 @@ title: StructureMap Dependency Injection Usage component: StructureMap reviewed: 2019-09-11 -tags: - - dependency injection related: - nservicebus/dependency-injection - nservicebus/dependency-injection/structuremap @@ -18,4 +16,4 @@ snippet: ContainerConfiguration ### Injecting the dependency in the handler -snippet: InjectingDependency +snippet: InjectingDependency \ No newline at end of file diff --git a/samples/dependency-injection/unity/sample.md b/samples/dependency-injection/unity/sample.md index 294e0011587..80d52715db2 100644 --- a/samples/dependency-injection/unity/sample.md +++ b/samples/dependency-injection/unity/sample.md @@ -2,8 +2,6 @@ title: Unity Dependency Injection Usage component: Unity reviewed: 2019-09-16 -tags: -- dependency injection related: - nservicebus/dependency-injection - nservicebus/dependency-injection/unity @@ -18,4 +16,4 @@ snippet: ContainerConfiguration ### Injecting the dependency in the handler -snippet: InjectingDependency +snippet: InjectingDependency \ No newline at end of file diff --git a/samples/encryption/basic-encryption/sample.md b/samples/encryption/basic-encryption/sample.md index a43f74b2ff2..a19c9664f31 100644 --- a/samples/encryption/basic-encryption/sample.md +++ b/samples/encryption/basic-encryption/sample.md @@ -3,12 +3,10 @@ title: Message property encryption summary: Encrypting specific parts of a message using the message property encryption feature. reviewed: 2018-12-11 component: PropertyEncryption -tags: -- Encryption redirects: - nservicebus/encryption-sample --- This sample demonstrates how to use `EncryptedString` to encrypt and decrypt specific properties of a message as it passes through the pipeline. -include: encryption-sample +include: encryption-sample \ No newline at end of file diff --git a/samples/encryption/encryption-conventions/sample.md b/samples/encryption/encryption-conventions/sample.md index b6e4ebeb3dc..b3814bce2ee 100644 --- a/samples/encryption/encryption-conventions/sample.md +++ b/samples/encryption/encryption-conventions/sample.md @@ -3,11 +3,8 @@ title: Unobtrusive property encryption summary: Encrypting specific parts of a message using conventions. reviewed: 2018-12-11 component: PropertyEncryption -tags: -- Encryption -- Unobtrusive --- This sample demonstrates how to use conventions to encrypt and decrypt specific properties of a message as it passes through the pipeline. -include: encryption-sample +include: encryption-sample \ No newline at end of file diff --git a/samples/encryption/message-body-encryption/sample.md b/samples/encryption/message-body-encryption/sample.md index 65a0e6112a7..f91bdad543a 100644 --- a/samples/encryption/message-body-encryption/sample.md +++ b/samples/encryption/message-body-encryption/sample.md @@ -3,8 +3,6 @@ title: Message body encryption summary: Encrypting the full message body using a mutator. reviewed: 2018-12-11 component: Core -tags: -- Encryption related: - nservicebus/security - nservicebus/security/property-encryption @@ -55,4 +53,4 @@ The mutator is in `Shared/MessageEncryptor.cs`: WARNING: This is for demonstration purposes and is not true encryption. It is only doing a byte array reversal to illustrate the API. In a production system, encryption should be performed used the [.NET Framework Cryptography Model](https://docs.microsoft.com/en-us/dotnet/standard/security/cryptography-model) or some other secure mechanism. -snippet: Mutator +snippet: Mutator \ No newline at end of file diff --git a/samples/errorhandling/sample.md b/samples/errorhandling/sample.md index fad10c3e0c0..2763a6020ad 100644 --- a/samples/errorhandling/sample.md +++ b/samples/errorhandling/sample.md @@ -3,11 +3,6 @@ title: Automatic Retries summary: Shows immediate and delayed retries when a handler throws an exception. reviewed: 2018-11-14 component: Core -tags: -- Delayed Retries -- Error Handling -- Exceptions -- Retry related: - nservicebus/recoverability --- diff --git a/samples/feature/sample.md b/samples/feature/sample.md index 4f4a4b3956a..74d06e39ca7 100644 --- a/samples/feature/sample.md +++ b/samples/feature/sample.md @@ -3,9 +3,6 @@ title: Building a Custom Feature summary: How to build a custom feature in NServiceBus reviewed: 2019-11-25 component: Core -tags: -- Pipeline -- Feature related: - nservicebus/pipeline - nservicebus/pipeline/features @@ -58,4 +55,4 @@ snippet: SagaStateAuditFeature The [pipeline behavior](/nservicebus/pipeline/manipulate-with-behaviors.md) that captures the saga state. -snippet: SagaStateAuditBehavior +snippet: SagaStateAuditBehavior \ No newline at end of file diff --git a/samples/file-share-databus/sample.md b/samples/file-share-databus/sample.md index 1ace1de1699..fe7e3206f47 100644 --- a/samples/file-share-databus/sample.md +++ b/samples/file-share-databus/sample.md @@ -2,8 +2,6 @@ title: File Share Data Bus Usage reviewed: 2019-12-12 component: FileShareDataBus -tags: - - DataBus redirects: - nservicebus/attachments-databus-sample related: @@ -81,4 +79,4 @@ In both cases, a 5MB message is sent, but the `MessageWithLargePayload` message This is the receiving message handler: -snippet: MessageWithLargePayloadHandler +snippet: MessageWithLargePayloadHandler \ No newline at end of file diff --git a/samples/fullduplex/sample.md b/samples/fullduplex/sample.md index 955e9335376..bebd012bc72 100644 --- a/samples/fullduplex/sample.md +++ b/samples/fullduplex/sample.md @@ -3,8 +3,6 @@ title: Full Duplex summary: Using full-duplex and request/response communication. reviewed: 2019-09-16 component: Core -tags: -- Messaging Patterns redirects: - nservicebus/full-duplex-sample --- @@ -58,4 +56,4 @@ Look back at `ClientEndpoint.cs` to see that it gets the header information from Open `DataResponseMessageHandler.cs` in the `Client` project and find a class whose signature looks similar to the message handler on the server: -snippet: DataResponseMessageHandler +snippet: DataResponseMessageHandler \ No newline at end of file diff --git a/samples/header-manipulation/sample.md b/samples/header-manipulation/sample.md index e6133f3c884..26f62d0c774 100644 --- a/samples/header-manipulation/sample.md +++ b/samples/header-manipulation/sample.md @@ -3,10 +3,6 @@ title: Header Manipulation summary: All extension points for mutating messages. reviewed: 2019-09-16 component: Core -tags: -- Header -- Mutator -- Pipeline related: - samples/messagemutators - samples/pipeline @@ -96,4 +92,4 @@ snippet: global-all-outgoing While the current contextual headers can be read in any of the above scenarios, in this sample all headers will be written from the receiving handler. -snippet: handler +snippet: handler \ No newline at end of file diff --git a/samples/hosting/docker/sample.md b/samples/hosting/docker/sample.md index 59adb2352d2..a301873dd6f 100644 --- a/samples/hosting/docker/sample.md +++ b/samples/hosting/docker/sample.md @@ -3,8 +3,6 @@ title: Hosting endpoints in Docker Linux containers summary: Hosting multiple endpoints in several Docker Linux containers managed by Docker Compose reviewed: 2019-12-16 component: Core -tags: -- Hosting related: - nservicebus/hosting/docker-host - nservicebus/hosting @@ -83,4 +81,4 @@ snippet: TransportConfiguration ### Waiting for RabbitMQ broker to become available -This sample takes advantage of Docker [healthchecks](https://docs.docker.com/engine/reference/builder/#healthcheck) to ensure RabbitMQ is available before starting the endpoints. +This sample takes advantage of Docker [healthchecks](https://docs.docker.com/engine/reference/builder/#healthcheck) to ensure RabbitMQ is available before starting the endpoints. \ No newline at end of file diff --git a/samples/hosting/generic-host/sample.md b/samples/hosting/generic-host/sample.md index a7e4e171a3a..34ea0495a82 100644 --- a/samples/hosting/generic-host/sample.md +++ b/samples/hosting/generic-host/sample.md @@ -3,8 +3,6 @@ title: Endpoint hosting with the Generic Host summary: Hosting an endpoint with the Generic Host. reviewed: 2020-02-27 component: Core -tags: -- Hosting related: - nservicebus/hosting - nservicebus/hosting/assembly-scanning @@ -68,4 +66,4 @@ snippet: generic-host-worker-registration The worker takes a dependency on `IServiceProvider` in order to retrieve the message session. This is required because all hosted services are resolved from the container first and then started in the order of having been added. Therefore it is not possible to inject `IMessageSession` directly because the hosted service that starts the NServiceBus endpoint has not been started yet when the worker service constructor is being resolved from the container. -snippet: generic-host-worker +snippet: generic-host-worker \ No newline at end of file diff --git a/samples/hosting/multi-hosting/sample.md b/samples/hosting/multi-hosting/sample.md index cb8d88ab98a..eeb3006dbc6 100644 --- a/samples/hosting/multi-hosting/sample.md +++ b/samples/hosting/multi-hosting/sample.md @@ -3,8 +3,6 @@ title: Endpoints multi hosting summary: Hosting multiple endpoints in one process. reviewed: 2019-09-16 component: Core -tags: -- Hosting related: - nservicebus/hosting - nservicebus/hosting/assembly-scanning @@ -20,4 +18,4 @@ One important thing to keep in mind is that [dependency injection](/nservicebus/ snippet: multi-hosting-assembly-scan -NOTE: This is possible only when self-hosting and not using NServiceBus.Host +NOTE: This is possible only when self-hosting and not using NServiceBus.Host \ No newline at end of file diff --git a/samples/hosting/nservicebus-host/sample.md b/samples/hosting/nservicebus-host/sample.md index 0f6b9a148de..f29ae4a3803 100644 --- a/samples/hosting/nservicebus-host/sample.md +++ b/samples/hosting/nservicebus-host/sample.md @@ -3,8 +3,6 @@ title: The NServiceBus.Host summary: Hosting an NServiceBus endpoint using the NServiceBus.Host. reviewed: 2019-11-25 component: Host -tags: -- Hosting related: - nservicebus/hosting/nservicebus-host - nservicebus/lifecycle @@ -23,4 +21,4 @@ snippet: nservicebus-host Since the configuration is done via an implementation of `IConfigureThisEndpoint` and the host controls the startup process there is no regular way to run code at startup and stop of the endpoint. To enable this scenario, there is an interface that is assembly scanned and executed at these times. -snippet: RunWhenStartsAndStops +snippet: RunWhenStartsAndStops \ No newline at end of file diff --git a/samples/logging/application-insights/sample.md b/samples/logging/application-insights/sample.md index 084393f4955..b3e8c289ce7 100644 --- a/samples/logging/application-insights/sample.md +++ b/samples/logging/application-insights/sample.md @@ -4,8 +4,6 @@ summary: How to report NServiceBus metrics data to Azure Monitor Application Ins component: Metrics isLearningPath: true reviewed: 2019-07-23 -tags: -- Azure related: - monitoring/metrics - samples/azure @@ -100,4 +98,4 @@ Similar for events, the following graphs show all events grouped by event name. Refer to the Microsoft documentation for more information on [creating dashboards from the metrics explorer](https://docs.microsoft.com/en-us/azure/application-insights/app-insights-dashboards). -Using the metrics explorer is an easy way to get started, but to create truly advanced graphs, App Insights offers an [advanced analytics environment](https://docs.microsoft.com/en-us/azure/application-insights/app-insights-analytics). +Using the metrics explorer is an easy way to get started, but to create truly advanced graphs, App Insights offers an [advanced analytics environment](https://docs.microsoft.com/en-us/azure/application-insights/app-insights-analytics). \ No newline at end of file diff --git a/samples/logging/commonlogging/sample.md b/samples/logging/commonlogging/sample.md index 959844a3ce2..e12038c9219 100644 --- a/samples/logging/commonlogging/sample.md +++ b/samples/logging/commonlogging/sample.md @@ -3,8 +3,6 @@ title: CommonLogging Usage summary: Using CommonLogging logging capability of NServiceBus. reviewed: 2019-07-30 component: CommonLogging -tags: -- Logging related: - nservicebus/logging --- diff --git a/samples/logging/custom-factory/sample.md b/samples/logging/custom-factory/sample.md index f7ef9e46c9b..b96de1e5e82 100644 --- a/samples/logging/custom-factory/sample.md +++ b/samples/logging/custom-factory/sample.md @@ -3,8 +3,6 @@ title: Custom Logger Factory summary: Illustrates a custom implementation of a logging factory. reviewed: 2019-07-30 component: Core -tags: - - Logging related: - nservicebus/logging --- diff --git a/samples/logging/default/sample.md b/samples/logging/default/sample.md index 1e77f703530..8138069ed68 100644 --- a/samples/logging/default/sample.md +++ b/samples/logging/default/sample.md @@ -3,8 +3,6 @@ title: Default Logging summary: The default logging capability of NServiceBus. reviewed: 2019-08-06 component: Core -tags: -- Logging related: - nservicebus/logging --- @@ -22,4 +20,4 @@ Inside the `[path_to_the_sample]\Core_6\Sample\bin\[Debug/Release]` directory sh ### Enabling Logging -snippet: ConfigureLogging +snippet: ConfigureLogging \ No newline at end of file diff --git a/samples/logging/eventsourcelogging/sample.md b/samples/logging/eventsourcelogging/sample.md index 82965b8a7c0..faa60f725b2 100644 --- a/samples/logging/eventsourcelogging/sample.md +++ b/samples/logging/eventsourcelogging/sample.md @@ -3,8 +3,6 @@ title: Using EventSourceLogging reviewed: 2019-07-23 component: EventSourceLogging summary: Illustrates writing log entries to event tracing for Windows (ETW). -tags: -- Logging related: - nservicebus/logging --- @@ -14,4 +12,4 @@ related: Illustrates writing log entries to [event tracing for Windows (ETW)](https://blogs.msdn.microsoft.com/vancem/2012/08/13/windows-high-speed-logging-etw-in-c-net-using-system-diagnostics-tracing-eventsource/) using [EventSourceLogging](https://github.com/robv8r/NServiceBus.EventSourceLogging). -include: eventsourcelogging +include: eventsourcelogging \ No newline at end of file diff --git a/samples/logging/extensions-logging/sample.md b/samples/logging/extensions-logging/sample.md index 38473eed610..363140e7902 100644 --- a/samples/logging/extensions-logging/sample.md +++ b/samples/logging/extensions-logging/sample.md @@ -3,8 +3,6 @@ title: NServiceBus.Extensions.Logging Usage summary: A sample that uses Microsoft.Extensions.Logging with NLog component: Extensions.Logging reviewed: 2020-03-26 -tags: - - logging related: - nservicebus/logging --- @@ -40,4 +38,4 @@ The following snippet shows how to initialize logging. NLog has its own provider snippet: MicrosoftExtensionsLoggingNLog -After logging initialization endpoints can be started or created. +After logging initialization endpoints can be started or created. \ No newline at end of file diff --git a/samples/logging/hostcustom/sample.md b/samples/logging/hostcustom/sample.md index f6976fdb017..891d3faaea7 100644 --- a/samples/logging/hostcustom/sample.md +++ b/samples/logging/hostcustom/sample.md @@ -3,8 +3,6 @@ title: Host Custom Logging summary: Customize logging when running inside the NServiceBus host. reviewed: 2019-08-09 component: Host -tags: -- Logging related: - nservicebus/logging --- @@ -17,4 +15,4 @@ This sample shows how to customize logging when running inside the [NServiceBus ## Configuring logging -snippet: Config +snippet: Config \ No newline at end of file diff --git a/samples/logging/hostprofiles/sample.md b/samples/logging/hostprofiles/sample.md index 5c58d285a81..30c8c12eda0 100644 --- a/samples/logging/hostprofiles/sample.md +++ b/samples/logging/hostprofiles/sample.md @@ -3,8 +3,6 @@ title: Host Profile Logging summary: Configure logging using the profile functionality of the NServiceBus host. reviewed: 2019-08-09 component: Host -tags: -- Logging related: - nservicebus/logging --- @@ -49,4 +47,4 @@ snippet: LiteHandler #### Production -snippet: ProductionHandler +snippet: ProductionHandler \ No newline at end of file diff --git a/samples/logging/log4net-custom/sample.md b/samples/logging/log4net-custom/sample.md index e27ef459be5..aa914a7cf4a 100644 --- a/samples/logging/log4net-custom/sample.md +++ b/samples/logging/log4net-custom/sample.md @@ -3,8 +3,6 @@ title: Custom Log4Net appender summary: Customizing Log4Net by passing in a custom Appender. reviewed: 2019-08-09 component: Log4Net -tags: -- Logging related: - nservicebus/logging --- @@ -26,4 +24,4 @@ snippet: UseConfig -include: verifyLoggingSample +include: verifyLoggingSample \ No newline at end of file diff --git a/samples/logging/nlog-custom/sample.md b/samples/logging/nlog-custom/sample.md index be88dc2ba06..7c26f719da1 100644 --- a/samples/logging/nlog-custom/sample.md +++ b/samples/logging/nlog-custom/sample.md @@ -3,8 +3,6 @@ title: Custom NLog configuration summary: Customizing NLog usage by configuring NLog targets and rules. reviewed: 2019-08-09 component: NLog -tags: -- Logging related: - nservicebus/logging --- @@ -25,4 +23,4 @@ snippet: ConfigureNLog snippet: UseConfig -include: verifyLoggingSample +include: verifyLoggingSample \ No newline at end of file diff --git a/samples/logging/stack-trace-cleaning/sample.md b/samples/logging/stack-trace-cleaning/sample.md index 844dff2693c..77932e5ca1c 100644 --- a/samples/logging/stack-trace-cleaning/sample.md +++ b/samples/logging/stack-trace-cleaning/sample.md @@ -3,9 +3,6 @@ title: Stack Trace Cleaning summary: Shows how to minimize the stack trace written to the Error queue and the log output. reviewed: 2019-07-22 component: Core -tags: -- Pipeline -- Logging related: - nservicebus/pipeline - nservicebus/logging @@ -184,4 +181,4 @@ at NServiceBus.ProcessingStatisticsBehavior.<Invoke>d__0.MoveNext() in C:\ at NServiceBus.ReceivePerformanceDiagnosticsBehavior.<Invoke>d__2.MoveNext() in C:\Build\src\NServiceBus.Core\Performance\Statistics\ReceivePerformanceDiagnosticsBehavior.cs:line 40 at NServiceBus.TransportReceiveToPhysicalMessageProcessingConnector.<Invoke>d__1.MoveNext() in C:\Build\src\NServiceBus.Core\Pipeline\Incoming\TransportReceiveToPhysicalMessageProcessingConnector.cs:line 38 at NServiceBus.MoveFaultsToErrorQueueBehavior.<Invoke>d__3.MoveNext() in C:\Build\src\NServiceBus.Core\Recoverability\Faults\MoveFaultsToErrorQueueBehavior.cs:line 38 -``` +``` \ No newline at end of file diff --git a/samples/message-error-handling/sample.md b/samples/message-error-handling/sample.md index 91ac4438d35..27a1dde631b 100644 --- a/samples/message-error-handling/sample.md +++ b/samples/message-error-handling/sample.md @@ -3,10 +3,6 @@ title: Custom Exception Handling summary: With custom exception handling, it is possible to fine-tune how exceptions should be handled after they have been retried reviewed: 2019-02-15 component: Core -tags: - - Error Handling - - Exceptions - - Retry related: - nservicebus/recoverability - nservicebus/pipeline/customizing-error-handling @@ -24,4 +20,4 @@ To register the new exception handler: snippet: registering-behavior -Beware of swallowing exceptions though, since it is almost never intended and the message will be removed from the queue, as if it has been processed successfully. +Beware of swallowing exceptions though, since it is almost never intended and the message will be removed from the queue, as if it has been processed successfully. \ No newline at end of file diff --git a/samples/messagemutators/sample.md b/samples/messagemutators/sample.md index 3133e14879d..8bcbb5a8eb1 100644 --- a/samples/messagemutators/sample.md +++ b/samples/messagemutators/sample.md @@ -3,8 +3,6 @@ title: Message Mutators summary: Change messages by plugging custom logic in to a couple of interfaces, encrypting as required. reviewed: 2019-09-16 component: Core -tags: -- Mutator redirects: - nservicebus/nservicebus-message-mutators-sample related: @@ -91,4 +89,4 @@ The message is invalid for several reasons: the product name is over the 20 char The receiver is straightforward. There is no special code to handle validation or compression since this is done by the logical and transport message mutators. -snippet: Handler +snippet: Handler \ No newline at end of file diff --git a/samples/mongodb/simple/sample.md b/samples/mongodb/simple/sample.md index 62c86c836eb..c4858ed2577 100644 --- a/samples/mongodb/simple/sample.md +++ b/samples/mongodb/simple/sample.md @@ -3,8 +3,6 @@ title: MongoDB Persistence summary: Using MongoDB to store sagas. reviewed: 2019-05-29 component: mongodb -tags: -- Saga related: - nservicebus/sagas redirects: diff --git a/samples/nhibernate/simple/sample.md b/samples/nhibernate/simple/sample.md index 15f44d3c891..e225555008c 100644 --- a/samples/nhibernate/simple/sample.md +++ b/samples/nhibernate/simple/sample.md @@ -3,9 +3,6 @@ title: Simple NHibernate Persistence Usage summary: Using NHibernate to store sagas and timeouts. reviewed: 2020-01-27 component: NHibernate -tags: - - Saga - - Timeout related: - nservicebus/sagas - persistence @@ -69,4 +66,4 @@ Data in the database is stored in three different tables. ### The handler stored data -![](handlerdoc.png) +![](handlerdoc.png) \ No newline at end of file diff --git a/samples/outbox/sql/sample.md b/samples/outbox/sql/sample.md index b531148cdfc..78cd419519b 100644 --- a/samples/outbox/sql/sample.md +++ b/samples/outbox/sql/sample.md @@ -3,8 +3,6 @@ title: Using Outbox with SQL summary: Integrating SQL Server Transport with SQL Persistence and ADO.net user data store using outbox. reviewed: 2019-04-16 component: Core -tags: - - Outbox related: - transports/sql - persistence/sql @@ -82,4 +80,4 @@ snippet: Timeout Once the Outbox transaction is committed, both the business data changes and the outgoing messages are durably stored in the database. Finally the messages in the Outbox are pushed to their destinations. The timeout message gets stored in the NServiceBus timeout store and is sent back to the saga after requested delay of 5 seconds. -See [Accessing the ambient database details](/samples/sqltransport-sqlpersistence/#receiver-project-accessing-the-ambient-database-details) for using a variety of other ORMs. +See [Accessing the ambient database details](/samples/sqltransport-sqlpersistence/#receiver-project-accessing-the-ambient-database-details) for using a variety of other ORMs. \ No newline at end of file diff --git a/samples/pipeline/audit-filtering/sample.md b/samples/pipeline/audit-filtering/sample.md index cf70cd477af..6485cf33118 100644 --- a/samples/pipeline/audit-filtering/sample.md +++ b/samples/pipeline/audit-filtering/sample.md @@ -3,9 +3,6 @@ title: Audit Filter Pipeline Extension summary: Extending the pipeline to stop certain messages from being audited reviewed: 2019-01-09 component: Core -tags: - - Pipeline - - Audit related: - nservicebus/pipeline - nservicebus/operations/auditing diff --git a/samples/pipeline/dispatch-notifications/sample.md b/samples/pipeline/dispatch-notifications/sample.md index 00efe47d190..25ac508e1d9 100644 --- a/samples/pipeline/dispatch-notifications/sample.md +++ b/samples/pipeline/dispatch-notifications/sample.md @@ -3,8 +3,6 @@ title: Dispatch notification pipeline extension summary: Extending the pipeline to fire a notification when messages are dispatched. reviewed: 2019-07-01 component: Core -tags: - - Pipeline related: - nservicebus/pipeline --- @@ -47,4 +45,4 @@ The behavior notifies all of the watches after the transport operations have bee * Run the solution. * Press any key other than Escape to send a message - * As the message is dispatched to the transport, the registered watches are invoked. One writes the details of the dispatch operations to the console. + * As the message is dispatched to the transport, the registered watches are invoked. One writes the details of the dispatch operations to the console. \ No newline at end of file diff --git a/samples/pipeline/feature-toggle/sample.md b/samples/pipeline/feature-toggle/sample.md index 94764db2aba..fa1560d0037 100644 --- a/samples/pipeline/feature-toggle/sample.md +++ b/samples/pipeline/feature-toggle/sample.md @@ -3,8 +3,6 @@ title: Add feature toggles to handlers summary: Checks feature toggles to determine whether or not a handler should be executed for a given message. reviewed: 2019-05-20 component: Core -tags: -- Pipeline related: - nservicebus/pipeline --- diff --git a/samples/pipeline/handler-timer/sample.md b/samples/pipeline/handler-timer/sample.md index 5c96f5ffe0b..31597111161 100644 --- a/samples/pipeline/handler-timer/sample.md +++ b/samples/pipeline/handler-timer/sample.md @@ -3,8 +3,6 @@ title: Add handler timing pipeline summary: Wraps handlers in a Stopwatch and logs a warning if a handler exceeds a given threshold. reviewed: 2019-11-08 component: Core -tags: -- Pipeline related: - nservicebus/pipeline --- @@ -28,4 +26,4 @@ snippet: HandlerTimerBehavior ## Configuring the Pipeline -snippet: pipeline-config +snippet: pipeline-config \ No newline at end of file diff --git a/samples/pipeline/message-signing/sample.md b/samples/pipeline/message-signing/sample.md index faf10da3ae5..1eda5e1479c 100644 --- a/samples/pipeline/message-signing/sample.md +++ b/samples/pipeline/message-signing/sample.md @@ -3,8 +3,6 @@ title: Message signing using the pipeline summary: Shows how to implement message signing and verification using NServiceBus pipeline behaviors. reviewed: 2019-10-03 component: Core -tags: - - Pipeline related: - samples/pipeline/handler-timer - samples/pipeline/unit-of-work @@ -80,4 +78,4 @@ snippet: EnableSigning The extensibility offered by the NServiceBus pipeline easily allows plugging in behaviors that enable message signing and verification. While this sample shows message signing, the same pattern could be leveraged to provide full end-to-end encryption of the message body. -Rather than trying to configure all the different options (cipher selection, key storage, key rotation, etc.) on a one-size-fits-all solution, implementing an infrastructure solution with behaviors requires only the minimum amount of code necessary to fit a system's exact nonfunctional requirements. +Rather than trying to configure all the different options (cipher selection, key storage, key rotation, etc.) on a one-size-fits-all solution, implementing an infrastructure solution with behaviors requires only the minimum amount of code necessary to fit a system's exact nonfunctional requirements. \ No newline at end of file diff --git a/samples/pipeline/multi-serializer/sample.md b/samples/pipeline/multi-serializer/sample.md index 382d3b17b6e..5dbaa450e0f 100644 --- a/samples/pipeline/multi-serializer/sample.md +++ b/samples/pipeline/multi-serializer/sample.md @@ -3,9 +3,6 @@ title: Control of serialization via the pipeline summary: Add support for attribute based message serialization. reviewed: 2018-11-07 component: Core -tags: -- Pipeline -- Serialization related: - nservicebus/pipeline - nservicebus/serialization @@ -105,4 +102,4 @@ Now have a look at the [Learning Transport's message storage](/transports/learni ```js {"SomeProperty":"Some content in a json message"} -``` +``` \ No newline at end of file diff --git a/samples/pipeline/session-filtering/sample.md b/samples/pipeline/session-filtering/sample.md index 35c783fb131..5e3f49d3c77 100644 --- a/samples/pipeline/session-filtering/sample.md +++ b/samples/pipeline/session-filtering/sample.md @@ -3,8 +3,6 @@ title: Session filter pipeline extension summary: How to extend the pipeline to filter out messages from older sessions. reviewed: 2019-10-04 component: Core -tags: - - Pipeline related: - nservicebus/pipeline --- diff --git a/samples/pipeline/stream-properties/sample.md b/samples/pipeline/stream-properties/sample.md index 4ef19f848a8..3c91e6bb885 100644 --- a/samples/pipeline/stream-properties/sample.md +++ b/samples/pipeline/stream-properties/sample.md @@ -3,8 +3,6 @@ title: Handling Stream Properties Via the Pipeline summary: Add support for writing streams to a file share that can be accessed by multiple endpoints. reviewed: 2019-12-11 component: Core -tags: -- Pipeline related: - nservicebus/pipeline --- @@ -97,4 +95,4 @@ snippet: message-with-stream-handler ## Difference to the databus -The [built-in database](/nservicebus/messaging/databus/) relies on byte arrays and memory streams to operate. As such, there are limits to the amount of data that it can send. +The [built-in database](/nservicebus/messaging/databus/) relies on byte arrays and memory streams to operate. As such, there are limits to the amount of data that it can send. \ No newline at end of file diff --git a/samples/pipeline/unit-of-work/sample.md b/samples/pipeline/unit-of-work/sample.md index 94d996ca86a..30dce06d9d3 100644 --- a/samples/pipeline/unit-of-work/sample.md +++ b/samples/pipeline/unit-of-work/sample.md @@ -3,8 +3,6 @@ title: Unit of work using the pipeline summary: Shows how to use IoC and the pipeline to create a unit of work implementation. reviewed: 2018-10-26 component: Core -tags: - - Pipeline related: - nservicebus/pipeline - nservicebus/pipeline/unit-of-work @@ -56,4 +54,4 @@ snippet: message-handlers ## Running the sample -Run the sample. Once running press any key to send messages. Note that for each given message the two message handlers will get the same session instance. +Run the sample. Once running press any key to send messages. Note that for each given message the two message handlers will get the same session instance. \ No newline at end of file diff --git a/samples/pubsub/sample.md b/samples/pubsub/sample.md index c6e35a7c50c..8cd4913062f 100644 --- a/samples/pubsub/sample.md +++ b/samples/pubsub/sample.md @@ -3,9 +3,6 @@ title: Publish/Subscribe summary: Publish/Subscribe, fault-tolerant messaging, and durable subscriptions. reviewed: 2018-11-14 component: Core -tags: - - Publish Subscribe - - Messaging Patterns redirects: - nservicebus/publish-subscribe-sample related: diff --git a/samples/ravendb/simple/sample.md b/samples/ravendb/simple/sample.md index f4a6d748909..48398fb32e9 100644 --- a/samples/ravendb/simple/sample.md +++ b/samples/ravendb/simple/sample.md @@ -2,9 +2,6 @@ title: Simple RavenDB Persistence Usage summary: Using RavenDB to store Sagas and Timeouts. component: Raven -tags: - - Saga - - Timeout related: - nservicebus/sagas - persistence/ravendb @@ -92,4 +89,4 @@ Note that the message type maps to multiple subscriber endpoints. ### The Handler Stored data -![](handlerdoc.png) +![](handlerdoc.png) \ No newline at end of file diff --git a/samples/routing/command-routing/sample.md b/samples/routing/command-routing/sample.md index a9ae8cb57f2..bef30a559b0 100644 --- a/samples/routing/command-routing/sample.md +++ b/samples/routing/command-routing/sample.md @@ -3,8 +3,6 @@ title: Command routing summary: Basic NServiceBus message routing component: Core reviewed: 2019-10-09 -tags: -- Routing --- The sample demonstrates basic command routing between endpoints. @@ -30,4 +28,4 @@ snippet: send-command-with-configured-route This is enabled by configuring a message route for the `PlaceOrder` command in the endpoint configuration. -snippet: configure-command-route +snippet: configure-command-route \ No newline at end of file diff --git a/samples/routing/fair-distribution/sample.md b/samples/routing/fair-distribution/sample.md index b32d5c6487e..1d01c02708d 100644 --- a/samples/routing/fair-distribution/sample.md +++ b/samples/routing/fair-distribution/sample.md @@ -3,8 +3,6 @@ title: Fair Load Distribution summary: Implementing fair load distribution for heterogeneous scaled-out endpoints component: Core reviewed: 2020-05-25 -tags: -- Routing --- This sample demonstrates how to extend the NServiceBus routing model with a custom distribution strategy. Distribution strategies replace the distributor feature as a scale-out mechanism for MSMQ. The default built-in distribution strategy uses a simple round-robin approach. This sample shows a more sophisticated distribution strategy that keeps the queue length of all load-balanced instances equal, allowing for the effective use of non-heterogeneous worker clusters. diff --git a/samples/routing/file-based-routing/sample.md b/samples/routing/file-based-routing/sample.md index 1bf85f734a0..d1a6d7e90e4 100644 --- a/samples/routing/file-based-routing/sample.md +++ b/samples/routing/file-based-routing/sample.md @@ -3,9 +3,6 @@ title: Using centralized routing configuration summary: Using file to control message routing in entire NServiceBus system reviewed: 2018-11-15 component: FileBasedRouting -tags: - - Routing - - MSMQ related: - nservicebus/messaging/file-based-routing --- @@ -43,4 +40,4 @@ snippet: endpoints For the purpose of the sample, the file is stored in the local file system. The routing mechanism based on the contents of the file is enabled by following code: -snippet: FileBasedRouting +snippet: FileBasedRouting \ No newline at end of file diff --git a/samples/routing/fowarding-address/sample.md b/samples/routing/fowarding-address/sample.md index dba61070f04..0b1d46fce92 100644 --- a/samples/routing/fowarding-address/sample.md +++ b/samples/routing/fowarding-address/sample.md @@ -3,8 +3,6 @@ title: Forwarding address summary: Implementing forwarding address for in-flight messages during handler migration component: Core reviewed: 2019-06-25 -tags: -- Routing --- When a handler is moved to a new endpoint, there may still be "in-flight" messages, bound for the original endpoint. When those messages arrive at the original endpoint, they need to be re-routed to the new endpoint. @@ -85,4 +83,4 @@ snippet: forwarding-routing-extensions ### Messages -A shared assembly containing the `ImportantMessage` message type. +A shared assembly containing the `ImportantMessage` message type. \ No newline at end of file diff --git a/samples/routing/instance-mapping-file/sample.md b/samples/routing/instance-mapping-file/sample.md index c79b8d99f4a..7c68b2e3011 100644 --- a/samples/routing/instance-mapping-file/sample.md +++ b/samples/routing/instance-mapping-file/sample.md @@ -3,9 +3,6 @@ title: Mapping Endpoint Instances With a Shared File summary: Mapping logical endpoints to physical instances with a shared file reviewed: 2020-05-27 component: Core -tags: - - Routing - - MSMQ --- The sample demonstrates how to use a file to describe the mapping between logical endpoints and their physical instances (i.e. deployments of a given logical endpoint to a concrete virtual machine). @@ -68,4 +65,4 @@ The shared project contains definitions for messages. ## Real-world scenario -For the sake of simplicity, all the endpoints in this sample run on a single machine. In production, it is recommended to run each instance on a separate virtual machine. In this case, the instance mapping file would contain `machine` attributes mapping instances to their machines' host names instead of `queue` attributes used to run more than one instance on a single box. +For the sake of simplicity, all the endpoints in this sample run on a single machine. In production, it is recommended to run each instance on a separate virtual machine. In this case, the instance mapping file would contain `machine` attributes mapping instances to their machines' host names instead of `queue` attributes used to run more than one instance on a single box. \ No newline at end of file diff --git a/samples/saga/migration/sample.md b/samples/saga/migration/sample.md index f94385685e7..f8445648d79 100644 --- a/samples/saga/migration/sample.md +++ b/samples/saga/migration/sample.md @@ -3,8 +3,6 @@ title: Migrating saga persistence summary: How to migrate from one type of saga persistence to another without an off-line migration procedure component: Core reviewed: 2019-10-04 -tags: -- Saga related: - nservicebus/sagas - persistence/nhibernate @@ -122,4 +120,4 @@ Once all the sagas stored in the old persister are complete, the old endpoint ca 1. Stop the old endpoint ("Server"). 1. Update the binaries and/or configuration of the old endpoint with the binaries and configuration of the new endpoint. Enable the redirection of the temporary queue. 1. Start the endpoint. - 1. The redirection of temporary queue can be removed when there are no timeout messages for the temporary queue (e.g. by running a query like `SELECT [Destination], [SagaId] FROM [NsbSamplesSagaMigration].[dbo].[NewTimeoutData] WHERE [Destination] =
`. + 1. The redirection of temporary queue can be removed when there are no timeout messages for the temporary queue (e.g. by running a query like `SELECT [Destination], [SagaId] FROM [NsbSamplesSagaMigration].[dbo].[NewTimeoutData] WHERE [Destination] =
`. \ No newline at end of file diff --git a/samples/saga/nh-custom-sagafinder/sample.md b/samples/saga/nh-custom-sagafinder/sample.md index fc5a2b42183..3db418cdf26 100644 --- a/samples/saga/nh-custom-sagafinder/sample.md +++ b/samples/saga/nh-custom-sagafinder/sample.md @@ -3,9 +3,6 @@ title: NHibernate Custom Saga Finding Logic summary: Perform custom saga finding logic based on custom query logic when the Saga storage is a relational database using NHibernate as the ORM. component: NHibernate reviewed: 2019-05-08 -tags: -- Saga -- SagaFinder related: - nservicebus/sagas - persistence/nhibernate @@ -38,4 +35,4 @@ snippet: finder include: sagafinder-ifindsagas -include: sagafinder-configurehowtofindsaga +include: sagafinder-configurehowtofindsaga \ No newline at end of file diff --git a/samples/saga/simple/sample.md b/samples/saga/simple/sample.md index 484d086e72a..41a49eeb077 100644 --- a/samples/saga/simple/sample.md +++ b/samples/saga/simple/sample.md @@ -3,9 +3,6 @@ title: Simple Saga Usage summary: How build and use a saga. reviewed: 2019-03-01 component: Core -tags: -- Saga -- SagaFinder redirects: - samples/saga/complexfindinglogic related: @@ -59,4 +56,4 @@ snippet: thesaga This is a helper class used by the sample to derive the storage locations of the [Learning Transport](/transports/learning/) and the [Learning Persistence](/persistence/learning/). -snippet: LearningLocationHelper +snippet: LearningLocationHelper \ No newline at end of file diff --git a/samples/saga/sql-sagafinder/sample.md b/samples/saga/sql-sagafinder/sample.md index e55efed364d..d9a434ab21f 100644 --- a/samples/saga/sql-sagafinder/sample.md +++ b/samples/saga/sql-sagafinder/sample.md @@ -3,9 +3,6 @@ title: SQL Persistence Saga Finding Logic summary: Perform custom saga finding logic based on custom query logic when the Saga storage is the native SQL Persistence component: SqlPersistence reviewed: 2019-01-24 -tags: -- Saga -- SagaFinder related: - nservicebus/sagas - persistence/sql @@ -59,4 +56,4 @@ snippet: SqlServerFinder snippet: MySqlFinder -partial: postgresfinder +partial: postgresfinder \ No newline at end of file diff --git a/samples/scaleout/distributor-upgrade/sample.md b/samples/scaleout/distributor-upgrade/sample.md index 99280099aa1..673eece4fcf 100644 --- a/samples/scaleout/distributor-upgrade/sample.md +++ b/samples/scaleout/distributor-upgrade/sample.md @@ -3,8 +3,6 @@ title: Upgrading a Distributor endpoint from Version 5 to 6 summary: Upgrading an existing scaled-out endpoint that uses Distributor to version 6 of NServiceBus reviewed: 2019-11-06 component: Core -tags: -- Scalability related: - transports/msmq/distributor --- @@ -97,4 +95,4 @@ Because the sender still uses Version 5 and the workers are on Version 6, the sh After the upgrade is done both worker projects are identical (apart from the configuration file). The sender needed only a minor routing correction. -NOTE: When Version 5 nodes enlist with the distributor, they use GUID-based queues that are created each time the worker starts. This behavior is suppressed in the sample via a configuration switch. In Versions 6 and above when worker nodes enlists with the distributor, they always use their regular input queues with stable names. +NOTE: When Version 5 nodes enlist with the distributor, they use GUID-based queues that are created each time the worker starts. This behavior is suppressed in the sample via a configuration switch. In Versions 6 and above when worker nodes enlists with the distributor, they always use their regular input queues with stable names. \ No newline at end of file diff --git a/samples/scaleout/senderside/sample.md b/samples/scaleout/senderside/sample.md index 7746c574a3a..fe7a91208cb 100644 --- a/samples/scaleout/senderside/sample.md +++ b/samples/scaleout/senderside/sample.md @@ -3,8 +3,6 @@ title: Sender-Side Distribution summary: Scale out MSMQ message processing with sender-side distribution reviewed: 2019-09-03 component: MsmqTransport -tags: - - Scalability related: - transports/msmq/scaling-out - transports/msmq/sender-side-distribution @@ -64,4 +62,4 @@ snippet: Physical-Routes Start the solution with all the console applications (`Server1`, `Server2`, `Client`) as startup applications. -In the `Client` console, press enter a few times to generate message load. This results in both the `Server1` and `Server2` consoles processing the generated message load in an alternating fashion. This is because the messages are sent in a round-robin fashion to `Server1` and `Server2` by the client using the [sender-side distribution feature](/transports/msmq/sender-side-distribution.md). +In the `Client` console, press enter a few times to generate message load. This results in both the `Server1` and `Server2` consoles processing the generated message load in an alternating fashion. This is because the messages are sent in a round-robin fashion to `Server1` and `Server2` by the client using the [sender-side distribution feature](/transports/msmq/sender-side-distribution.md). \ No newline at end of file diff --git a/samples/servicecontrol/events-subscription/sample.md b/samples/servicecontrol/events-subscription/sample.md index 33c96a5ae1b..eadd527e99e 100644 --- a/samples/servicecontrol/events-subscription/sample.md +++ b/samples/servicecontrol/events-subscription/sample.md @@ -3,8 +3,6 @@ title: Monitor with ServiceControl events summary: A sample showing how to monitor events in ServiceControl component: ServiceControlContracts reviewed: 2018-12-18 -tags: - - Notifications related: - servicecontrol - servicecontrol/contracts @@ -92,4 +90,4 @@ This sample uses the [Learning Transport](/transports/learning/) in order to be If adjusting this sample to use the [Azure Service Bus transport](/transports/azure-service-bus/legacy/), note that the subscribing endpoint must also use the same name shortening strategy as ServiceControl. See the [configuration settings](/transports/azure-service-bus/configuration.md#entity-creation), or if using the [legacy Azure Service Bus transport](), see its [sanitization strategy documentation](/transports/azure-service-bus/legacy/sanitization.md). -Same applies to [Azure Storage Queues](/transports/azure-storage-queues) name [sanitization strategy](/transports/azure-storage-queues/sanitization.md#backward-compatibility-with-versions-7-and-below) +Same applies to [Azure Storage Queues](/transports/azure-storage-queues) name [sanitization strategy](/transports/azure-storage-queues/sanitization.md#backward-compatibility-with-versions-7-and-below) \ No newline at end of file diff --git a/samples/sql-persistence/saga-rename/sample.md b/samples/sql-persistence/saga-rename/sample.md index 09e79d642ec..8fa3ae55f96 100644 --- a/samples/sql-persistence/saga-rename/sample.md +++ b/samples/sql-persistence/saga-rename/sample.md @@ -3,9 +3,6 @@ title: SQL Persistence Saga Rename summary: Renaming a saga that is stored in the SQL Persistence reviewed: 2020-01-27 component: SqlPersistence -tags: - - Saga - - Timeout related: - nservicebus/sagas --- @@ -173,4 +170,4 @@ where json_value(Headers, '$."NServiceBus.OriginatingSagaType"') The mutator is registered at endpoint startup. -snippet: registerMutator +snippet: registerMutator \ No newline at end of file diff --git a/samples/sql-persistence/simple/sample.md b/samples/sql-persistence/simple/sample.md index c33f21753c0..058d05f2e9e 100644 --- a/samples/sql-persistence/simple/sample.md +++ b/samples/sql-persistence/simple/sample.md @@ -3,9 +3,6 @@ title: Simple SQL Persistence Usage summary: Using SQL Persistence to store sagas and timeouts. reviewed: 2020-03-26 component: SqlPersistence -tags: - - Saga - - Timeout related: - nservicebus/sagas --- @@ -88,4 +85,3 @@ snippet: sagadata ## Order Saga snippet: thesaga - diff --git a/samples/throttling/sample.md b/samples/throttling/sample.md index 3dd00d9ac71..9b7c165e6d7 100644 --- a/samples/throttling/sample.md +++ b/samples/throttling/sample.md @@ -2,8 +2,6 @@ title: Message Throughput Throttling reviewed: 2019-05-06 component: Core -tags: -- Throttling related: - nservicebus/pipeline/manipulate-with-behaviors - nservicebus/operations/tuning @@ -62,4 +60,4 @@ snippet: RegisterBehavior Handles the detection of `Octokit.RateLimitExceededException` and defers the message. -snippet: ThrottlingBehavior +snippet: ThrottlingBehavior \ No newline at end of file diff --git a/samples/unobtrusive/sample.md b/samples/unobtrusive/sample.md index dfd7556d299..806ab65ccf2 100644 --- a/samples/unobtrusive/sample.md +++ b/samples/unobtrusive/sample.md @@ -3,11 +3,6 @@ title: Unobtrusive summary: Demonstrates NServiceBus operating in unobtrusive mode. reviewed: 2019-05-06 component: Core -tags: -- Unobtrusive -- Command -- Event -- Convention redirects: - nservicebus/unobtrusive-sample related: @@ -31,4 +26,4 @@ Look at the code. There are a number of projects in the solution: * **Client**: sends a request and a command to the server and handles a published event * **Server**: handles requests and commands, and publishes events - * **Shared**: the shared message definitions + * **Shared**: the shared message definitions \ No newline at end of file diff --git a/samples/wcf/sample.md b/samples/wcf/sample.md index 4446aa2d581..a54ce1cf341 100644 --- a/samples/wcf/sample.md +++ b/samples/wcf/sample.md @@ -3,8 +3,6 @@ title: WCF to messaging bridge summary: Reliable WCF communication over messaging. component: Wcf reviewed: 2019-06-25 -tags: - - Hosting related: - nservicebus/wcf --- @@ -43,4 +41,4 @@ snippet: wcf-proxy-call The proxy waits, asynchronously, until the response or cancellation is received. A response is sent from a regular handler hosted in the same endpoint: -snippet: wcf-reply-handler +snippet: wcf-reply-handler \ No newline at end of file diff --git a/security-advisories/asq-alias-for-default-connectionstring.md b/security-advisories/asq-alias-for-default-connectionstring.md index b7173c0ad48..9614f9d92d2 100644 --- a/security-advisories/asq-alias-for-default-connectionstring.md +++ b/security-advisories/asq-alias-for-default-connectionstring.md @@ -2,9 +2,6 @@ title: Security Advisory 2018-01-19 summary: Azure Storage Queues vulnerability reviewed: 2019-10-18 -tags: - - Transport - - Security --- This advisory discloses a security vulnerability that has been found in Azure Storage Queues version 7 and fixed in the released hotfixes 7.5.3 and 7.4.3. @@ -77,4 +74,4 @@ Update the NuGet package using `Update-Package NServiceBus.Azure.Transports.Wind ## Contact Info -If there are any questions or concerns regarding this advisory, send an email to [security@particular.net](mailto://security@particular.net). +If there are any questions or concerns regarding this advisory, send an email to [security@particular.net](mailto://security@particular.net). \ No newline at end of file diff --git a/security-advisories/msmq-permissions.md b/security-advisories/msmq-permissions.md index 79cac5fb99b..bfd6e3b2a14 100644 --- a/security-advisories/msmq-permissions.md +++ b/security-advisories/msmq-permissions.md @@ -2,10 +2,6 @@ title: Security Advisory 2017-01-10 summary: MSMQ permissions vulnerability reviewed: 2018-11-20 -tags: - - MSMQ - - Transport - - Security --- This advisory discloses a security vulnerability that has been found in NServiceBus and fixed in a recently released hotfix. @@ -80,4 +76,4 @@ Update the NuGet package using `Update-Package NServiceBus`, stop affected endpo ## Contact Info -If there are any questions or concerns regarding this advisory, send an email to [security@particular.net](mailto://security@particular.net). +If there are any questions or concerns regarding this advisory, send an email to [security@particular.net](mailto://security@particular.net). \ No newline at end of file diff --git a/security-advisories/servicepulse-directorytraversal.md b/security-advisories/servicepulse-directorytraversal.md index e5d50ea2981..7dcd442e085 100644 --- a/security-advisories/servicepulse-directorytraversal.md +++ b/security-advisories/servicepulse-directorytraversal.md @@ -2,8 +2,6 @@ title: Security Advisory 2020-03-11 summary: ServicePulse directory traversal vulnerability reviewed: 2020-03-11 -tags: - - Security --- This advisory discloses a security vulnerability that has been found in [ServicePulse](/servicepulse/) and fixed in a recently released version. @@ -44,4 +42,4 @@ This vulnerability can be fixed by upgrading ServicePulse to the latest version. ### Contact info -If there are any questions or concerns regarding this advisory, contact [security@particular.net](mailto://security@particular.net). +If there are any questions or concerns regarding this advisory, contact [security@particular.net](mailto://security@particular.net). \ No newline at end of file diff --git a/security-advisories/sqlserver-sqlinjection.md b/security-advisories/sqlserver-sqlinjection.md index 07b58510583..6834706a40d 100644 --- a/security-advisories/sqlserver-sqlinjection.md +++ b/security-advisories/sqlserver-sqlinjection.md @@ -2,9 +2,6 @@ title: Security Advisory 2016-07-05 summary: NServiceBus SQL Server Transport injection vulnerability reviewed: 2018-12-09 -tags: - - Transport - - Security --- This advisory discloses a security vulnerability that has been found in the [SQL Server Transport](/transports/sql/) and fixed in a recently released version. @@ -81,4 +78,4 @@ Download the NuGet package using `Update-Package NServiceBus.SqlServer -Pre`, st ### Contact info -If there are any questions or concerns regarding this advisory, contact [security@particular.net](mailto://security@particular.net). +If there are any questions or concerns regarding this advisory, contact [security@particular.net](mailto://security@particular.net). \ No newline at end of file diff --git a/servicecontrol/audit-instances/installation-powershell.md b/servicecontrol/audit-instances/installation-powershell.md index 9f3287f17dc..06276c3fb4f 100644 --- a/servicecontrol/audit-instances/installation-powershell.md +++ b/servicecontrol/audit-instances/installation-powershell.md @@ -1,9 +1,6 @@ --- title: Managing ServiceControl Audit instances via PowerShell reviewed: 2019-07-09 -tags: - - Installation - - PowerShell --- NOTE: For general information about ServiceControl PowerShell, including troubleshooting and licensing guidance, see [Managing ServiceControl via PowerShell](/servicecontrol/powershell.md). @@ -93,4 +90,4 @@ Use the following command to find a list of all of the ServiceControl Audit inst Get-ServiceControlAuditInstances | Select Name, Version ``` -The upgrade will stop the service if it is running. Additional parameters for `Invoke-ServiceControlAuditInstanceUpgrade` may be required. The configuration file of the existing version is examined prior to determine if all the required settings are present. If a configuration setting is missing then the cmdlet will throw an error indicating the required additional parameter. +The upgrade will stop the service if it is running. Additional parameters for `Invoke-ServiceControlAuditInstanceUpgrade` may be required. The configuration file of the existing version is examined prior to determine if all the required settings are present. If a configuration setting is missing then the cmdlet will throw an error indicating the required additional parameter. \ No newline at end of file diff --git a/servicecontrol/contracts.md b/servicecontrol/contracts.md index 3f8bc2bc607..41fc45e2407 100644 --- a/servicecontrol/contracts.md +++ b/servicecontrol/contracts.md @@ -4,8 +4,6 @@ summary: Build custom notifications by subscribing to ServiceControl events reviewed: 2020-03-30 component: ServiceControlContracts isLearningPath: true -tags: - - Notifications redirects: - servicepulse/custom-notification-and-alerting-using-servicecontol-events - servicepulse/custom-notification-and-alerting-using-servicecontrol-events @@ -93,4 +91,4 @@ An event will also be published and displayed in the ServicePulse dashboard with 'EVENTTYPE' failed to be published to other integration points. Reason for failure: REASON. ``` -To avoid this situation it is important to properly decommission an endpoint that subscribes to ServiceControl events. To do this, [disable auto-subscription](/nservicebus/messaging/publish-subscribe/controlling-what-is-subscribed.md#disabling-auto-subscription) and then [unsubscribe from all events](/nservicebus/messaging/publish-subscribe/controlling-what-is-subscribed.md#manually-subscribing-to-a-message). +To avoid this situation it is important to properly decommission an endpoint that subscribes to ServiceControl events. To do this, [disable auto-subscription](/nservicebus/messaging/publish-subscribe/controlling-what-is-subscribed.md#disabling-auto-subscription) and then [unsubscribe from all events](/nservicebus/messaging/publish-subscribe/controlling-what-is-subscribed.md#manually-subscribing-to-a-message). \ No newline at end of file diff --git a/servicecontrol/how-purge-expired-data.md b/servicecontrol/how-purge-expired-data.md index 8e2071bd093..14c5f67196d 100644 --- a/servicecontrol/how-purge-expired-data.md +++ b/servicecontrol/how-purge-expired-data.md @@ -4,11 +4,9 @@ summary: Configuring ServiceControl's data retention policy related: - nservicebus/recoverability - nservicebus/operations/auditing -tags: -- Expiration reviewed: 2018-10-05 --- ServiceControl stores audit and error data. Any audit and error data that is older than the specified thresholds is deleted from the embedded RavenDB. The expiration thresholds for both faulted and audited messages must be set during installation. These values can be modified later by launching ServiceControl Management and editing the configuration settings for the instance. -Note: The expiration process curates only the data in the embedded RavenDB. Audit and error forwarding queues are not curated or managed by ServiceControl. To turn these settings off, launch ServiceControl Management and edit the configuration settings for the instance. +Note: The expiration process curates only the data in the embedded RavenDB. Audit and error forwarding queues are not curated or managed by ServiceControl. To turn these settings off, launch ServiceControl Management and edit the configuration settings for the instance. \ No newline at end of file diff --git a/servicecontrol/installation-powershell.md b/servicecontrol/installation-powershell.md index 3b96b1a3226..7b0fdf20603 100644 --- a/servicecontrol/installation-powershell.md +++ b/servicecontrol/installation-powershell.md @@ -1,9 +1,6 @@ --- title: Manage ServiceControl instances via PowerShell reviewed: 2019-07-02 -tags: - - Installation - - PowerShell --- NOTE: For general information about using PowerShell with ServiceControl, including troubleshooting and licensing guidance, see [Managing ServiceControl via PowerShell](/servicecontrol/powershell.md). @@ -143,4 +140,4 @@ Use the following command to find a list of all of the ServiceControl Audit inst ```ps Get-ServiceControlAuditInstances | Select Name, Version -``` +``` \ No newline at end of file diff --git a/servicecontrol/installation.md b/servicecontrol/installation.md index 6d263e3fcc9..9211a57ea8f 100644 --- a/servicecontrol/installation.md +++ b/servicecontrol/installation.md @@ -1,8 +1,6 @@ --- title: Installing ServiceControl reviewed: 2020-03-16 -tags: - - Installation redirects: - servicecontrol/multi-transport-support --- @@ -162,4 +160,4 @@ NOTE: If the instance was configured to run under a service account then that ac To uninstall ServiceControl Management, use the `Apps & features` settings in Windows. -NOTE: Uninstalling the ServiceControl Management application will not remove existing instances. Remove all ServiceControl instances using ServiceControl Management before uninstalling the application itself. +NOTE: Uninstalling the ServiceControl Management application will not remove existing instances. Remove all ServiceControl instances using ServiceControl Management before uninstalling the application itself. \ No newline at end of file diff --git a/servicecontrol/license.md b/servicecontrol/license.md index a952101694b..996a027da4c 100644 --- a/servicecontrol/license.md +++ b/servicecontrol/license.md @@ -1,8 +1,6 @@ --- title: Licensing ServiceControl reviewed: 2018-10-10 -tags: - - license --- There are a few options to add a license to ServiceControl. @@ -60,4 +58,4 @@ NOTE: Instance Licensing is deprecated in Version 1.18 and above. Use ServiceCon ### ServiceControl license was updated, but ServicePulse reports the license has expired -License information is read at service startup and cached for 8 hours. Therefore, either wait for the cache to expire or restart the ServiceControl instance manually to have ServicePulse reflect the new license. +License information is read at service startup and cached for 8 hours. Therefore, either wait for the cache to expire or restart the ServiceControl instance manually to have ServicePulse reflect the new license. \ No newline at end of file diff --git a/servicecontrol/logging.md b/servicecontrol/logging.md index 2aef5c90674..8aa075582db 100644 --- a/servicecontrol/logging.md +++ b/servicecontrol/logging.md @@ -1,8 +1,6 @@ --- title: Logging reviewed: 2018-10-10 -tags: -- Logging redirects: - servicecontrol/setting-custom-log-location --- @@ -105,4 +103,4 @@ Log Level Options: `Trace`, `Debug`, `Info`, `Warn`, `Error`, `Fatal`, `Off`. ### Critical Exception Logging -If ServiceControl experiences a critical exception when running as a Windows Service, the exception information will be logged to the Windows EventLog. If ServiceControl is running interactively, the error is shown on the console and not logged. Typically ServiceControl is only run interactively to conduct database maintenance. See [Compacting the ServiceControl RavenDB database](db-compaction.md). +If ServiceControl experiences a critical exception when running as a Windows Service, the exception information will be logged to the Windows EventLog. If ServiceControl is running interactively, the error is shown on the console and not logged. Typically ServiceControl is only run interactively to conduct database maintenance. See [Compacting the ServiceControl RavenDB database](db-compaction.md). \ No newline at end of file diff --git a/servicecontrol/monitoring-instances/installation/index.md b/servicecontrol/monitoring-instances/installation/index.md index 7748616c511..8791bc854f7 100644 --- a/servicecontrol/monitoring-instances/installation/index.md +++ b/servicecontrol/monitoring-instances/installation/index.md @@ -1,8 +1,6 @@ --- title: Installing ServiceControl Monitoring Instances reviewed: 2019-05-03 -tags: - - Installation --- The ServiceControl installation file consists of an MSI bootstrapper EXE and an embedded MSI. This installation can be executed standalone or via the [Platform Installer](/platform/installer/). The installation package includes a utility to manage the installation, upgrade, and removal of ServiceControl services, including monitoring instances. This utility is launched as the final step in the installation process and is also available via the Windows Start Menu. diff --git a/servicecontrol/monitoring-instances/installation/installation-powershell.md b/servicecontrol/monitoring-instances/installation/installation-powershell.md index 82732901eb3..46215c0575c 100644 --- a/servicecontrol/monitoring-instances/installation/installation-powershell.md +++ b/servicecontrol/monitoring-instances/installation/installation-powershell.md @@ -1,9 +1,6 @@ --- title: Managing Monitoring instances via PowerShell reviewed: 2019-05-08 -tags: - - Installation - - PowerShell --- NOTE: For general information about ServiceControl PowerShell, including troubleshooting and licensing guidance, see [Managing ServiceControl via PowerShell](/servicecontrol/powershell.md). @@ -66,4 +63,4 @@ To upgrade and instance to the latest version of the binaries run. Invoke-MonitoringInstanceUpgrade -Name ``` -The upgrade will stop the service if it is running. Additional parameters for `Invoke-MonitoringInstanceUpgrade` may be required. The configuration file of the existing version is examined prior to determine if all the required settings are present. If a configuration setting is missing then the cmdlet will throw an error indicating the required additional parameter. +The upgrade will stop the service if it is running. Additional parameters for `Invoke-MonitoringInstanceUpgrade` may be required. The configuration file of the existing version is examined prior to determine if all the required settings are present. If a configuration setting is missing then the cmdlet will throw an error indicating the required additional parameter. \ No newline at end of file diff --git a/servicecontrol/powershell.md b/servicecontrol/powershell.md index 2874a8b025c..91ee52c36f6 100644 --- a/servicecontrol/powershell.md +++ b/servicecontrol/powershell.md @@ -1,9 +1,6 @@ --- title: Managing ServiceControl via PowerShell reviewed: 2019-05-03 -tags: - - Installation - - PowerShell --- @@ -108,4 +105,4 @@ The following example shows how to add a UrlAcl for a ServiceControl service tha ```ps Add-UrlAcl -Url http://servicecontrol.mycompany.com:33333/api/ -Users Users -``` +``` \ No newline at end of file diff --git a/servicecontrol/securing-servicecontrol.md b/servicecontrol/securing-servicecontrol.md index f53c53f39ea..175c9763960 100644 --- a/servicecontrol/securing-servicecontrol.md +++ b/servicecontrol/securing-servicecontrol.md @@ -2,8 +2,6 @@ title: Securing ServiceControl summary: How security is addressed in ServiceControl and how to limit access to ServiceControl data. reviewed: 2020-03-30 -tags: -- Security related: - servicecontrol/creating-config-file - servicecontrol/configure-ravendb-location @@ -72,4 +70,4 @@ ServiceControl uses an embedded RavenDB database to store its data. This databas Access to the location of the database files enables full access to the database contents, so take great care to ensure the database location is secure from unauthorized access and tampering. -Similarly, when backing up the ServiceControl embedded database, ensure the database backup is located in a secure location. +Similarly, when backing up the ServiceControl embedded database, ensure the database backup is located in a secure location. \ No newline at end of file diff --git a/serviceinsight/application-invocation.md b/serviceinsight/application-invocation.md index 3c6c795db37..d7b78e19662 100644 --- a/serviceinsight/application-invocation.md +++ b/serviceinsight/application-invocation.md @@ -3,7 +3,6 @@ title: ServiceInsight Application Invocation reviewed: 2020-03-16 component: ServiceInsight summary: How the integration between ServicePulse and ServiceInsight works and how to use the parameterized invocation of ServiceInsight. -tags: --- It is possible to load any given message in ServiceInsight from ServicePulse by clicking the "Open in ServiceInsight" link. @@ -37,4 +36,4 @@ A list of the supported parameters and a description of their effects: - Example: `si://localhost:33333/api?EndpointName=VideoStore.Sales&search=SubmitOrder&Auto&AutoRefresh=5` - `SilentStartup` [Boolean]: When set to true, the splash screen will not show when launching the application. -When ServiceInsight is launched using these parameters, notice the effects on the user interface (having the endpoint selected, message selected, etc.). If a passed-in argument is not supported, ServiceInsight will notify when it runs. +When ServiceInsight is launched using these parameters, notice the effects on the user interface (having the endpoint selected, message selected, etc.). If a passed-in argument is not supported, ServiceInsight will notify when it runs. \ No newline at end of file diff --git a/serviceinsight/license.md b/serviceinsight/license.md index f251a06b53e..9d46e6b39a4 100644 --- a/serviceinsight/license.md +++ b/serviceinsight/license.md @@ -3,8 +3,6 @@ title: Install the license in ServiceInsight reviewed: 2020-03-09 summary: Install the Particular Platform license in ServiceInsight. component: ServiceInsight -tags: - - license redirects: - serviceinsight/how-to-install-your-license-file-serviceinsight related: @@ -37,4 +35,4 @@ See the [ServiceControl licensing page](/servicecontrol/license.md) or the [inst Once the license file is loaded, ServiceInsight will display licensing information on its status bar (bottom right hand side) upon launch: -![license verified](images/license-verified.png 'width=500') +![license verified](images/license-verified.png 'width=500') \ No newline at end of file diff --git a/serviceinsight/logging.md b/serviceinsight/logging.md index f959aee4baf..ed38179aae9 100644 --- a/serviceinsight/logging.md +++ b/serviceinsight/logging.md @@ -3,8 +3,6 @@ title: Logging in ServiceInsight reviewed: 2020-02-27 summary: How logging works and how to access the log files component: ServiceInsight -tags: - - Logging redirects: - serviceinsight/how-logging-works --- diff --git a/serviceinsight/no-data-available.md b/serviceinsight/no-data-available.md index bda5bf3f8e2..8dacbc4c953 100644 --- a/serviceinsight/no-data-available.md +++ b/serviceinsight/no-data-available.md @@ -3,8 +3,6 @@ title: Data not available reviewed: 2020-03-16 summary: Why ServiceInsight cannot visualize a conversation component: ServiceInsight -tags: -- Expiration --- When selecting a message in ServiceInsight, the visualization windows may show the message "Data not available". diff --git a/servicepulse/install-servicepulse-in-iis.md b/servicepulse/install-servicepulse-in-iis.md index 2a287b29486..ff2096a2d20 100644 --- a/servicepulse/install-servicepulse-in-iis.md +++ b/servicepulse/install-servicepulse-in-iis.md @@ -3,8 +3,6 @@ title: Install ServicePulse in IIS summary: Describes how to manually install ServicePulse in IIS reviewed: 2019-12-25 component: ServicePulse -tags: -- Security --- @@ -217,4 +215,4 @@ Extension | Mime Type .woff | application/font-woff .woff2 | application/font-woff2 -NOTE: Some of these MIME types will already be set up on newer versions of IIS. Verify that all the listed MIME types are present. +NOTE: Some of these MIME types will already be set up on newer versions of IIS. Verify that all the listed MIME types are present. \ No newline at end of file diff --git a/servicepulse/installation.md b/servicepulse/installation.md index 791d7e8c66d..ad490b0eae9 100644 --- a/servicepulse/installation.md +++ b/servicepulse/installation.md @@ -3,8 +3,6 @@ title: Installing ServicePulse summary: Describes how ServicePulse is installed - and its basic requirements component: ServicePulse reviewed: 2020-02-24 -tags: -- Installation related: - servicepulse/troubleshooting --- @@ -63,4 +61,4 @@ NOTE: ServiceControl consumes messages from the Audit queue and stores it tempor ## ServicePulse license -ServicePulse will check the current licensing status by querying the ServiceControl API, located by default at `http://localhost:33333/api`. If ServicePulse indicates that the license is invalid or has expired, then the [license must be updated in ServiceControl](/servicecontrol/license.md). +ServicePulse will check the current licensing status by querying the ServiceControl API, located by default at `http://localhost:33333/api`. If ServicePulse indicates that the license is invalid or has expired, then the [license must be updated in ServiceControl](/servicecontrol/license.md). \ No newline at end of file diff --git a/transports/azure-service-bus/compatibility.md b/transports/azure-service-bus/compatibility.md index 773cdc0d9cb..584d48e804b 100644 --- a/transports/azure-service-bus/compatibility.md +++ b/transports/azure-service-bus/compatibility.md @@ -2,8 +2,6 @@ title: Backwards Compatibility summary: Describes the requirements for backward compatibility with legacy Azure Service Bus component: ASBS -tags: - - Azure reviewed: 2019-02-07 --- @@ -39,4 +37,4 @@ If the legacy transport [sanitizes](/transports/azure-service-bus/legacy/sanitiz For example, for the `ValidateAndHashIfNeeded` strategy, the sanitization functions must include the strategy logic to preserve the same entity names. -snippet: asb-sanitization-compatibility +snippet: asb-sanitization-compatibility \ No newline at end of file diff --git a/transports/azure-service-bus/configuration.md b/transports/azure-service-bus/configuration.md index b1fe42e336f..58bab352556 100644 --- a/transports/azure-service-bus/configuration.md +++ b/transports/azure-service-bus/configuration.md @@ -2,8 +2,6 @@ title: Configuration summary: Explains the configuration options component: ASBS -tags: - - Azure reviewed: 2020-04-15 --- @@ -39,4 +37,4 @@ These settings control how the transport connects to the broker. * `UseWebSockets()`: Configures the transport to use AMQP over websockets. * `TimeToWaitBeforeTriggeringCircuitBreaker(TimeSpan)`: The time to wait before triggering the circuit breaker after a critical error occurred. Defaults to 2 minutes. * `CustomTokenProvider(ITokenProvider)`: Allows replacement of the default token provider, which uses the shared secret in the connection string for authentication. This opens up additional authentication mechanisms such as [shared access signatures](https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-sas), [SAML, Oauth, SWT, windows authentication](https://docs.microsoft.com/en-us/dotnet/api/microsoft.servicebus.tokenprovider?view=azure-dotnet), [managed identities for Azure resources](https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-managed-service-identity), or even custom implementations. -partial: custom-retry-policy +partial: custom-retry-policy \ No newline at end of file diff --git a/transports/azure-service-bus/index.md b/transports/azure-service-bus/index.md index ae0f69e0fff..0416ee8bd57 100644 --- a/transports/azure-service-bus/index.md +++ b/transports/azure-service-bus/index.md @@ -1,9 +1,6 @@ --- title: Azure Service Bus Transport component: ASBS -tags: - - Azure - - Transport related: - samples/azure-service-bus-netstandard/send-reply - samples/azure-service-bus-netstandard/native-integration @@ -34,4 +31,4 @@ To use Azure Service Bus as the underlying transport: snippet: azure-service-bus-for-dotnet-standard -NOTE: The Azure Service Bus transport requires a connection string to connect to a namespace. +NOTE: The Azure Service Bus transport requires a connection string to connect to a namespace. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/addressing-logic.md b/transports/azure-service-bus/legacy/addressing-logic.md index f5268dfedf6..6d3a66cab31 100644 --- a/transports/azure-service-bus/legacy/addressing-logic.md +++ b/transports/azure-service-bus/legacy/addressing-logic.md @@ -2,8 +2,6 @@ title: Addressing Logic summary: How to map logical endpoint names to physical Azure Service Bus addresses component: ASB -tags: - - Azure reviewed: 2020-02-18 redirects: - nservicebus/azure-service-bus/addressing-logic @@ -15,4 +13,4 @@ include: legacy-asb-warning One of the responsibilities of the Azure Service Bus transport is determining the names and physical location of entities in the underlying physical infrastructure. This is achieved by turning logical endpoint names into physical addresses of the Azure Service Bus entities, which is called *Physical Addressing Logic*. -partial: body +partial: body \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/batching.md b/transports/azure-service-bus/legacy/batching.md index f9175871f24..555e1ff1f18 100644 --- a/transports/azure-service-bus/legacy/batching.md +++ b/transports/azure-service-bus/legacy/batching.md @@ -2,9 +2,6 @@ title: Batching summary: Batching with Azure Service Bus and how it works component: ASB -tags: -- Azure -- Transport reviewed: 2019-02-13 redirects: - nservicebus/azure-service-bus/batching @@ -81,4 +78,4 @@ The default value for `MessageSizePaddingPercentage` is 5%. The custom percentag | 10K | 15,057 | 17,440 | 16% | | 100K | 137,937 | 146,464 | 7% | | 170K | 233,509 | 246,815 | 6% | -| 180K | 247,161 | 261,149 | 6% | +| 180K | 247,161 | 261,149 | 6% | \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/brokered-message-creation.md b/transports/azure-service-bus/legacy/brokered-message-creation.md index 8899a8e7d7d..9d663fb05c9 100644 --- a/transports/azure-service-bus/legacy/brokered-message-creation.md +++ b/transports/azure-service-bus/legacy/brokered-message-creation.md @@ -4,8 +4,6 @@ summary: Details on brokered message creation with Azure Service Bus component: ASB versions: '[6,)' reviewed: 2019-03-04 -tags: - - Azure related: - nservicebus/messaging/third-party-integration - nservicebus/messaging/headers @@ -56,4 +54,4 @@ If the message content is in an unsupported or proprietary format, then the appl ### Message type detection -The native message must allow NServiceBus to [detect the message type either via the headers or the message payload](/nservicebus/messaging/message-type-detection.md). +The native message must allow NServiceBus to [detect the message type either via the headers or the message payload](/nservicebus/messaging/message-type-detection.md). \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/configuration/azureservicebusqueueconfig.md b/transports/azure-service-bus/legacy/configuration/azureservicebusqueueconfig.md index 8cfb0cb39eb..e74927bbb86 100644 --- a/transports/azure-service-bus/legacy/configuration/azureservicebusqueueconfig.md +++ b/transports/azure-service-bus/legacy/configuration/azureservicebusqueueconfig.md @@ -3,8 +3,6 @@ title: Queue Configuration Section summary: Configuring Azure Service Bus as transport component: ASB versions: '[5,7)' -tags: -- Azure reviewed: 2019-02-19 redirects: - transports/azure-service-bus/configuration/azureservicebusqueueconfig @@ -42,4 +40,4 @@ NOTE: Most of these values are applied when a queue or topic is created and cann NOTE: AzureServiceBusQueueConfig is only available in Versions 6 and below. `QueueName` and `QueuePerInstance` are obsoleted since version 6. Instead, specify endpoint name and scale out option. -Defaults are just starting values. These values should be always measured and tested against the specific solution and adjusted accordingly. +Defaults are just starting values. These values should be always measured and tested against the specific solution and adjusted accordingly. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/configuration/full.md b/transports/azure-service-bus/legacy/configuration/full.md index 2c023154726..c483abf07b6 100644 --- a/transports/azure-service-bus/legacy/configuration/full.md +++ b/transports/azure-service-bus/legacy/configuration/full.md @@ -3,8 +3,6 @@ title: Full Configuration API summary: List of all Azure Service Bus Transport configuration settings component: ASB versions: '[7,)' -tags: -- Azure redirects: - nservicebus/azure-service-bus/configuration/configuration - nservicebus/azure-service-bus/configuration/full @@ -219,4 +217,4 @@ The settings that determine how entities are composed inside a single namespace: * `FlatComposition`: The entity is in the root of the namespace. Default strategy. * `HierarchyComposition`: The entity is in a namespace hierarchy, at the location generated by the path generator. This composition strategy is idempotent. -Note: When implementing a custom composition strategy, idempotency needs to be taken into consideration to ensure an entity path is not altered when strategy is invoked more than once. +Note: When implementing a custom composition strategy, idempotency needs to be taken into consideration to ensure an entity path is not altered when strategy is invoked more than once. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/configuration/index.md b/transports/azure-service-bus/legacy/configuration/index.md index 6515b44a4db..590d6a8b23d 100644 --- a/transports/azure-service-bus/legacy/configuration/index.md +++ b/transports/azure-service-bus/legacy/configuration/index.md @@ -2,8 +2,6 @@ title: Configuration component: ASB versions: '[7,)' -tags: -- Azure reviewed: 2019-02-19 redirects: - nservicebus/azure-service-bus/configuration @@ -53,4 +51,4 @@ There have historically been regular changes to the physical addressing logic, f ## AzureServiceBusQueueConfig -In versions 6 and below, configuration values are provided using the `AzureServiceBusQueueConfig` configuration section, refer to the [AzureServiceBusQueueConfig configuration page](/transports/azure-service-bus/legacy/configuration/azureservicebusqueueconfig.md) for more details. +In versions 6 and below, configuration values are provided using the `AzureServiceBusQueueConfig` configuration section, refer to the [AzureServiceBusQueueConfig configuration page](/transports/azure-service-bus/legacy/configuration/azureservicebusqueueconfig.md) for more details. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/dlq-forwarding.md b/transports/azure-service-bus/legacy/dlq-forwarding.md index 8c0075ce431..22a729a9e4c 100644 --- a/transports/azure-service-bus/legacy/dlq-forwarding.md +++ b/transports/azure-service-bus/legacy/dlq-forwarding.md @@ -3,9 +3,6 @@ title: Dead Letter Queue Forwarding component: ASB versions: '[7,)' reviewed: 2020-04-19 -tags: -- Azure -- Error Handling redirects: - nservicebus/azure-service-bus/dlq-forwarding - transports/azure-service-bus/dlq-forwarding @@ -30,4 +27,4 @@ When dead letter forwarding is enabled, it will be enabled for all dead letter q snippet: asb-configure-dead-letter-queue-forwarding -NOTE: The centralized dead-letter queue is not created when the EnableInstaller call is invoked and therefore should be created up-front. +NOTE: The centralized dead-letter queue is not created when the EnableInstaller call is invoked and therefore should be created up-front. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/error-handling.md b/transports/azure-service-bus/legacy/error-handling.md index 0f237dccac1..4dd0518dd39 100644 --- a/transports/azure-service-bus/legacy/error-handling.md +++ b/transports/azure-service-bus/legacy/error-handling.md @@ -3,9 +3,6 @@ title: Error Handling summary: Describes the native error-handling capabilities of Azure Service Bus reviewed: 2019-02-19 component: ASB -tags: -- Azure -- Error Handling redirects: - nservicebus/azure-service-bus/error-handling - transports/azure-service-bus/error-handling @@ -63,4 +60,4 @@ Next to the client-side error handling concerns described above, the broker itse Broker will respond to any of these conditions by moving the message to a dead letter queue, which is a sub-queue below a messaging entity. Each regular queue or subscription has a dead letter queue. -From a management perspective, it is not ideal for an operations staff to monitor a multitude of entities for dead lettered or discarded messages in multiple locations. One solution could be to set up [dead letter queue forwarding](dlq-forwarding.md) to a centralized error or dead letter queue. +From a management perspective, it is not ideal for an operations staff to monitor a multitude of entities for dead lettered or discarded messages in multiple locations. One solution could be to set up [dead letter queue forwarding](dlq-forwarding.md) to a centralized error or dead letter queue. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/index.md b/transports/azure-service-bus/legacy/index.md index 5478a7f1017..84ab87ef91e 100644 --- a/transports/azure-service-bus/legacy/index.md +++ b/transports/azure-service-bus/legacy/index.md @@ -1,8 +1,6 @@ --- title: Azure Service Bus Transport (Legacy) component: ASB -tags: - - Azure redirects: - nservicebus/using-azure-servicebus-as-transport-in-nservicebus - nservicebus/azure/azure-servicebus-transport @@ -60,4 +58,4 @@ partial: code-connection ### Via App.Config -snippet: AzureServiceBusConnectionStringFromAppConfig +snippet: AzureServiceBusConnectionStringFromAppConfig \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/message-lock-renewal.md b/transports/azure-service-bus/legacy/message-lock-renewal.md index 7a6d798054a..6c022139f9d 100644 --- a/transports/azure-service-bus/legacy/message-lock-renewal.md +++ b/transports/azure-service-bus/legacy/message-lock-renewal.md @@ -3,9 +3,6 @@ title: Message lock renewal summary: Extending message lock for long-running operations component: ASB versions: '[7,)' -tags: -- Azure -- Transport reviewed: 2019-03-22 related: - samples/azure/azure-service-bus-long-running @@ -38,4 +35,4 @@ The configuration of message lock renewal is done on the `MessageReceivers` exte snippet: asb-auto-lock-renewal -For example, setting lock renewal time to 10 minutes and `LockDuration` set to 1 minute will ensure that message will remain locked for up to 10 minutes, but no longer. If message processing exceeds 10 minutes, the message will become available to other consumers. +For example, setting lock renewal time to 10 minutes and `LockDuration` set to 1 minute will ensure that message will remain locked for up to 10 minutes, but no longer. If message processing exceeds 10 minutes, the message will become available to other consumers. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/migration.md b/transports/azure-service-bus/legacy/migration.md index 80ec99738f0..63a58b84fa7 100644 --- a/transports/azure-service-bus/legacy/migration.md +++ b/transports/azure-service-bus/legacy/migration.md @@ -3,9 +3,6 @@ title: Migrating from the endpoint-oriented topology summary: Migrating a system using the Azure Service Bus transport from the endpoint-oriented topology to the forwarding topology component: ASB versions: '[9.1,)' -tags: -- Azure -- Transport reviewed: 2020-04-30 related: - transports/azure-service-bus/legacy/topologies @@ -114,4 +111,4 @@ A: No. Commands work the same way in both topologies and are not affected by mig When migrating from the legacy Azure Service Bus transport, not all configuration settings will be found with the new Azure Service Bus transport. Certain configuration options will not be found in the new transport as it has sensible and optimal settings configured by the transports and should not be altered. -Particular Services Platform support for new transport was added in Service Control version 3 and later. +Particular Services Platform support for new transport was added in Service Control version 3 and later. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/multiple-namespaces-support.md b/transports/azure-service-bus/legacy/multiple-namespaces-support.md index e36244a604d..8b1ee760ace 100644 --- a/transports/azure-service-bus/legacy/multiple-namespaces-support.md +++ b/transports/azure-service-bus/legacy/multiple-namespaces-support.md @@ -4,9 +4,6 @@ summary: Configuring Azure Service Bus transport to support different partitioni reviewed: 2019-10-06 component: ASB versions: '[7,)' -tags: -- Azure -- Transport related: - samples/azure/custom-partitioning-asb redirects: @@ -90,4 +87,4 @@ snippet: default_namespace_alias or use `NamespacePartitioning().AddNamespace()` with a different alias instead of the `ConnectionString()` method in the source endpoint. -Also, ensure that the same alias and connection string are registered with the replying endpoint using the `NamespaceRouting().AddNamespace()` method. +Also, ensure that the same alias and connection string are registered with the replying endpoint using the `NamespaceRouting().AddNamespace()` method. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/namespace-hierarchy.md b/transports/azure-service-bus/legacy/namespace-hierarchy.md index 10051e921b2..277945fec37 100644 --- a/transports/azure-service-bus/legacy/namespace-hierarchy.md +++ b/transports/azure-service-bus/legacy/namespace-hierarchy.md @@ -3,9 +3,6 @@ title: Namespace hierarchy support summary: Configuring Azure Service Bus transport to support namespace hierarchies. component: ASB versions: "[7,)" -tags: -- Azure -- Transport reviewed: 2019-05-12 redirects: - nservicebus/azure-service-bus/namespace-hierarchy @@ -52,4 +49,4 @@ snippet: asb-custom-composition-strategy The implementation of the `ICompositionStrategy` needs to be registered: -snippet: asb-custom-composition-config +snippet: asb-custom-composition-config \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/naming-conventions.md b/transports/azure-service-bus/legacy/naming-conventions.md index cce5e10b969..2dc7663aeb1 100644 --- a/transports/azure-service-bus/legacy/naming-conventions.md +++ b/transports/azure-service-bus/legacy/naming-conventions.md @@ -3,8 +3,6 @@ title: Naming Conventions summary: Naming Conventions for Azure Service Bus, Versions 6 and below. component: ASB versions: '[6,7)' -tags: - - Azure reviewed: 2019-02-13 redirects: - nservicebus/azure-service-bus/naming-conventions @@ -30,4 +28,4 @@ Entities creation: snippet: ASB-NamingConventions-entity-creation-conventions -WARNING: This is an advanced topic and requires full understanding of the topology. +WARNING: This is an advanced topic and requires full understanding of the topology. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/native-integration.md b/transports/azure-service-bus/legacy/native-integration.md index 94e0e5cc6a1..e743bca126a 100644 --- a/transports/azure-service-bus/legacy/native-integration.md +++ b/transports/azure-service-bus/legacy/native-integration.md @@ -3,8 +3,6 @@ title: Native Integration with Azure Service Bus summary: How to integrate NServiceBus endpoints with non-NServiceBus endpoints on Azure Service Bus. component: ASB reviewed: 2019-02-15 -tags: -- Azure related: - nservicebus/operations redirects: @@ -32,4 +30,4 @@ The following points need to be taken into account when integrating ### See it in action -[The following sample](/samples/azure/native-integration-asb/) shows how to use the native integration capabilities of the Azure Service Bus transport between an NServiceBus endpoint and a regular .NET application. +[The following sample](/samples/azure/native-integration-asb/) shows how to use the native integration capabilities of the Azure Service Bus transport between an NServiceBus endpoint and a regular .NET application. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/oversized-sends.md b/transports/azure-service-bus/legacy/oversized-sends.md index 6cf9c5d6905..722b9967a69 100644 --- a/transports/azure-service-bus/legacy/oversized-sends.md +++ b/transports/azure-service-bus/legacy/oversized-sends.md @@ -3,9 +3,6 @@ title: Oversized Sends reviewed: 2019-02-27 component: ASB versions: '[7,)' -tags: -- Azure -- Error Handling redirects: - nservicebus/azure-service-bus/oversized-sends - transports/azure-service-bus/oversized-sends @@ -27,4 +24,4 @@ snippet: asb-configure-oversized-messages-handler and registered using the `OversizedBrokeredMessageHandler` API. -snippet: asb-configure-oversized-messages-handler-config +snippet: asb-configure-oversized-messages-handler-config \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/performance-tuning.md b/transports/azure-service-bus/legacy/performance-tuning.md index 7fa5a1841a3..308894effcf 100644 --- a/transports/azure-service-bus/legacy/performance-tuning.md +++ b/transports/azure-service-bus/legacy/performance-tuning.md @@ -1,8 +1,6 @@ --- title: Performance Tuning component: ASB -tags: - - Azure reviewed: 2019-04-18 related: - nservicebus/operations @@ -14,4 +12,3 @@ redirects: include: legacy-asb-warning partial: body - diff --git a/transports/azure-service-bus/legacy/publisher-names-configuration.md b/transports/azure-service-bus/legacy/publisher-names-configuration.md index 75e329ae88e..9173c8ab970 100644 --- a/transports/azure-service-bus/legacy/publisher-names-configuration.md +++ b/transports/azure-service-bus/legacy/publisher-names-configuration.md @@ -3,9 +3,6 @@ title: Publishers name configuration summary: Configuration mapping between publisher names and event types for the endpoint-oriented topology component: ASB versions: "[7,)" -tags: -- Azure -- Transport reviewed: 2018-12-11 redirects: - nservicebus/azure-service-bus/publisher-names-configuration @@ -27,4 +24,4 @@ snippet: publisher_names_mapping_by_assembly In the latter case, the transport analyzes all types in the assembly to identify which are events, using the `IEvent` interface or the configured `DefiningEventsAs()` [message convention](/nservicebus/messaging/conventions.md). Then for each event type, the transport registers a mapping between the type and the publisher name. -In the snippets the **publisherName** is the name of the endpoint that will publish messages. +In the snippets the **publisherName** is the name of the endpoint that will publish messages. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/retries.md b/transports/azure-service-bus/legacy/retries.md index c23f102a2a1..a92592b6db1 100644 --- a/transports/azure-service-bus/legacy/retries.md +++ b/transports/azure-service-bus/legacy/retries.md @@ -3,9 +3,6 @@ title: Retry behavior summary: Describes the relationship between the NServiceBus retry behavior and the Azure Service Bus native retry behavior component: ASB versions: '[7,)' -tags: -- Azure -- Transport reviewed: 2019-02-19 redirects: - nservicebus/azure-service-bus/retries @@ -56,4 +53,4 @@ snippet: forward-deadletter-conditional-queue ## Delayed Retries -Delayed Retries are not affected by `MaxDeliveryCount` since the message is deferred for a longer period, it will result in a resend operation inside the Azure Service Bus transport. That, in turn, will reset the delivery counter inside the brokered message. +Delayed Retries are not affected by `MaxDeliveryCount` since the message is deferred for a longer period, it will result in a resend operation inside the Azure Service Bus transport. That, in turn, will reset the delivery counter inside the brokered message. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/sanitization.md b/transports/azure-service-bus/legacy/sanitization.md index ca3a773ef2b..19715b89757 100644 --- a/transports/azure-service-bus/legacy/sanitization.md +++ b/transports/azure-service-bus/legacy/sanitization.md @@ -1,9 +1,6 @@ --- title: Sanitization component: ASB -tags: -- Azure -- Transport related: - samples/azure/custom-sanitization-asb reviewed: 2019-10-01 @@ -64,4 +61,4 @@ When implementing custom sanitization, consider factors such as readability and * Define endpoint name as short and meaningful. * Avoid message definitions in deep-nested namespaces. - * Keep event names descriptive and short. + * Keep event names descriptive and short. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/securing-connection-strings.md b/transports/azure-service-bus/legacy/securing-connection-strings.md index 10f41455941..a3ac22e040d 100644 --- a/transports/azure-service-bus/legacy/securing-connection-strings.md +++ b/transports/azure-service-bus/legacy/securing-connection-strings.md @@ -2,10 +2,6 @@ title: Securing Connection Strings To Namespaces component: ASB versions: '[7,)' -tags: -- Azure -- Transport -- Security reviewed: 2019-02-19 related: - nservicebus/operations @@ -64,4 +60,4 @@ Without enabling the `UseNamespaceAliasInsteadOfConnectionStrings()` behavior, t By calling `UseNamespaceAliasNameInsteadOfConnectionString()` the transport will change its behavior. Instead of embedding connection strings in headers, namespace aliases will be used instead. -Any incoming message can have headers in either format, the transport will automatically convert connection strings on the wire to namespace alias for internal use. +Any incoming message can have headers in either format, the transport will automatically convert connection strings on the wire to namespace alias for internal use. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/token-provider.md b/transports/azure-service-bus/legacy/token-provider.md index b847b4555bf..b93d908be13 100644 --- a/transports/azure-service-bus/legacy/token-provider.md +++ b/transports/azure-service-bus/legacy/token-provider.md @@ -3,10 +3,6 @@ title: Custom Token Provider summary: Configuring Azure Service Bus transport to use a custom token provider for authentication component: ASB versions: '[7,)' -tags: - - Azure - - Transport - - Security reviewed: 2019-02-19 redirects: - nservicebus/azure-service-bus/token-provider @@ -42,4 +38,4 @@ Snippet: asb-register-token-provider-namespace-manager-settings If the `MessagingFactory` requires different tokens for authentication then the `NamespaceManager`, its `TokenProvider` can be replaced using the `MessagingFactories().MessagingFactorySettingsFactory()` configuration API that allows to override the `MessagingFactorySettings`. -Snippet: asb-register-token-provider-messaging-factory-settings +Snippet: asb-register-token-provider-messaging-factory-settings \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/topologies.md b/transports/azure-service-bus/legacy/topologies.md index 859968b09e3..76011752bed 100644 --- a/transports/azure-service-bus/legacy/topologies.md +++ b/transports/azure-service-bus/legacy/topologies.md @@ -3,8 +3,6 @@ title: Topologies reviewed: 2018-12-11 component: ASB versions: '[7,)' -tags: - - Azure related: - nservicebus/operations - samples/azure/azure-service-bus @@ -82,4 +80,4 @@ The `ForwardingTopology` supports up to 2,000 endpoints with up to 2,000 events ## Versions 6 and below -The Azure Service Bus transport has always supported a single default topology out-of-the-box. It is equivalent to the `EndpointOrientedTopology` introduced in Version 7. +The Azure Service Bus transport has always supported a single default topology out-of-the-box. It is equivalent to the `EndpointOrientedTopology` introduced in Version 7. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/transaction-support.md b/transports/azure-service-bus/legacy/transaction-support.md index d5d06736501..ef465bf57d5 100644 --- a/transports/azure-service-bus/legacy/transaction-support.md +++ b/transports/azure-service-bus/legacy/transaction-support.md @@ -3,9 +3,6 @@ title: Transaction Support reviewed: 2019-02-06 component: ASB versions: '[7,)' -tags: - - Azure - - Transactions redirects: - nservicebus/azure-service-bus/transaction-support - transports/azure-service-bus/transaction-support @@ -52,4 +49,4 @@ NOTE: For a full explanation of the transactional behavior in Azure, refer to [U Using the supported transaction levels, the transport only provides an **`at-least-once`** delivery model. Azure Service Bus provides a [duplicate detection feature](https://docs.microsoft.com/en-us/azure/service-bus-messaging/duplicate-detection) which will ensure the message is received exactly once if enabled. However, Duplicate Detection comes at the expense of throughput and is time constrained. -WARN: The Azure Service Bus duplicate detection feature is not compatible with the [second level retries](/nservicebus/recoverability/#delayed-retries). Enabling duplicate detection and second level retries together can cause message loss. +WARN: The Azure Service Bus duplicate detection feature is not compatible with the [second level retries](/nservicebus/recoverability/#delayed-retries). Enabling duplicate detection and second level retries together can cause message loss. \ No newline at end of file diff --git a/transports/azure-service-bus/legacy/understanding-transactions-and-delivery-guarantees.md b/transports/azure-service-bus/legacy/understanding-transactions-and-delivery-guarantees.md index edb346b8250..d9856de304e 100644 --- a/transports/azure-service-bus/legacy/understanding-transactions-and-delivery-guarantees.md +++ b/transports/azure-service-bus/legacy/understanding-transactions-and-delivery-guarantees.md @@ -2,9 +2,6 @@ title: Understanding internal transactions and delivery guarantees reviewed: 2019-04-18 component: ASB -tags: - - Azure - - Transactions redirects: - nservicebus/azure-service-bus/understanding-transactions-and-delivery-guarantees - transports/azure-service-bus/understanding-transactions-and-delivery-guarantees @@ -12,4 +9,4 @@ redirects: include: legacy-asb-warning -partial: desc +partial: desc \ No newline at end of file diff --git a/transports/azure-service-bus/native-integration.md b/transports/azure-service-bus/native-integration.md index b6944c46ba0..27f56fb38d3 100644 --- a/transports/azure-service-bus/native-integration.md +++ b/transports/azure-service-bus/native-integration.md @@ -2,9 +2,6 @@ title: Native Integration with Azure Service Bus summary: How to integrate NServiceBus endpoints with non-NServiceBus endpoints on Azure Service Bus. component: ASBS -tags: - - Azure - - Transport related: - samples/azure-service-bus-netstandard/native-integration reviewed: 2020-04-29 @@ -28,4 +25,4 @@ The following points must be taken into account when integrating ### See it in action -[This sample](/samples/azure/native-integration-asb/) shows how to use the native integration capabilities of the Azure Service Bus transport between an NServiceBus endpoint and a regular .NET application. +[This sample](/samples/azure/native-integration-asb/) shows how to use the native integration capabilities of the Azure Service Bus transport between an NServiceBus endpoint and a regular .NET application. \ No newline at end of file diff --git a/transports/azure-service-bus/native-message-access.md b/transports/azure-service-bus/native-message-access.md index 3968e44c4ff..25a869fbe33 100644 --- a/transports/azure-service-bus/native-message-access.md +++ b/transports/azure-service-bus/native-message-access.md @@ -2,8 +2,6 @@ title: Native message access component: ASBS versions: '[1.4.0,]' -tags: - - Azure reviewed: 2019-12-02 --- @@ -15,4 +13,4 @@ It can sometimes be useful to access the native Service Bus message from behavio snippet: access-native-message -The behavior above uses the native message's `LockedUntilUtc` system property to determine wherever the message has lost its lock as a result of aggressive prefetching and slow processing. The message with the lost lock will not go through recoverability, skipping attempted processing that otherwise would be guaranteed to fail due to the message's lost lock. +The behavior above uses the native message's `LockedUntilUtc` system property to determine wherever the message has lost its lock as a result of aggressive prefetching and slow processing. The message with the lost lock will not go through recoverability, skipping attempted processing that otherwise would be guaranteed to fail due to the message's lost lock. \ No newline at end of file diff --git a/transports/azure-service-bus/operational-scripting.md b/transports/azure-service-bus/operational-scripting.md index c8b1c073ad5..93bfb9dcf51 100644 --- a/transports/azure-service-bus/operational-scripting.md +++ b/transports/azure-service-bus/operational-scripting.md @@ -2,8 +2,6 @@ title: Operational Scripting summary: Explains how to create queues and topics with the Azure Service Bus transport using scripting component: ASBS -tags: - - Azure reviewed: 2019-02-07 --- @@ -124,4 +122,4 @@ asb-transport queue delete #### options `-c` | `--connection-string` : Overrides the environment variable 'AzureServiceBus_ConnectionString' - + \ No newline at end of file diff --git a/transports/azure-service-bus/topology.md b/transports/azure-service-bus/topology.md index d7b395b29a8..ad83e92080f 100644 --- a/transports/azure-service-bus/topology.md +++ b/transports/azure-service-bus/topology.md @@ -1,9 +1,6 @@ --- title: Topology component: ASBS -tags: - - Azure - - Transport reviewed: 2020-04-29 --- diff --git a/transports/azure-service-bus/transaction-support.md b/transports/azure-service-bus/transaction-support.md index a329cebd160..e5cbc065513 100644 --- a/transports/azure-service-bus/transaction-support.md +++ b/transports/azure-service-bus/transaction-support.md @@ -3,9 +3,6 @@ title: Transaction Support reviewed: 2019-02-07 component: ASBS versions: '[1,)' -tags: - - Azure - - Transactions --- @@ -37,4 +34,4 @@ When transactions are disabled in NServiceBus, the transport uses the Azure Serv The message is deleted from the queue directly after the receive operation completes and before it is processed, so it's not possible to retry that message in case of processing failures. As transient exceptions occur regularly when integrating with online services, disabling retries when in unreliable mode is not recommended. This mode should only be used in very specific situations, when message loss is acceptable. -NOTE: For a full explanation of the transactional behavior in Azure, refer to [Understanding internal transactions and delivery guarantees](/transports/azure-service-bus/legacy/understanding-transactions-and-delivery-guarantees.md). +NOTE: For a full explanation of the transactional behavior in Azure, refer to [Understanding internal transactions and delivery guarantees](/transports/azure-service-bus/legacy/understanding-transactions-and-delivery-guarantees.md). \ No newline at end of file diff --git a/transports/azure-storage-queues/configuration.md b/transports/azure-storage-queues/configuration.md index 8b50899655d..862e8a6c34d 100644 --- a/transports/azure-storage-queues/configuration.md +++ b/transports/azure-storage-queues/configuration.md @@ -1,8 +1,6 @@ --- title: Azure Storage Queues Transport Configuration component: ASQ -tags: -- Azure related: - persistence/azure-storage/performance-tuning reviewed: 2019-06-04 @@ -80,4 +78,4 @@ partial: sanitization Azure Storage Queues Transport changes the default serializer to JSON. The serializer can be changed using the [serialization API](/nservicebus/serialization). -partial: envelope +partial: envelope \ No newline at end of file diff --git a/transports/azure-storage-queues/delayed-delivery.md b/transports/azure-storage-queues/delayed-delivery.md index 99751a16dae..ec47c6c0333 100644 --- a/transports/azure-storage-queues/delayed-delivery.md +++ b/transports/azure-storage-queues/delayed-delivery.md @@ -2,8 +2,6 @@ title: Azure Storage Queues Delayed Delivery component: ASQ versions: '[7,)' -tags: -- Azure related: - persistence - persistence/azure-storage @@ -43,4 +41,4 @@ Once an endpoint has no more delayed messages in its persistence database, there snippet: delayed-delivery-disable-timeoutmanager -At this point, the `{endpoint}-timeouts` and `{endpoint}-timeoutsdispatcher` queues can be deleted from the storage account. In addition, the endpoint no longer requires timeout persistence, so those storage tables can be removed from the persistence database as well. +At this point, the `{endpoint}-timeouts` and `{endpoint}-timeoutsdispatcher` queues can be deleted from the storage account. In addition, the endpoint no longer requires timeout persistence, so those storage tables can be removed from the persistence database as well. \ No newline at end of file diff --git a/transports/azure-storage-queues/index.md b/transports/azure-storage-queues/index.md index 63031acfdd5..c47ccb5f9bd 100644 --- a/transports/azure-storage-queues/index.md +++ b/transports/azure-storage-queues/index.md @@ -2,8 +2,6 @@ title: Azure Storage Queues Transport summary: Using Azure Storage Queues as a message transport component: ASQ -tags: - - Azure related: - samples/azure/storage-queues reviewed: 2020-03-25 @@ -39,4 +37,4 @@ snippet: AzureStorageQueueTransportWithAzure Then set up appropriate [connection strings](/transports/azure-storage-queues/configuration.md#connection-strings) and consider using aliases to make them [more secure](/transports/azure-storage-queues/configuration.md#connection-strings-using-aliases-for-connection-strings-to-storage-accounts). -Note: When using Azure Storage Queues transport, a serializer must be configured explicitly [by the `UseSerializer` API](/nservicebus/serialization/). +Note: When using Azure Storage Queues transport, a serializer must be configured explicitly [by the `UseSerializer` API](/nservicebus/serialization/). \ No newline at end of file diff --git a/transports/azure-storage-queues/multi-storageaccount-support.md b/transports/azure-storage-queues/multi-storageaccount-support.md index 60a3b51da22..d1c83835f0f 100644 --- a/transports/azure-storage-queues/multi-storageaccount-support.md +++ b/transports/azure-storage-queues/multi-storageaccount-support.md @@ -3,9 +3,6 @@ title: Multiple storage accounts summary: Use multiple Azure storage accounts for scale out component: ASQ reviewed: 2019-08-06 -tags: -- Azure -- Performance redirects: - nservicebus/using-multiple-azure-storage-accounts-for-scaleout - nservicebus/azure/using-multiple-azure-storage-accounts-for-scaleout @@ -67,4 +64,4 @@ partial: routing-send-options-full-connectionstring partial: aliases -partial: registered-endpoint +partial: registered-endpoint \ No newline at end of file diff --git a/transports/azure-storage-queues/performance-tuning.md b/transports/azure-storage-queues/performance-tuning.md index a18dc2aa5b5..13bea8d045b 100644 --- a/transports/azure-storage-queues/performance-tuning.md +++ b/transports/azure-storage-queues/performance-tuning.md @@ -5,10 +5,6 @@ component: ASQ isLearningPath: true versions: '[7,]' reviewed: 2020-03-25 -tags: -- Azure -- Transport -- Performance related: - nservicebus/operations redirects: @@ -23,4 +19,4 @@ Microsoft's [Azure Storage Performance Checklist](https://docs.microsoft.com/en- Multiple parallel read operations are used to improve message throughput. The amount of parallel read operations is the square root of the configured [message processing concurrency](/nservicebus/operations/tuning.md). This value can be increased or decreased as needed by using the `DegreeOfReceiveParallelism` configuration parameter. See [Azure Storage Queues Transport Configuration](/transports/azure-storage-queues/configuration.md) on how to use this parameter. -Note: Changing the value of `DegreeOfReceiveParallelism` will influence the total number of storage operations against Azure Storage Services and can result in higher costs. +Note: Changing the value of `DegreeOfReceiveParallelism` will influence the total number of storage operations against Azure Storage Services and can result in higher costs. \ No newline at end of file diff --git a/transports/azure-storage-queues/sanitization.md b/transports/azure-storage-queues/sanitization.md index bad573af14d..fbf647c4509 100644 --- a/transports/azure-storage-queues/sanitization.md +++ b/transports/azure-storage-queues/sanitization.md @@ -2,8 +2,6 @@ title: Azure Storage Queues Sanitization component: ASQ versions: '[8,)' -tags: -- Azure related: - transports/azure-storage-queues/configuration - samples/azure/storage-queues @@ -52,4 +50,4 @@ When implementing custom sanitization, consider factors such as readability and * Hashed queue names could lead to difficult names to use during production troubleshooting or debugging. * Sanitized queue names stay in the system and cannot be replaced until no longer used. -Possible way to avoid sanitization is to define endpoint name short and meaningful. +Possible way to avoid sanitization is to define endpoint name short and meaningful. \ No newline at end of file diff --git a/transports/azure-storage-queues/transaction-support.md b/transports/azure-storage-queues/transaction-support.md index f2ee49651c1..dec7ef2fac6 100644 --- a/transports/azure-storage-queues/transaction-support.md +++ b/transports/azure-storage-queues/transaction-support.md @@ -3,9 +3,6 @@ title: Transaction Support summary: A description of the transaction modes supported by the Azure Storage Queues transport component: ASQ versions: '[6,]' -tags: -- Azure -- Transactions reviewed: 2020-03-23 redirects: - nservicebus/azure-storage-queues/transaction-support @@ -24,4 +21,4 @@ Azure Storage Queues use a `Peek-Lock` model to overcome the lack of transaction ## Unreliable (transactions disabled) -The message is deleted from the queue directly after the receive operation completes and before it is processed. +The message is deleted from the queue directly after the receive operation completes and before it is processed. \ No newline at end of file diff --git a/transports/msmq/connection-strings.md b/transports/msmq/connection-strings.md index c0881c519f1..8e503fe1ae2 100644 --- a/transports/msmq/connection-strings.md +++ b/transports/msmq/connection-strings.md @@ -3,10 +3,8 @@ title: MSMQ Transport connection strings summary: Detailed connection string information for MSMQ. component: MsmqTransport reviewed: 2020-04-07 -tags: - - Transport redirects: - nservicebus/msmq/connection-strings --- -partial: content +partial: content \ No newline at end of file diff --git a/transports/msmq/dead-letter-queues.md b/transports/msmq/dead-letter-queues.md index 918223146ae..572ec872d8a 100644 --- a/transports/msmq/dead-letter-queues.md +++ b/transports/msmq/dead-letter-queues.md @@ -3,8 +3,6 @@ title: MSMQ Dead Letter Queues summary: Controlling MSMQ Dead Letter Queue behavior reviewed: 2019-09-16 component: MsmqTransport -tags: - - Transport redirects: - nservicebus/msmq/dead-letter-queues related: @@ -42,4 +40,4 @@ DIRECT=OS:{MACHINE-NAME}\SYSTEM$;DEADXACT #### Performance counters -The [**MSMQ Queue**](https://technet.microsoft.com/en-us/library/cc771098.aspx#Anchor_2) performance object contains counters that can be used to monitor the number of messages in various queues. Value of the **Messages in Queue** counter of the **Computer Queues** instance tracks the number of messages in the DLQ on a given machine. +The [**MSMQ Queue**](https://technet.microsoft.com/en-us/library/cc771098.aspx#Anchor_2) performance object contains counters that can be used to monitor the number of messages in various queues. Value of the **Messages in Queue** counter of the **Computer Queues** instance tracks the number of messages in the DLQ on a given machine. \ No newline at end of file diff --git a/transports/msmq/distributor/configuration.md b/transports/msmq/distributor/configuration.md index 62e15dde48e..99b00f7c1b5 100644 --- a/transports/msmq/distributor/configuration.md +++ b/transports/msmq/distributor/configuration.md @@ -3,8 +3,6 @@ title: Configuring Distributor and Workers summary: Describes how to configure the distributor and its workers. component: distributor reviewed: 2018-10-24 -tags: - - Scalability redirects: - nservicebus/msmq/distributor/configuration --- @@ -111,4 +109,4 @@ The NServiceBus default values for these settings can be overridden, as shown in Similar to standard NServiceBus routing, it is not desirable to have high priority messages to get stuck behind lower priority messages, so just as it is possible to have separate NServiceBus processes for different message types, it is also possible to set up different distributor process instances (with separate queues) for various message types. -In this case, name the queues after the message type. For example: `SubmitPurchaseOrder.StrategicCustomers.Sales` becomes the name of the distributor data queue and the input queues of each of the workers. +In this case, name the queues after the message type. For example: `SubmitPurchaseOrder.StrategicCustomers.Sales` becomes the name of the distributor data queue and the input queues of each of the workers. \ No newline at end of file diff --git a/transports/msmq/distributor/disconnect-workers.md b/transports/msmq/distributor/disconnect-workers.md index 35fb67dfdbb..ec6a5f4a9ab 100644 --- a/transports/msmq/distributor/disconnect-workers.md +++ b/transports/msmq/distributor/disconnect-workers.md @@ -2,8 +2,6 @@ title: Disconnect Workers summary: How a worker can be disconnected from its distributor using PowerShell cmdlets reviewed: 2019-04-02 -tags: - - Scalability redirects: - nservicebus/disconnect-workers-from-running-distributor - nservicebus/scalability-and-ha/disconnect-workers @@ -32,4 +30,4 @@ If the Worker is configured using the [NServiceBus.Distributor.MSMQ NuGet](https 1. A disconnect message is sent by the PowerShell cmdlet to the Distributor control queue. 1. When the Distributor processes it, the Worker with the address specified in the message is set with SessionID `disconnected`. - 1. Ready messages sent back by the Worker to the Distributor never match the session, so they are skipped and that way the Worker won't receive any more messages from the Distributor. + 1. Ready messages sent back by the Worker to the Distributor never match the session, so they are skipped and that way the Worker won't receive any more messages from the Distributor. \ No newline at end of file diff --git a/transports/msmq/distributor/error-handling.md b/transports/msmq/distributor/error-handling.md index d1b6ecaab67..aa6ab69795a 100644 --- a/transports/msmq/distributor/error-handling.md +++ b/transports/msmq/distributor/error-handling.md @@ -3,10 +3,6 @@ title: Distributor error handling summary: Error handling with and configuration with the distributor component: Distributor reviewed: 2019-04-15 -tags: - - Error Handling - - Exceptions - - Retry redirects: - nservicebus/errors/distributor-errorhandling - nservicebus/scalability-and-ha/error-handling @@ -44,4 +40,4 @@ Due to the behavioral differences between major versions it is advised to have t It is assumed that *NumberOfRetries* and *TimeIncrease* are the same on the distributor and the workers. -NOTE: If settings are managed in XML configuration all changes in the distributor configuration need to be replicated to all nodes. +NOTE: If settings are managed in XML configuration all changes in the distributor configuration need to be replicated to all nodes. \ No newline at end of file diff --git a/transports/msmq/distributor/index.md b/transports/msmq/distributor/index.md index b308db212fe..b0ae72e421f 100644 --- a/transports/msmq/distributor/index.md +++ b/transports/msmq/distributor/index.md @@ -2,8 +2,6 @@ title: Scaling Out With the Distributor summary: The distributor maintains all the characteristics of NServiceBus but is designed never to overwhelm any of the worker nodes. reviewed: 2019-04-02 -tags: - - Scalability redirects: - nservicebus/load-balancing-with-the-distributor - nservicebus/scalability-and-ha/distributor @@ -160,4 +158,4 @@ Pros and cons: - The routing configuration is really complex, it is not suitable to store routes in application configuration files. - Can still suffer from throughput limitations. In that case [sender side distribution](../sender-side-distribution.md) might be an alternative. -Note: This setup is especially appropriate for virtualized environments and in the cloud when using the IaaS model. +Note: This setup is especially appropriate for virtualized environments and in the cloud when using the IaaS model. \ No newline at end of file diff --git a/transports/msmq/distributor/troubleshooting.md b/transports/msmq/distributor/troubleshooting.md index 88a37e5d984..4a582ddf002 100644 --- a/transports/msmq/distributor/troubleshooting.md +++ b/transports/msmq/distributor/troubleshooting.md @@ -3,8 +3,6 @@ title: MSMQ Distributor Troubleshooting summary: Describes how to solve common issues with the distributor. component: distributor reviewed: 2019-11-05 -tags: -- Scalability related: - transports/msmq/troubleshooting --- @@ -111,4 +109,4 @@ Enabled by Default: No Status: Enabled Dependencies: None Startup Tasks: None -``` +``` \ No newline at end of file diff --git a/transports/msmq/full-qualified-domain-name.md b/transports/msmq/full-qualified-domain-name.md index 9f18de2277d..4760e1e9e06 100644 --- a/transports/msmq/full-qualified-domain-name.md +++ b/transports/msmq/full-qualified-domain-name.md @@ -4,8 +4,6 @@ summary: How to use NServiceBus in environments requiring Fully Qualified Domain component: MsmqTransport versions: '[4,)' reviewed: 2018-10-29 -tags: -- MSMQ redirects: - nservicebus/msmq/full-qualified-domain-name --- diff --git a/transports/msmq/index.md b/transports/msmq/index.md index 5f221b54ffc..47dfc265a04 100644 --- a/transports/msmq/index.md +++ b/transports/msmq/index.md @@ -11,8 +11,6 @@ reviewed: 2020-01-30 redirects: - nservicebus/msmq-information - nservicebus/msmq -tags: - - Transport --- WARNING: As Microsoft is not making MSMQ available for .NET Core, building new systems using MSMQ is not recommended. @@ -160,4 +158,4 @@ See also [Message Queuing Security Overview](https://docs.microsoft.com/en-us/pr To support guaranteed [once delivery of messages,](/nservicebus/operations/transactions-message-processing.md) NServiceBus makes use of the Distributed Transaction Coordinator (DTC) to synchronize transactions between MSMQ and the database. For this to work, the DTC must be started and configured correctly. -In NServiceBus versions 5 and above, there is a _non-DTC_ mode of operation available. In this mode NServiceBus uses a concept of _Outbox_, a message store backed by the same database as the user code, to temporarily store messages that need to be sent as a result of processing an incoming message. To read more about this subject see [Outbox](/nservicebus/outbox/). +In NServiceBus versions 5 and above, there is a _non-DTC_ mode of operation available. In this mode NServiceBus uses a concept of _Outbox_, a message store backed by the same database as the user code, to temporarily store messages that need to be sent as a result of processing an incoming message. To read more about this subject see [Outbox](/nservicebus/outbox/). \ No newline at end of file diff --git a/transports/msmq/routing-extensibility.md b/transports/msmq/routing-extensibility.md index 7629e3ae729..14d3b7271d4 100644 --- a/transports/msmq/routing-extensibility.md +++ b/transports/msmq/routing-extensibility.md @@ -3,11 +3,9 @@ title: Routing system extensibility points for MSMQ summary: Extending MSMQ's physical routing reviewed: 2020-05-26 component: MsmqTransport -tags: - - routing related: - nservicebus/messaging/routing - transports/msmq/routing --- -partial: content +partial: content \ No newline at end of file diff --git a/transports/msmq/routing.md b/transports/msmq/routing.md index fdb3aa54b03..1198fbdf1cc 100644 --- a/transports/msmq/routing.md +++ b/transports/msmq/routing.md @@ -3,9 +3,6 @@ title: Physical routing with MSMQ summary: Configuring physical routing with MSMQ transport component: MsmqTransport reviewed: 2020-05-20 -tags: - - Routing - - MSMQ related: - nservicebus/messaging/routing - transports/msmq/routing-extensibility diff --git a/transports/msmq/scaling-out.md b/transports/msmq/scaling-out.md index 2468bf5e6ea..d94833c78ac 100644 --- a/transports/msmq/scaling-out.md +++ b/transports/msmq/scaling-out.md @@ -3,10 +3,6 @@ title: Scaling out MSMQ endpoints summary: How to scale out when using the MSMQ transport reviewed: 2018-09-28 component: MsmqTransport -tags: -- scalability -- Routing -- MSMQ related: - nservicebus/messaging/routing redirects: @@ -21,4 +17,4 @@ partial: overview Version 4 of MSMQ, made available with Vista and Server 2008, can perform [remote transactional receive](https://msdn.microsoft.com/en-us/library/ms700128.aspx). This means that processes on other machines can transactionally pull work from a queue on a different machine. If the machine processing the message crashes, the message rolls back to the queue and other machines could then process it. -One problem with 'remote transactional receive' is that it gets proportionally slower as more worker nodes are added. This is due to the overhead of managing more transactions, as well as the longer period of time that these transactions are open. In short, the scale-out benefits of MSMQ version 4 by itself are quite limited. +One problem with 'remote transactional receive' is that it gets proportionally slower as more worker nodes are added. This is due to the overhead of managing more transactions, as well as the longer period of time that these transactions are open. In short, the scale-out benefits of MSMQ version 4 by itself are quite limited. \ No newline at end of file diff --git a/transports/msmq/sender-side-distribution.md b/transports/msmq/sender-side-distribution.md index 3a8401c88db..6d871981a1e 100644 --- a/transports/msmq/sender-side-distribution.md +++ b/transports/msmq/sender-side-distribution.md @@ -4,10 +4,6 @@ summary: How to scale out with sender-side distribution when using the MSMQ tran component: MsmqTransport reviewed: 2018-12-09 versions: '[6,)' -tags: - - scalability - - Routing - - MSMQ redirects: - nservicebus/messaging/file-based-routing related: @@ -87,4 +83,4 @@ For the reasons outlined above, when scaling down (removing a "target" endpoint 1. Allow time (30 seconds by default) for all endpoints to reread the instance mapping file, and ensure no new messages are arriving in the target instance's queue. 1. Allow the target endpoint instance to complete processing all messages in its queue. 1. Disable the target endpoint instance. - 1. Check the input queue of the decommissioned instance for leftover messages and move them to other instances if necessary. + 1. Check the input queue of the decommissioned instance for leftover messages and move them to other instances if necessary. \ No newline at end of file diff --git a/transports/msmq/subscription-authorisation.md b/transports/msmq/subscription-authorisation.md index 7b699e7d686..922ab08d945 100644 --- a/transports/msmq/subscription-authorisation.md +++ b/transports/msmq/subscription-authorisation.md @@ -3,8 +3,6 @@ title: MSMQ Subscription Authorization summary: Managing authorization of subscribers in the MSMQ Transport component: MsmqTransport reviewed: 2018-09-21 -tags: -- Security redirects: related: - samples/pubsub @@ -14,4 +12,4 @@ redirects: Subscription authorization allows the programmatic control over what subscribers can subscribe or unsubscribe to. -snippet: SubscriptionAuthorizer +snippet: SubscriptionAuthorizer \ No newline at end of file diff --git a/transports/msmq/transportconfig.md b/transports/msmq/transportconfig.md index 62953116274..598739a0194 100644 --- a/transports/msmq/transportconfig.md +++ b/transports/msmq/transportconfig.md @@ -3,10 +3,6 @@ title: MSMQ Transport Configuration summary: Explains the mechanics of MSMQ transport, its configuration options, and other configuration settings that were coupled to this transport reviewed: 2020-04-14 component: MsmqTransport -tags: - - Transport - - MSMQ - - Transactions related: - transports/msmq/connection-strings redirects: @@ -53,4 +49,4 @@ partial: native-transactions ### Unreliable (transactions disabled) -In this mode, when a message is received, it is immediately removed from the input queue. If processing fails, the message is lost because the operation cannot be rolled back. Any other operation that is performed when processing the message is executed without a transaction and cannot be rolled back. This can lead to undesired side effects when message processing fails part way through. +In this mode, when a message is received, it is immediately removed from the input queue. If processing fails, the message is lost because the operation cannot be rolled back. Any other operation that is performed when processing the message is executed without a transaction and cannot be rolled back. This can lead to undesired side effects when message processing fails part way through. \ No newline at end of file diff --git a/transports/msmq/troubleshooting.md b/transports/msmq/troubleshooting.md index 176a10462a3..ea05206fb57 100644 --- a/transports/msmq/troubleshooting.md +++ b/transports/msmq/troubleshooting.md @@ -4,9 +4,6 @@ summary: Resolutions for common problems with the MSMQ transport. reviewed: 2019-10-18 component: MsmqTransport isLearningPath: true -tags: -- Transport -- MSMQ redirects: - nservicebus/messagequeueexception-insufficient-resources-to-perform-operation - nservicebus/msmq/messagequeueexception-insufficient-resources-to-perform-operation @@ -119,4 +116,4 @@ For more information, see [MSMQ dead-letter queues](dead-letter-queues.md). - [MSMQ Errors and Events](https://technet.microsoft.com/en-us/library/dd337466.aspx) - [Message Queueing Resources](https://technet.microsoft.com/en-us/library/dd337480.aspx) - [Message Queueing System Resources](https://technet.microsoft.com/en-us/library/dd337537.aspx) - - [Troubleshooting MSDTC issues with the DTCPing tool](https://blogs.msdn.microsoft.com/distributedservices/2008/11/12/troubleshooting-msdtc-issues-with-the-dtcping-tool/) + - [Troubleshooting MSDTC issues with the DTCPing tool](https://blogs.msdn.microsoft.com/distributedservices/2008/11/12/troubleshooting-msdtc-issues-with-the-dtcping-tool/) \ No newline at end of file diff --git a/transports/msmq/uninstalling-msmq.md b/transports/msmq/uninstalling-msmq.md index cd87cd52bdf..889e0876921 100644 --- a/transports/msmq/uninstalling-msmq.md +++ b/transports/msmq/uninstalling-msmq.md @@ -2,10 +2,6 @@ title: Uninstalling the MSMQ Service summary: How to remove the Microsoft Messaging Queue (MSMQ) service reviewed: 2020-01-24 -tags: - - Transport - - MSMQ - - Installation redirects: - nservicebus/msmq/uninstalling-msmq --- @@ -119,4 +115,4 @@ Get-WindowsOptionalFeature -Online | } ``` -The script is suppressing restarts to stop a prompt being shown for each feature as it is removed. Once the script has completed the system should be restarted to finalize the changes. +The script is suppressing restarts to stop a prompt being shown for each feature as it is removed. Once the script has completed the system should be restarted to finalize the changes. \ No newline at end of file diff --git a/transports/rabbitmq/index.md b/transports/rabbitmq/index.md index a442adcec0d..8c596b91b20 100644 --- a/transports/rabbitmq/index.md +++ b/transports/rabbitmq/index.md @@ -9,8 +9,6 @@ related: redirects: - nservicebus/rabbitmq/configuration-api - nservicebus/rabbitmq -tags: - - Transport --- Provides support for sending messages over [RabbitMQ](https://www.rabbitmq.com/) using the [RabbitMQ .NET Client](https://www.nuget.org/packages/RabbitMQ.Client/). @@ -58,4 +56,4 @@ partial: topology * Doesn't handle [network partitions](https://www.rabbitmq.com/partitions.html) well; partitioning across a WAN requires dedicated features. * Requires careful consideration for duplicate messages, e.g. using the [outbox](/nservicebus/outbox/) feature or making all endpoints idempotent. * Many organizations don't have the same level of expertise with RabbitMQ as with other technologies, such as SQL Server, so it may require additional training. - * May require covering additional costs of [commercial RabbitMQ license and support](https://www.rabbitmq.com/services.html). + * May require covering additional costs of [commercial RabbitMQ license and support](https://www.rabbitmq.com/services.html). \ No newline at end of file diff --git a/transports/rabbitmq/transactions-and-delivery-guarantees.md b/transports/rabbitmq/transactions-and-delivery-guarantees.md index 094dc943d2d..77c63d6e7a7 100644 --- a/transports/rabbitmq/transactions-and-delivery-guarantees.md +++ b/transports/rabbitmq/transactions-and-delivery-guarantees.md @@ -4,8 +4,6 @@ summary: A description of the transport transaction modes supported by RabbitMQ reviewed: 2020-01-24 versions: '[4,]' component: Rabbit -tags: - - Transactions redirects: - nservicebus/rabbitmq/transactions-and-delivery-guarantees --- @@ -27,4 +25,4 @@ WARNING: If the connection to the broker is lost for any reason before a message Similar to `ReceiveOnly` mode messages are consumed in manual acknowledgment mode, but regardless of whether a message is successfully processed or not, it is acknowledged via the AMQP [basic.ack](https://www.rabbitmq.com/amqp-0-9-1-quickref.html#basic.ack) method after the processing attempt. This means that a message will be attempted once, and moved to the error queue if it fails. -WARNING: Since manual acknowledgment mode is being used, if the connection to the broker is lost for any reason before a message can be acknowledged, the message will automatically be re-queued by the broker. If this occurs, the message will be retried by the endpoint, despite the transaction mode setting. +WARNING: Since manual acknowledgment mode is being used, if the connection to the broker is lost for any reason before a message can be acknowledged, the message will automatically be re-queued by the broker. If this occurs, the message will be retried by the endpoint, despite the transaction mode setting. \ No newline at end of file diff --git a/transports/sql/addressing.md b/transports/sql/addressing.md index 3f6527196ab..0d2f4e6c714 100644 --- a/transports/sql/addressing.md +++ b/transports/sql/addressing.md @@ -3,8 +3,6 @@ title: Addressing summary: How SQL Server transport addresses are translated to queue names reviewed: 2019-01-11 component: SqlTransport -tags: -- Transport redirects: - nservicebus/sqlserver/addressing - transports/sqlserver/addressing diff --git a/transports/sql/deployment-options.md b/transports/sql/deployment-options.md index 26a6f925fa3..b17e152aa72 100644 --- a/transports/sql/deployment-options.md +++ b/transports/sql/deployment-options.md @@ -2,8 +2,6 @@ title: Deployment options reviewed: 2019-10-24 component: SqlTransport -tags: -- Transport related: - nservicebus/operations redirects: @@ -14,4 +12,4 @@ redirects: The SQL Server Transport offers several deployment options for the queue tables. -partial: content +partial: content \ No newline at end of file diff --git a/transports/sql/design.md b/transports/sql/design.md index c0c5db9101a..95a0ef9838c 100644 --- a/transports/sql/design.md +++ b/transports/sql/design.md @@ -3,10 +3,6 @@ title: SQL Transport Design summary: The design and implementation details of SQL Server Transport reviewed: 2019-10-08 component: SqlTransport -tags: -- Transactions -- Transport -- Concurrency redirects: - nservicebus/sqlserver/design - transports/sqlserver/design @@ -82,4 +78,4 @@ Messages are sent by executing an `insert` command against the queue table. Messages are received by executing a `delete` command against the queue table. The `delete` is limited to a row with the lowest `RowVersion` not locked by other concurrent `delete`. This ensures that multiple threads within an endpoint instance and multiple instances of the same scaled-out endpoint can operate at full speed without conflicts. -partial: concurrency +partial: concurrency \ No newline at end of file diff --git a/transports/sql/service-control.md b/transports/sql/service-control.md index c11c446bee1..4c61c8c48ee 100644 --- a/transports/sql/service-control.md +++ b/transports/sql/service-control.md @@ -3,8 +3,6 @@ title: ServiceControl and Multi-Instance Mode summary: ServiceControl and SQL Server transport multi-instance mode configuration guidance reviewed: 2019-12-10 hidden: true -tags: - - Transport redirects: - nservicebus/sqlserver/service-control - transports/sqlserver/service-control @@ -41,4 +39,4 @@ snippet: sc-multi-instance-connection-strings Each endpoint can use queues stored in any SQL Server instance except for shared `error` and `audit` queues, which need to be stored in an instance used by ServiceControl. This cannot be expressed in the configuration file but can be implemented using the [pull mode API](/transports/sql/connection-settings.md?version=SqlTransportLegacySystemClient_3#multiple-connection-strings): -snippet: sc-multi-instance-endpoint-connection-strings +snippet: sc-multi-instance-endpoint-connection-strings \ No newline at end of file diff --git a/transports/sql/transactions.md b/transports/sql/transactions.md index 3613378a5c1..f6780df3755 100644 --- a/transports/sql/transactions.md +++ b/transports/sql/transactions.md @@ -3,9 +3,6 @@ title: Transaction support summary: The design and implementation details of SQL Server transport transaction support reviewed: 2019-12-19 component: SqlTransport -tags: -- Transactions -- Transport redirects: - nservicebus/sqlserver/transactions - transports/sqlserver/transactions @@ -52,4 +49,4 @@ partial: native In this mode, when a message is received it is immediately removed from the input queue. If processing fails the message is lost because the operation cannot be rolled back. Any other operation that is performed when processing the message is executed without a transaction and cannot be rolled back. This can lead to undesired side effects when message processing fails part way through. -partial: custom-connection-and-transaction +partial: custom-connection-and-transaction \ No newline at end of file diff --git a/transports/sqs/configuration-options.md b/transports/sqs/configuration-options.md index 50d773ffc28..d2c08c21728 100644 --- a/transports/sqs/configuration-options.md +++ b/transports/sqs/configuration-options.md @@ -3,8 +3,6 @@ title: Configuration Options summary: Configuration options for the SQS transport. component: SQS reviewed: 2019-10-17 -tags: -- AWS redirects: - nservicebus/sqs/configuration-options --- diff --git a/transports/sqs/index.md b/transports/sqs/index.md index 2d97122de34..0a5895536a8 100644 --- a/transports/sqs/index.md +++ b/transports/sqs/index.md @@ -5,8 +5,6 @@ component: SQS reviewed: 2020-04-27 related: - samples/sqs/simple -tags: -- AWS redirects: - nservicebus/sqs/index --- diff --git a/transports/sqs/performance-tuning.md b/transports/sqs/performance-tuning.md index 8b9d5d386da..460e4432a45 100644 --- a/transports/sqs/performance-tuning.md +++ b/transports/sqs/performance-tuning.md @@ -3,9 +3,6 @@ title: Performance Tuning summary: Guidance to tweak the performance of the SQS transport component: SQS reviewed: 2020-05-25 -tags: -- AWS -- Performance --- NOTE: It is difficult to give performance tuning guidelines that will be generally applicable. Results may vary greatly depending on many factors such as bandwidth, latency, client version, and much more. As always with performance tuning: Measure, don't assume. @@ -73,4 +70,4 @@ ServicePointManager.UseNagleAlgorithm = false; ## Known Limitations -- The transport uses a single client for all operations on SQS. The throughput of a single endpoint is thus limited to the number of connections a single client can handle +- The transport uses a single client for all operations on SQS. The throughput of a single endpoint is thus limited to the number of connections a single client can handle \ No newline at end of file diff --git a/transports/sqs/topology.md b/transports/sqs/topology.md index 45fb5156b35..2ce5ea1086b 100644 --- a/transports/sqs/topology.md +++ b/transports/sqs/topology.md @@ -3,8 +3,6 @@ title: Topology summary: Identify the physical components used by the Amazon SQSL transport and how they interact. component: SQS reviewed: 2020-04-27 -tags: -- AWS --- The topology used by the transport is composed of several AWS components. diff --git a/transports/sqs/transaction-support.md b/transports/sqs/transaction-support.md index 4726bd56a84..4f5ce80c53e 100644 --- a/transports/sqs/transaction-support.md +++ b/transports/sqs/transaction-support.md @@ -3,9 +3,6 @@ title: Transaction Support summary: Explore the transaction modes the transport supports. component: SQS reviewed: 2019-05-27 -tags: -- AWS -- Transactions --- The Amazon SQS transport supports the following [Transport Transaction Modes](/transports/transactions.md): @@ -17,4 +14,4 @@ The transport functions in the same way regardless of whether it is running in R As the transport receives messages from the SQS queue for processing, SQS hides the received messages from other consumers for a configurable [visibility timeout](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html) period. After the endpoint has successfully processed a message, the transport deletes the message from the SQS queue. Messages that are not processed successfully will be either sent back to the input queue as part of deferred retries or moved to the error queue, depending on how the [recoverability](/nservicebus/recoverability) of the endpoint is configured. -WARNING: The transport uses [Amazon SQS Standard Queues](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/standard-queues.html) which guarantee [at-least-once delivery](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/standard-queues.html#standard-queues-at-least-once-delivery) of messages. Furthermore if the connection to Amazon SQS is lost for any reason before a message can be deleted, even if the message was successfully processed, the message will become available to other consumers when the [visibility timeout](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html) expires. Therefore it is possible for endpoints to successfully process the same messages more than once. Consider using the [Outbox](/nservicebus/outbox) feature to deduplicate incoming messages. +WARNING: The transport uses [Amazon SQS Standard Queues](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/standard-queues.html) which guarantee [at-least-once delivery](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/standard-queues.html#standard-queues-at-least-once-delivery) of messages. Furthermore if the connection to Amazon SQS is lost for any reason before a message can be deleted, even if the message was successfully processed, the message will become available to other consumers when the [visibility timeout](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html) expires. Therefore it is possible for endpoints to successfully process the same messages more than once. Consider using the [Outbox](/nservicebus/outbox) feature to deduplicate incoming messages. \ No newline at end of file diff --git a/transports/sqs/troubleshooting.md b/transports/sqs/troubleshooting.md index faba58f4f62..6b1470923e5 100644 --- a/transports/sqs/troubleshooting.md +++ b/transports/sqs/troubleshooting.md @@ -6,8 +6,6 @@ reviewed: 2019-02-22 related: - transports/sqs - samples/sqs/simple -tags: -- AWS --- ## Viewing the message ID on the SQS message @@ -57,4 +55,4 @@ When throttling occurs with no custom error logic implemented, one or more messa ## On endpoint shutdown messages might be only visible after the visibility timeout has expired -After an endpoint is shutdown messages that were in flight but not handled might not be visible in the input queue for up to 30 seconds (default message visibility timeout). Messages will not be lost and will reappear in the input queue once the visibility timeout is expired. This is due to an [issue in the AWS SDK](https://github.com/aws/aws-sdk-net/issues/796#issuecomment-375494537). +After an endpoint is shutdown messages that were in flight but not handled might not be visible in the input queue for up to 30 seconds (default message visibility timeout). Messages will not be lost and will reappear in the input queue once the visibility timeout is expired. This is due to an [issue in the AWS SDK](https://github.com/aws/aws-sdk-net/issues/796#issuecomment-375494537). \ No newline at end of file diff --git a/transports/sqs/why-use-sqs.md b/transports/sqs/why-use-sqs.md index 20e51946c7a..ddde4f5247f 100644 --- a/transports/sqs/why-use-sqs.md +++ b/transports/sqs/why-use-sqs.md @@ -3,8 +3,6 @@ title: Why Use SQS? summary: Explore when it makes sense to use SQS as a transport. component: SQS reviewed: 2019-07-15 -tags: -- AWS redirects: - nservicebus/sqs/why-use-sqs --- @@ -46,4 +44,4 @@ However, this approach doesn't mesh well with [AWS Auto Scaling](https://aws.ama AS can be configured to not terminate any EBS volumes when scaling down. However this leaves an orphaned volume, potentially with messages on it, with nothing processing them. Naturally this is a problem when there are SLAs to meet. -To solve these problems, the guidance from Amazon is to use SQS as the transport. This transport will help get the most out of AWS and the Auto Scaling feature. +To solve these problems, the guidance from Amazon is to use SQS as the transport. This transport will help get the most out of AWS and the Auto Scaling feature. \ No newline at end of file diff --git a/transports/transactions.md b/transports/transactions.md index 8690570e446..6c1ed87a978 100644 --- a/transports/transactions.md +++ b/transports/transactions.md @@ -3,9 +3,6 @@ title: Transport Transactions summary: Supported transaction modes and their consistency guarantees component: Core versions: "[4,)" -tags: - - Transactions - - Transport redirects: - nservicebus/messaging/transactions - nservicebus/transports/transactions @@ -110,4 +107,4 @@ WARNING: This might escalate to a distributed transaction if data in different d partial: partial-updates -partial: scope-options +partial: scope-options \ No newline at end of file diff --git a/transports/types.md b/transports/types.md index 8cda126f490..2907e8752d9 100644 --- a/transports/types.md +++ b/transports/types.md @@ -2,8 +2,6 @@ title: Different transport types summary: The main transport type differences explained component: Core -tags: - - Transport reviewed: 2018-11-27 ---