Open Source C# Cloud Services Software

The Service Bus Explorer allows users to connect to a Service Bus namespace and administer messaging entities in an easy manner. The tool provides advanced features like import/export functionality or the ability to test topics, queues, subscriptions, relay services, notification hubs, and events hubs. Microsoft Azure Service Bus is a reliable information delivery service. The purpose of this service is to make communication easier. When two or more parties want to exchange information, they need a communication facilitator. Service Bus is a brokered, or third-party communication mechanism. This is similar to postal service in the physical world. Postal services make it very easy to send different kinds of letters and packages with a variety of delivery guarantees, anywhere in the world. The Service Bus Explorer 2.1.0 can be used with the Service Bus for Windows Server 1.1. The Service Bus Explorer 2.1.0 uses a version of the Microsoft.ServiceBus.dll client library.

This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs or our versioned developer docs. New wave of packages that we are announcing as GA and several that are currently releasing in preview. These libraries follow the Azure SDK Design Guidelines for .NET and share a number of core features such as HTTP retries, logging, transport protocols, authentication protocols, etc., so that once you learn how to use these features in one client library, you will know how to use them in other client libraries. You can learn about these shared features at Azure.Core. Last stable versions of packages that are production-ready. These libraries provide similar functionalities to the preview packages, as they allow you to use and consume existing resources and interact with them, for example: upload a storage blob. Stable library directories typically contain 'Microsoft.Azure' in their names.

A unique, highly tailored customer experience (CX) might become a significant advantage to beating any competitor, even with a larger market presence and budget. Choose Virto Commerce's headless, API-driven platform to build such a unique CX. Entrepreneurs ourselves, we constantly develop our .NET Core platform offering the flexibility, scalability, and agility for building new revenue sources like online stores, B2B portals, multi-vendor portals, mobile apps, chatbots or any other touchpoints. Use Virto Commerce B2B eCommerce platform as a transformational force to reimagine how to do business, identify new markets and deploy resources more efficiently for higher ROI. Strive for online business when you win while the client wins as well. Worldwide network of certified implementation partners & solution partners to fit every project. Build a B2B channel with complicated business logic on top of your e-commerce solution without re-platforming or data duplication.

The Amazon GameLift Plugin for Unity contains libraries and native UI that makes it easier to access GameLift resources and integrate GameLift into your Unity game. You can use the GameLift Unity Plugin to access GameLift APIs and deploy AWS CloudFormation templates for common gaming scenarios. Auth Only, this scenario creates a game backend service that performs only player authentication and no game server capability. It creates a Cognito user pool to store player authentication information, as well as an API gateway REST endpoint backed up AWS Lambda handlers to start a game and view game connection information. The Lambda handler always returns a 501 Error (Unimplemented). Single-Region Fleet, this scenario creates a game backend service with a single GameLift fleet. After player authenticates and starts a game (with a POST request to /start_game), a AWS Lambda handler searches for an existing viable game session with an open player slot on the fleet.

This project provides a custom library that extends the Apache TinkerPop Gremlin.NET client to enable AWS IAM Signature Version 4 signing for establishing authenticated connections to Amazon Neptune. For example usage refer to: NeptuneGremlinNETSigV4Example.cs. This example shows how to leverage this library for establishing an authenticated connection to Neptune. The GremlinClient library accepts both a GremlinServer object as well as a webSocketConfiguration object that contains a custom configuration set for establishing the WebSocket connection to Amazon Neptune. The SigV4RequestSigner library fetchs IAM credentials using the FallbackCredentialsFactory API (which works similarly to the Java Default Credential Provider Chain), performs the proper Signature Version 4 signing of an http request, and creates the proper WebSocket configuration based on this signed http request. One can then pass this webSocketConfiguration to the GremlinClient to create the connection to Neptune.

This repository contains PowerShell cmdlets for developers and administrators to develop, deploy, and manage Microsoft Azure applications. This module runs on Windows PowerShell with .NET Framework 4.7.2 or greater, or the latest version of PowerShell 7. The Az module replaces AzureRM. You should not install Az side-by-side with AzureRM. Update-Module installs the new version side-by-side with previous versions. It does not uninstall the previous versions. To connect to Azure, use the Connect-AzAccount cmdlet. A session context persists login information across Azure PowerShell modules and PowerShell instances. To view the context you are using in the current session, which contains the subscription and tenant, use the Get-AzContext cmdlet. To get the subscriptions in a tenant, use the Get-AzSubscription cmdlet. To change the subscription that you are using for your current context, use the Set-AzContext cmdlet.