New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port runtime to .NET Core #98
Comments
Do we have an availability date for WebJobs SDK in .NET Core? |
Is there a public repo where we can contribute and monitor the netcore port? |
Have opened the following issues to track migration: PRs to follow (starting with WebJobs SDK) |
Hi, |
@VenkateshSrini This work is in progress. You can see the detailed status by watching the issues that @fabiocav listed above: #98 (comment) |
The WebJobs SDK port has been completed and merged. The basic extensions work has been done to enable work on the Script Runtime (Functions Runtime) to begin and that is currently in progress, tracked by Azure/azure-functions-host#1576 |
Will this open up improved local development options at all? |
@ahmelsayed Just checked and I was on node v8.0.0, not with v8.5.0, upgrading fixed the issue.
{ name: 'azure-functions-core-tools',
description: 'Azure Functions Core Tools',
'dist-tags': { latest: '1.0.4', core: '2.0.1-beta1.15' },
versions:
[ '1.0.0-beta.95',
'1.0.0-beta.96',
'1.0.0-beta.97',
'1.0.0-beta.98',
'1.0.0-beta.99',
'1.0.0-beta.100',
'1.0.0',
'1.0.1',
'1.0.2',
'1.0.3',
'1.0.4',
'2.0.0',
'2.0.1-beta.1',
'2.0.1-beta.2',
'2.0.1-beta.3',
'2.0.1-beta.4',
'2.0.1-beta.5',
'2.0.1-beta.6',
'2.0.1-beta.7',
'2.0.1-beta.8',
'2.0.1-beta.9',
'2.0.1-beta.10',
'2.0.1-beta.11',
'2.0.1-beta.12',
'2.0.1-beta.13',
'2.0.1-beta.14',
'2.0.1-beta1.15' ],
maintainers:
[ 'ahmelsayed <ahmelsayed@outlook.com>',
'mattmason03 <mamaso@microsoft.com>',
'windowsazure <azuresdk@outlook.com>' ],
time:
{ modified: '2017-09-24T01:21:58.149Z',
created: '2017-05-03T01:21:59.910Z',
'1.0.0-beta.95': '2017-05-03T01:21:59.910Z',
'1.0.0-beta.96': '2017-05-06T00:28:12.344Z',
'1.0.0-beta.97': '2017-05-16T00:36:46.444Z',
'1.0.0-beta.98': '2017-06-05T22:49:20.702Z',
'1.0.0-beta.99': '2017-06-06T17:44:30.500Z',
'1.0.0-beta.100': '2017-06-30T01:11:17.967Z',
'1.0.0': '2017-08-11T20:16:18.849Z',
'1.0.1': '2017-08-11T20:26:41.323Z',
'2.0.0': '2017-08-24T00:42:42.553Z',
'2.0.1-beta.1': '2017-08-24T00:52:25.874Z',
'2.0.1-beta.2': '2017-08-24T01:39:42.781Z',
'2.0.1-beta.3': '2017-08-24T03:59:28.009Z',
'2.0.1-beta.4': '2017-08-24T19:53:37.771Z',
'1.0.2': '2017-08-24T20:00:32.643Z',
'2.0.1-beta.5': '2017-08-24T20:48:29.592Z',
'2.0.1-beta.6': '2017-08-24T20:50:42.136Z',
'2.0.1-beta.7': '2017-08-24T22:34:29.823Z',
'2.0.1-beta.8': '2017-08-25T21:17:18.102Z',
'2.0.1-beta.9': '2017-08-28T23:39:47.614Z',
'2.0.1-beta.10': '2017-08-31T05:39:11.901Z',
'2.0.1-beta.11': '2017-08-31T23:24:58.043Z',
'1.0.3': '2017-09-08T20:24:56.964Z',
'2.0.1-beta.12': '2017-09-12T00:06:54.866Z',
'1.0.4': '2017-09-15T20:42:16.101Z',
'2.0.1-beta.13': '2017-09-23T01:13:19.707Z',
'2.0.1-beta.14': '2017-09-24T00:45:29.946Z',
'2.0.1-beta1.15': '2017-09-24T01:21:58.149Z' },
homepage: 'https://github.com/Azure/azure-functions-cli#readme',
repository:
{ type: 'git',
url: 'git+https://github.com/Azure/azure-functions-cli.git' },
author: 'Microsoft',
bugs: { url: 'https://github.com/Azure/azure-functions-cli/issues' },
license: 'MIT',
readmeFilename: '',
users: { lastexile: true, 'ivan.marquez': true },
version: '1.0.4',
scripts: { postinstall: 'node lib/install.js' },
preferGlobal: true,
bin:
{ func: 'lib/main.js',
azfun: 'lib/main.js',
azurefunctions: 'lib/main.js' },
os: [ 'win32' ],
dependencies:
{ chalk: '^2.1.0',
'command-exists': '^1.2.2',
tmp: '^0.0.33',
unzipper: '^0.8.9' },
dist:
{ integrity: 'sha512-I2MpcThfchxX6o6k8ndDcvY2zTgYO6xs619R+7RWUbYnUsJRqh40VYUjmColsg6yVf5Erqb8kdsrLJ9DF2OyUw==',
shasum: '0752a0b5b048f55fd955aa8b40874822b5a4d7cc',
tarball: 'https://registry.npmjs.org/azure-functions-core-tools/-/azure-functions-core-tools-1.0.4.tgz' },
directories: {} } |
I installed the latest version of VS tools by running |
@imsam67 these bits are in preview so you won't get them as a normal update. See this blog post for more details. |
@nelak you're right it looks like @mamaso added node >=8.4.0 and I didn't notice that. |
Interesting - iirc npm removed the explicit errors around invalid engines / node versions. I added the engines field as documentation / a guideline, but if it's causing these strange resolution failures we should pull it out. |
@fabiocav Apologies if I'm posting in the wrong issue... Does this issue cover the work required to get an asp.net core 2 web app with webjobs deployed to azure? In ASP.NET, we'd use |
@mattwoberts that's definitely a different topic, and is not directly related to Azure Functions. See https://stackoverflow.com/questions/38919723/how-do-i-deploy-an-azure-webjob-alongside-a-net-core-web-app-via-git#comment79729644_38919723 which discusses this. |
Nuget dependencies fail with OSX. Does not help to install nuget mono version. NuGet restore failed with message: 'Operation not permitted' |
what version of the cli do you have? can you run
|
There are known issues (we're documenting relevant issues here) with package restore that will be addressed with the next update, likely to occur by the end of next week. |
Closing this as the initial port has been completed. New tasks tracking gaps, improvements and bug fixes will be open with the appropriate labels. |
@fabiocav did everything got ported and out of preview? |
There are some gaps and it is still in preview, but we now have tracking issues for them/etc. so we've closed the main issue. |
@christopheranderson yeah... I found out that Also, we can't use VSTS to build/deploy it. We need to manually publish from our dev machines. Besides that, it work-ish. |
@galvesribeiro can you expand on what you mean by |
@fabiocav from the solution directory:
Multiple errors while building. If you want more details I can open another issue. Thanks |
This helps. One thing I did notice is that you're using the old Functions SDK (1.0.4). Fixes were made to more recent versions (the latest is 1.0.6) specifically for .NET Standard scenarios. Can you try upgrading to see if that helps? And yes, a separate issue so we don't have different side threads on this would be helpful. |
There is still no NET core template in VS. |
There are .net core template in vs 2017. |
This issue will track the .NET Core port activities for porting the runtime to .NET core. Note that netstandard 1.3 assemblies can be used on Azure Functions and this is fully supported.
We'll continue to update this list and details as we move along.
Have opened the following issues to track migration:
WebJobs SDK - Azure/azure-webjobs-sdk#1177
WebJobs SDK Extensions - Azure/azure-webjobs-sdk-extensions#233
WebJobs Script (Functions Runtime) - Azure/azure-functions-host#1576
Activities
Issues
The text was updated successfully, but these errors were encountered: