2.1.0-beta1

Included in this release:

• Application Insights logging support
  • ability to configure an ApplicationInsights logger for all standard logs written by the SDK, as well as logs written by user code via TextWriter/TraceWriter bindings
  • new ILogger binding allowing you to bind directly to the Application Insights logger
  • see wiki here for more info
• improvements for binding extension authors
• added a new Connection property to all Azure Storage, ServiceBus and EventHub binding attributes to facilitate multi-account scenarios
  • e.g. previously you had to apply StorageAccountAttribute/ServiecBusAccountAttribute to specify use of an alternate connection
  • those attribute are still useful for method/class level overrides, but if you only want to specify an override on a single binding, you can now do so via the attribute directly, e.g. [QueueTrigger("myqueue", Connection = "MyStorageSetting")] where "MyStorageSetting" is the name of an app setting that contains the storage connection string to use for the binding
• expanded binding data contracts for ServiceBus, EventHub, BlobTrigger bindings
  • see https://github.com/Azure/azure-webjobs-sdk/wiki/Trigger-Binding-Data for a detailed writeup
• fixed TextWriter concurrency issues (#1042)
• big improvements to error log stack traces for readability (#1051)
• Added ServiceBusAttribute.EntityType property to allow output bindings to disambiguate between queue and topic creation (addresses #1052)
• QueueTrigger stability improvements (#944)
• DocumentDB Query support
  • A new sqlQuery binding property is now supported allowing you to declaratively specify a query with full parameter binding support.
  • e.g. "sqlQuery": "SELECT f.id, f.related FROM f WHERE f.related = {documentId}"
  • See here for more details