Welcome to the June release of the Azure SDK. We have updated the following libraries:<\/p>\n
These are ready to use in your production applications. You can find details of all released libraries on our releases page<\/a>.<\/p>\n New preview releases:<\/p>\n In addition, we’ve released a new preview of the Azure SDK for Embedded C. See below for details.<\/p>\n We believe these are ready for you to use and experiment with, but not yet ready for production. Between now and the GA release, these libraries may undergo API changes. We’d love your feedback! If you use these libraries and like what you see, or you want to see changes, let us know in GitHub issues.<\/p>\n Use the links below to get started with your language of choice. You will notice that all the preview libraries are tagged with “preview”.<\/p>\n If you want to dive deep into the content, the release notes linked above and the change logs they point to give more details on what has changed.<\/p>\n The Azure Embedded C SDK<\/a> is designed to allow small embedded (IoT) devices to communicate with Azure services. Since we expect the client library code to run on microcontrollers that have slower CPUs and very limited amounts of flash, the Embedded C SDK is architected very differently than the Azure SDKs we offer in other languages.<\/p>\n To properly address the needs of the embedded developer:<\/p>\n At the heart of the SDK is what we refer to as Azure Core<\/em>. This code defines several data types and functions for use by the client libraries such as the Azure IoT client libraries and the Azure Blob Storage client library. Some of the features you will use directly:<\/p>\n By utilizing Azure Core, Azure client libraries will share a common implementation and many features will behave identically across the suite of client libraries. For example, the standard HTTP pipeline unifies the handling of authentication, logging, retry, and telemetry.<\/p>\n The code below demonstrates how to upload ASCII text to an Azure Storage blob using the Azure Embedded C SDK. The sample also shows how to enable logging.<\/p>\n While this example demonstrates how to use For more information on using the Azure Embedded C SDK for IoT, check out the introductory video: Introduction to the new Embedded C SDK for Azure IoT<\/a>.<\/p>\n So far, the community has filed hundreds of issues against these new SDKs with feedback ranging from documentation issues to API surface area change requests to pointing out failure cases. Please keep that coming. We work in the open on GitHub and you can submit issues here:<\/p>\n\n
Getting Started<\/h2>\n
\n
Introducing the Azure SDK for Embedded Devices<\/h2>\n
\n
SDK architecture<\/h3>\n
\n
Example: Uploading a blob to Azure Storage<\/h3>\n
#include <az_context.h>\n#include <az_storage_blobs.h>\n#include <curl\/curl.h> \/\/ libcurl is our HTTP stack\n#include <stdio.h>\n#include <stdlib.h>\n\nstatic void log_func(az_log_classification classification, az_span message)\n{\n (void)classification;\n printf(\"%.*s\\n\", az_span_size(message), az_span_ptr(message));\n}\n\nint main()\n{\n \/\/ Initialize libcurl\n if (curl_global_init(CURL_GLOBAL_ALL) != CURLE_OK)\n {\n printf(\"Couldn't init libcurl\\n\");\n return 1;\n }\n \/\/ Set up libcurl cleaning callback as to be called before ending program\n atexit(curl_global_cleanup);\n\n \/\/ Enable SDK logging:\n az_log_classification const classifications[] = { \n AZ_LOG_HTTP_RESPONSE, AZ_LOG_END_OF_LIST \n };\n az_log_set_classifications(classifications);\n az_log_set_callback(log_func);\n\n \/\/ Allocate & initialize client using Blob URL (with SAS) from environment variable\n az_storage_blobs_blob_client client;\n if (az_storage_blobs_blob_client_init(\n &client, az_span_from_str(getenv(\"AZURE_STORAGE_URL\")), AZ_CREDENTIAL_ANONYMOUS, NULL)\n != AZ_OK)\n {\n printf(\"Failed to initialize blob client\\n\");\n return 1;\n }\n\n \/\/ Allocate a buffer to hold HTTP responses; reused by each HTTP request\n uint8_t response_buffer[1024 * 4] = { 0 };\n\n \/\/ Allocate & initialize an HTTP response structure pasing it the HTTP response buffer\n az_http_response http_response;\n if (az_http_response_init(&http_response, AZ_SPAN_FROM_BUFFER(response_buffer)) != AZ_OK)\n {\n printf(\"Failed to init http response\\n\");\n return 1;\n }\n\n \/\/ Upload bytes to the blob\n az_result blob_upload_result = az_storage_blobs_blob_upload(\n &client, &az_context_app, AZ_SPAN_FROM_STR(\"Some content\"), NULL, &http_response);\n if (az_failed(blob_upload_result))\n {\n printf(\"Failed to upload blob\\n\");\n return 1;\n }\n\n \/\/ Show HTTP response information\n az_http_response_status_line status_line;\n if (az_failed(az_http_response_get_status_line(&http_response, &status_line)))\n {\n printf(\"Failed to get status line\\n\");\n return 1;\n }\n\n printf(\"HTTP Status Code: %d\\n\", status_line.status_code);\n return 0;\n}\n<\/code><\/pre>\nlibcurl<\/code> as an HTTP stack, you can modify the code to use a different HTTP stack. See the GitHub repository<\/a> for more information.<\/p>\nMore information<\/h3>\n
Working with us and giving feedback<\/h2>\n