Found 16 packages
An NLog layout renderer that allows items in the current HTTP context to be added to a log layout. Example: ${http-context-item:X-RequestId} will log the contents of HttpContext.Current.Items["X-Request-Id"]
NLog Extensions. [Features] - HipChat Target. - ASP.NET Request Summary Renderer. - Truncate Renderer. If you find bugs or have requests for improvement, contact me. http://github.com/nabehiro/NLog.Extensions
ASP.NET Core Responsive middleware for routing base upon request client device detection to specific view. Also in the added feature of user preference made this library even more comprehensive must for developers whom to target multiple devices with view rendered and optimized directly from the server side.
To build a SOAP request and more. Target framework: Netstandard2.0
Extension class for Azure StorageException to extract usefull information embedded inside the StorageException object by Azure Storage services on a failed request. Provides StorageException extension methods to extract: - ErrorCode - ETag - ExtendedErrorMessage - FailedOperationIndex (of a failed Batch Operation) - HttpStatusCode - OperationStartTime (UTC) - OperationEndTime (UTC) - RequestDate (UTC) - RequestId - TargetLocation (Primary, Secondary, etc.) - IsOptimisticConcurrencyFailure And extended ToString() method which automatically extracts this information from the exception instance and converts it into a string for logging purposes. Usage: Try { //Make a request to Azure Table Storage (Blob, Table, Queue, ..) } catch (StorageException storageException) { //Gives you the HttpStatusCode embedded inside the StorageException int? httpStatusCode = storageException.GetHttpStatusCode(); // Gives you the index of the failed operation in a azure table batch operation int failedOperationIndex = storageException.GetFailedOperationIndex(); }
To build a SOAP request and more. Target framework: Net462
Requires Sitecore 10.3 Requires .NET Framework 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Feature.Navigation library addresses the three most common forms of Navigation on Sitecore sites: Declared (static) Navigation: (explicitly defined, may differ from the shape of the content tree) - DeclaredNavigationRepository.GetNavigation - Accepts a Navigation Menu item and assembles a full tree-like ViewModel for immediate processing in your View. If you need context highlighting in your navigation, be sure to pass in the Context Item as well. When using NavigationLink objects, there are usually several opportunities to supply the text of a given link. NavigationLink.GetBestLinkText() evaluates all of them and attempts to supply the best fit. The strategy is based on overriding the concept of "name". Here are the rules: - If Use This Display Name is checked on the NavigationLink item, it wins. - If the Link.Text is supplied by the user, it wins. - If the Link.TargetItem exists and inherits from Page Navigation Title, and the field value is not null, it wins. - If the Link.TargetItem exists its DisplayName is used. - Assuming all other things are not true, use the NavigationLink's DisplayName. Note that in this condition if you intended to point to a Sitecore Item, you have a bad link. Branch (Context) Navigation: (implicitly defined. It follows the shape of the Content Tree) - BranchNavigationRepository.GetNavigation - Accepts the request Context Item (should be a Page) and generates a tree of BranchNodes representing the nearest LandingPage, its children, as well as the descendants of any children that are Ancestors of the Context Item. (will also create Children for the Context Item node in the tree). Use this to produce the expanded navigation seen on many sites with deep content. Breadcrumbs: (implicitly defined. It walks up the Content Tree to get the path) - BreadcrumbNavigationRepository.GetNavigation - Accepts the request Context Item and Context SiteInfo. Generates an array of Breadcrumb models you can enumerate on your View. The breadcrumbs will start on your Site's StartItem and end with the supplied Context Item, which will be marked IsContextItem so you can change your rendering behavior. Uses the Item.Axes.GetAncestors() method to generate the list of breadcrumbs. The included package must be installed to use this library. This should happen automatically after you build and deploy your project.
ASP.NET Core Detection service components for identifying details about client device, browser, engine, platform, and crawler. Responsive middleware for routing base upon request client device detection to specific view. Also in the added feature of user preference made this library even more comprehensive must for developers whom to target multiple devices with view rendered and optimized directly from the server side.
3.10.2 - Healthcheck for RabbitMQ fixed; special characters inthe username and password are now supported 3.10.1 - Dotnet 8.0 target framework added, older versions removed 3.9.6 - ReqRespAsync pattern support via ServiceBus restored - RoutingSlip ServiceBus support added 3.9.3 - It is now possible to call AddAsHighAvailableQueue and AddAsDefaultQueue extensions using custom RabbitMQSettings objects. 3.9.2 - Fixes a dependency injection unexpected behaviour when multi reqrespasync used 3.9.0 - MultiTarget framework support (.net3.1 - 5 - 6) rather than being single target with .NetStandard 2.0 which is outdated 3.8.0 - It is now possible to supply custom configuration objects to AddRabbitMqBus and AddServiceBus extensions. - It is now possible to give custom health check tags to AddRabbitMqBus extensions (helps in avoiding duplicates). 3.7.8 - Fixed a critical bug when ReqRespAsync is used in multiple APIs and same virtual hosts - Add multiple responder to your project 3.7.2 -Fixed a bug for quorum ReqRespAsync patterns 3.7.0 - HighAvailable Queues introduced (powered by quorum) 3.6.0 - ReqRespAsync as GetResponse/Respond Pattern introduced - Awaitable saga, routing slip or ReqRespAsync - Some other useful extension methods 3.5.2 - Minor fixes - Request Response Async Pattern response sender can send response from anywhere thanks to bus 3.5.0 - Request-Response Async Pattern introduced 3.4.0 - Masstransit upgraded to latest 7.x.x version - Masstransit HostedService is now using the as-is one comes directly from MassTransit package - RabbitMQ Healthchecks are now more accurate including all the consumers and their healthiness 3.3.0 - RoutingSlip pattern Added (ConsumeRoutingSlipActivity as consumer) 3.1.1 - MultiBus Hosted Service registration fixed 3.1.0 - MultiBus Support Added 3.0.4 -Health Check with IConnection 3.0.3 -Buggy Rabbitmq healthcheck removed temporarily, will be fixed in a later version 3.0.2 -Added Health Check 3.0.1 -Recovered the port settings feature from 2.0.8 3.0.0 -MassTransit 7.1.5 support added 2.1.0 -MassTransit 6.3.1 support added. Use this version, if MassTransit 6.3.1 required in your project. 2.0.8 -Port Issue fixed (RabbitMQ started using the port number in settings.) 2.0.7 -Prefetch Count Added
ASP.NET Core Responsive middleware for routing base upon request clientInfo device detection to specific view Being to target difference clientInfo devices with seperation of concern is crucial, due to you can mininize what is sent to the clientInfo directly from the service to only what is needed and nothing more. This increase performance and lower bandwidth usage.
2.6.3 - Carbon.HttpClient.Auth version update 2.6.2 - Dotnet 8.0 target framework added, older versions removed 2.5.0 - Dotnet 6.0 target framework added 2.4.1 - NetCore 3.1 target framework added 2.4.0 - GRPC Client ReAuth and Resend request when unauthorized 401 from server automatically 2.3.6 - Dependency Injection Nuget 3.1.12 sync 2.3.5 - Added Authorized GRPC Client for Identity Server (Handles token retreival and header injection) 2.2.10 - GRPC Client Extension for Carbon.WebApplication or Carbon.ConsoleApplication
Port of the SendGrid HTTP APIs for use with a .NET Core 3.1 target. We have also made steps to enhance the performance of the library by moving to the System.Text.JSON library for serialization and deserialization which greatly improves request RW performance and greatly reduces memory consumption.
-2.10.1 - Dotnet 8.0 target framework added, older versions removed -2.9.3 - MenuItems field added to SolutionCreationRequest -2.9.2 - IsDynamic solution flag is added - 2.9.0 - MultiTarget framework support (.net3.1 - 5 - 6) rather than being previously single target with .NetStandard 2.0 which is outdated -Works with MassTransit 3.9.0 -2.8.0 - Works with MassTransit 3.7.2 version which supports quorum queues as well as this package supports quorum queues as of this version -2.7.1 - Carbon.Domain.Messages updated from 1.8.0 to 1.9.18 for Solution model Uri prop -2.7.0 - Critical bug fixed for Directory separator char to specific platform (Windows,Linux) -2.6.0 - Critical bug fixed for SolutionRegistration when there is no default MassTransit usage - Some Performance Improvements-2.6.0 - Critical bug fixed for SolutionRegistration when there is no default MassTransit usage - Some Performance Improvements -2.5.0 - Uses latest Masstransit version which is 7.3.x - Uses MultiBus instead of SingleBus while registering solution or subscribing tenant featureset notifications - Compatible with Carbon.MassTransit > 3.4.x - Improved Performance and Health Monitorable - Each SubscriptionToFeatureSetNotification Requires a bus interface derived from IBus -2.1.4 - Consumer added as a scoped -2.1.1 - Enables featureset notification to the subscribers when a tenant is assigned with -2.0.3 Works with CarbonException Handling 1.2.0 -2.0.2 Supports Masstransit 7.1.x and Carbon.MassTransit 3.0.4 -2.0.1 Supports Masstransit 7.1.x and Carbon.MassTransit 3.0.2 -1.0.23 Supports MassTransit 6.2.3 and Carbon.MassTransit 2.0.8
3.3.6 - Carbon.Common version update 3.3.5 - Microsoft.Extensions.Logging package added 3.3.4 - HybridModelBinding updated to 0.17.0 on net8.0 target framework 3.3.3 - Dotnet 8.0 target framework added for minimal api 3.3.2 - Dotnet 8.0 target framework added, older versions removed 3.2.0 - Degraded health check HTTP status code changed as custom 218 (This Is Fine) status code. Because even if system is degraed it should be working normally, so returning 5XX status code is not right for degraded state. 3.1.0 - Carbon.Common updated and Serilog.Enrichers.Sensitive Enricher added for masking sensitive values within logs. 3.0.2 - Cors Policy changes(Location parameter is added to WithExposedHeaders) 3.0.1 - Not a RC anymore - Cors Allow Credentials support added 3.0.0-preview - Dotnet 6 support with minimal and not minimal api added 2.5.1 -NetCore 3.1 target framework added 2.5.0 -Major bug fixed for UI Authorized request 401 error. Startup changed. 2.4.3 - Bearer Interceptor Included as default 2.3.0 - Can inject Interceptor as ctor parameter 2.2.10 - GRPC Web supported 2.2.6 - GRPC Extension for Carbon.WebApplication
Requires Sitecore 10.3 Requires .NET Framework 4.8 Constellation is a collection of utilities for the Sitecore .NET CMS. The Foundation.PageNotFound library provides unique Sitecore-hosted "not found" pages with the correct 404 Http Response for each site in your installation. Installation 1. Add this NuGet package to your Sitecore solution 2. Build and Deploy your solution to a target environment Package Includes: Custom Site Attribute: notFoundPageID This attribute should be set to the ID of the Item to use for presenting 404 Response Status messages to the visitor. Each site requires its own 404 page Item. HttpRequestBegin Pipeline Processor: Page Not Found Resolver Assuming the site is configured with the ID of the "not found page" this processor will resolve the context item to that specific item if the context item is currently null. This processor must run after all Site, Database, Language, and Item resolvers, but before Device and Layout resolvers. The supplied patch:before is a safe bet, but may need to be changed depending on your solution. Please note that this processor will only run for databases and sites as configured, and should intentionally not run for Sitecore system sites. HttpRequestEnd Pipeline Processor: Set404StatusCode Assuming the site is configured with the ID of the "not found page" this processor will detect that the context item is the 404 page and will add the 404 code to the Response. Please note that the customizations in this processor will only run for databases and sites as configured, and should intentionally not run for Sitecore system sites.
Allows a microservice API to be described declaratively as an interface-based contract. Once such a contract is configured for use, SilkRoute can provide a dynamically generated proxy that implements the interface and can be consumed like a regular application service. Although the calling code interacts with an ordinary interface, each method invocation is translated into an HTTP request to the target service, and the received response is mapped back to the return type declared by the contract.