3.0.0-rc1

This is the release candidate for WebJobs 3.0. Major changes in this release:

• packages are strong name signed
• the service bus extension package has been renamed to be consistent with the other extension packages (it was renamed from Microsoft.Azure.WebJobs.ServiceBus to Microsoft.Azure.WebJobs.Extensions.ServiceBus)

3.0.0-beta8

Significant breaking changes in this release.

• Introduction of new extension loading model
• New dependency injection model, based on Microsoft.Extensions.Hosting
• Decoupled storage extensions from SDK
• Decoupled storage core services from SDK

v2.2.0

In this release:

• ServiceBus MessageProcessor fix (#1605)
• warning now emitted if ServicePointManager.DefaultConnectionLimit is set to default value of 2. See here for details
• fixing TraceWriter concurrency issue (#1533)
• Allow JobHostQueuesConfiguration.NewBatchThreshold to be set to 0 (#1568)
• Don't query non-existent queues (#770)
• Fixes to support Storage SDK 9.0
• improvements to ServiceBus connection string error message (#1583)

v2.1.0

See the release notes below for the intervening 4 beta releases since the 2.0 release. Those beta releases will have details on all the updates/features in this release. Since beta4 we've fixed some remaining bugs and stabilized things.

One special note on this release: We've taken the approach of applying ObsoleteAttribute on a set of public APIs that are new in this release, but not yet ready for public consumption. These APIs are under active development as part of Azure Functions and may experience breaking changes in the next release (even the next minor release), so we don't recommend their use unless you're OK with absorbing breaking changes.

3.0.0-beta4

Stability enhancements, bug fixes and dependencies updates.

2.1.0-beta4

Included in this release:

• Dot expression support in binding templates
  • See the binding expressions section on the wiki for more details
• Support for FunctioName attribute
  • You can control the name of the job function by using this attribute on your methods
• Support for binding return values
• Invocation filters
  • Allows custom logic to be executed in the WebJobs invocation pipeline. You can find more information here
• Configurable Event Hubs checkpointing
• Miscellaneous fixes and enhancements

3.0.0-beta2

Resolve #1403

Missing lock.

2.1.0-beta1-10950

• Return value support (#1243)
• Miscellaneous bug fixes and enhancements

2.1.0-beta1-10851

• Dot expressions support for bindings
• Miscellaneous bug fixes, performance improvements and other enhancements

Detailed commit log here

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