When generating function.json files from attribute scriptFile path is set incorrectly.
Imported
<PackageReference Include="Microsoft.NET.Sdk.Functions" Version="1.0.6" />
In generated function.json below the scriptFile path should be set to "../bin/HttpTriggerCore.dll" but is instead set to "bin/HttpTriggerCore.dll".
{
"generatedBy": "Microsoft.NET.Sdk.Functions.Generator-1.0.6",
"configurationSource": "attributes",
"bindings": [
{
"type": "httpTrigger",
"route": "name/{name}/sname/{sname}",
"methods": [
"get"
],
"authLevel": "anonymous",
"name": "req"
}
],
"disabled": false,
"scriptFile": "bin/HttpTriggerCore.dll",
"entryPoint": "HttpTriggerCore.HttpTrigger.Run"
}
Folder structure

Here is the error when trying to run:
11/18/17 8:23:49 AM] Job host started
[11/18/17 8:23:49 AM] The following 1 functions are in error:
[11/18/17 8:23:49 AM] Echo: Invalid script file name configuration. The 'scriptFile' property is set to a file that does not exist.
I have submitted a pull request here: https://github.com/Azure/azure-functions-vs-build-sdk/pull/143
This is my first time submitting a PR here so please let me know if I have missed an important step :)
Any update on getting this merged, currently running into this issue. Changing all function.json files generated seems onerous.
I see that the fix has been merged - but any update on when it'll be released?
We're adding C# class library support to the Azure Functions extension for VS Code, which is obviously cross platform and would greatly benefit from this fix
@fabiocav @ahmelsayed
1.0.8 will contain this and will be released on nuget tomorrow morning. Thanks again @craig006 and sorry for the delay in the release.
@ahmelsayed Hi, I want to know if 1.0.8 is going to be released any time soon?
@rcastill yes, sorry I was shooting for release on Wednesday, but it got pushed back a bit due to some test machines issues. Friday is the current plan to be nuget.
@ahmelsayed Thanks for the info!
Most helpful comment
I see that the fix has been merged - but any update on when it'll be released?
We're adding C# class library support to the Azure Functions extension for VS Code, which is obviously cross platform and would greatly benefit from this fix
@fabiocav @ahmelsayed