Search Results for "folder"

...Client libraries are packages that you would use to consume these resources and interact with them. The readme for each package contains code samples and package information. This readme can be found in the corresponding package folder under the folder of the service of your choice in the /SDK folder of this repository. The same readme file can be found on the landing page for the package in npm. The API reference documentation of the latest versions of these packages can be found at our public developer docs. The API reference documentation of older versions can be found in our versioned developer docs.

...These libraries can be easily identified by folder, package, and namespaces names starting with azure-, e.g. azure-key vault.

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...

...For your convenience, each service has a separate set of libraries that you can choose to use instead of one, large Azure package. To get started with a specific library, see the README.md (or README.rst) file located in the library's project folder. Last stable versions of packages that have been provided for usage with Azure and are production-ready. These libraries provide you with similar functionalities to the Preview ones as they allow you to use and consume existing resources and interact with them, for example: upload a blob. They might not implement the guidelines or have the same feature set as the November releases. ...

...It also includes examples on how to develop a Lambda function in JavaScript as well as packaging and running an example Hello World file in JavaScript for your Greengrass core. The environment where Greengrass is running on needs to be able to run NodeJS 12.x applications. Unzip the SDK into your node_modules folder of your function. This should create a aws-greengrass-core-sdk folder which includes the SDK. Your console.log operation will be logged as INFO. A console.error operation will be logged as error. Currently, our NodeJS SDK only allows you to log at info or error level only.

...If you are using RN < 0.30.0 and react-native-fcm < 1.0.16, pass intent into package, edit MainActivity.java. Import libraries, add Capabilities (background running and push notification), upload APNS and etc. Put frameworks under ios/Frameworks folder, and drag those files into your xcode solution. Make sure the file is not just moved into the folder. You need to Right Click the project folder in XCode and Add File to <Project Name>. Select Copy if needed in the Options page while selecting the file.