We plan to release public support for non-Azure Storage backends for Durable Functions. In order for the VS build SDK to fully support this, we need to exclude Durable triggers from the list of triggers requiring `AzureWebJobsStorage`.
Note that we already made the same change for the Functions Core Tools: https://github.com/Azure/azure-functions-core-tools/pull/2409
Moving the v1 & v3 tests to separate folders.
Removing the samples folder and moving the tests to endtoend tests
Moving the pack folder under src
Updating build.cmd with tests
Adding directly.build.props with version info.
Updating the build version for the binaries based on each build
* Copying the missing dlls to the bin folder
* Adding End to End Tests and porting the projects to netcoreapp3.1. Tests cover the following scenarios
- Build and publish for a project targeting Netsdk latest version
- Build and publish for a project with SQl dependency
- Build and publish for a project with a HttpTrigger
* Upgrading the sdk to 3.1.301
* Running end to end tests as a part of ci build
* Auto-increment the assembly version for generator and msbuild dll
Fix assembly loading when dealing with different versions of libraries
than what the SDK has a dependency on. This should resolve numerous
issues with types not loading in the generator itself. In addition, some
places where you typically would get a rather unhelpfull
`NullReferenceException`, a check for null values have been added,
throwing `InvalidOperationException`s with more helpfull error messages.
Resolves#359
* This functionality is off by default; to enable, set the project
property FunctionsInDependencies to True.
* Compilers can be too smart. To ensure that a referenced project's DLL
is included in the assembly's dependencies, make sure the assembly's
code explicitly references a member or type from the referenced project.
Chris Gillum
Graham Zuber
Naren Soni
soninaren
Brett Samblanet
Vijay Ramakrishnan
Vijay Ramakrishnan
Fabio Cavalcante
Marie Hoeger
Aleksander Heintz
Katy Shimizu