WebHooks for ASP.NET Core

[smbecker]

Is there a plan to support ASP.NET 5?

[Eilon]

Of course 😄

[garora]

We have ASP.NET5 Beta7 released, so, what we are meant with the support of ASP.NET5?
I believe @HenrikFrystykNielsen - already planned 👍 and @Eilon already answered, awesome to read it.

[Eilon]

There is no support yet for Web Hooks on ASP.NET 5. It currently works with ASP.NET 4.x only.

[garora]

@Eilon thanks for confirming but as per your above reply, I understood that its in plan?

[Eilon]

We intend to support it. There is no specific date.

[nicofr83]

Any news/date on this support ? I need to run a web hook under a linux box and I would hate to return to javascript/node... Thanks

[Eilon]

Sorry no updates at this time.

[rposener]

Just FYI - I have a pending pull request with mostly working port of the base and custom sender/receiver. Hopefully we will see this soon. Will need some help building up the supported receivers for the various supported hooks out of the box - if you want to help contribute those once the base stuff is sync'd in.

[Eilon]

@rposener I do intend to take a look at it, but I just haven't yet found the time. It's kind of a big PR 😄

[mikeesouth]

Any news? I am also intrested in this.

[rposener]

Still waiting to hear from the asp.net core team. The code base has moved a lot since this pull request. Anyone interested is just writing out own since MS is being so slow? New tooling should be out this week helping us move onto CLI. Unless MS give confirmation that they will actually review and give input on a pull request to get this done. Kind of frustrating they are not embracing OSS community any more than this on this project!

[HenrikFrystykNielsen]

I know this is frustrating and I apologize. With RC2 being out, my hope is that we can get some more cycles from the right people. Stay tuned!

[mikeesouth]

Can we help out somehow? I'm really waiting for this so being able to help our getting an ETA would be great :)

[rposener]

The pull request is there, updated to rc2 with custom sender and receiver working in sample.

Might be good if you at minimum grabbed the source from pull source https://github.com/rposener/webhooks and gave it a test and provide comments.

Just need some review from asp.net team, and it to be merged in. If you want to fork a copy of the pull request and build xunit tests to convert the existing test sets. Then we just need to crank through the other receivers and samples.

[mikeesouth]

Unfortunately, I'm not much help here. I'm having troubles understanding your changes @rposener. The commits have thousands of changed files and I'm too new to loading custom libraries so I'm afraid I'm not much help here. I'll need some serious instructions on how to incorporate a custom built lib into an ASP.NET Core project. I would also like to use the Slack receiver but I assume I can mimic it with a custom receiver.
So, any help to get me on track or even better - an official merge into the core library would be great :)

[ups216]

hi, asp.net core 1.0 is now RTM. Is there any progress on porting this to core?

[bragma]

I'd really like to see this ported to Core too. Please do it! :)

[ArturKarbone]

@rposener, I just pulled your fork. Was not able to run it, since it's still requires RC2. Anyway I looked through the code. At the first glance it looks there are no breaking changes in terms of method's signatures/contracts.

However, there is something Core specific stuff, like initialization extensions, middleWare, etc.

I mean to support Core, WebHooks should support two code bases now, right? Otherwise previous package clients will be in trouble. Just wandering what is the best way to go here?

[tedvanderveen]

@Eilon as you assigned this issue to yourself, can you please update on status? With Core 1.0.0 released it would be a good time to look at the PR that @rposener invested time in developing?

[coderabsolute]

Any timelines to have the Webhook functionality released?

[BenHayat]

Is WH based on similar principals as SignalR? Do they overlap or complement each other?

Can't wait for these two to come to ASP.Net Core.

Thanks!
..Ben

[consigliory]

+1

[divad4686]

+1

[SimoneBWS]

👍

[hasan-assi]

+1

[toast-gear]

+1

[Cafeffroi]

Any news about asp.net core support ?

[stodolos]

Any updates on Core support timeline?

[dougbu]

Closing because remaining work is tracked in smaller issues. Though we'll reevaluate some design details and fill in gaps, the overall ASP.NET Core receiver basics and 10 receivers are in place.

[mkArtakMSFT]

Reopening this as a high-level tracking item for all the receivers work for 2.1 release

[dougbu]

What does "Working" mean here and why this issue is assigned to me? I have no action items I'm aware of that aren't already assigned to me.

We closed #5 when the port was complete and all known additional work for the 2.1 release (really 1.0 RTM) and beyond was tracked elsewhere.

[mkArtakMSFT]

Removed the 2 - Working label as this is just an umbrella item, to track the rest of the work in this area for upcoming release.

[dougbu]

Added cost - 0 since this is an umbrella tracking issue.

[dougbu]

Suggest we un-assign this issue and remove the Mapped to Big Rock label.

Alternatively, could close this issue as well as aspnet/Specs#103.

[dougbu]

@mkArtakMSFT @danroth27 @Eilon similar to aspnet/specs#103, I suggest we close this issue. Agreed?

[danroth27]

I think we can close this since implementing WebHooks support for ASP.NET Core is what this repo is all about.