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

Could not load type 'Microsoft.ServiceBus.Messaging.MessageClientEntity' from assembly 'Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. #3548

Closed
rbmanian75 opened this Issue Sep 11, 2015 · 69 comments

Comments

Projects
None yet
@rbmanian75

rbmanian75 commented Sep 11, 2015

We have upgraded Microsoft Azure Service Bus to version 3.0 and it seems to be that signal is breaking with the following error message

Could not load type 'Microsoft.ServiceBus.Messaging.MessageClientEntity' from assembly 'Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.TypeLoadException: Could not load type 'Microsoft.ServiceBus.Messaging.MessageClientEntity' from assembly 'Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[TypeLoadException: Could not load type 'Microsoft.ServiceBus.Messaging.MessageClientEntity' from assembly 'Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.]
Microsoft.AspNet.SignalR.ServiceBus.ServiceBusConnection..ctor(ServiceBusScaleoutConfiguration configuration, TraceSource traceSource) +0
Microsoft.AspNet.SignalR.ServiceBus.ServiceBusMessageBus..ctor(IDependencyResolver resolver, ServiceBusScaleoutConfiguration configuration) +227
Microsoft.AspNet.SignalR.DependencyResolverExtensions.UseServiceBus(IDependencyResolver resolver, ServiceBusScaleoutConfiguration configuration) +64
Sgc.Web.Code.Generic.SignalROWinStartup.Configuration(IAppBuilder app) +279

@tvanfosson

This comment has been minimized.

Show comment
Hide comment
@tvanfosson

tvanfosson Sep 15, 2015

I had a similar issue, seems to be resolved in 3.0.2

tvanfosson commented Sep 15, 2015

I had a similar issue, seems to be resolved in 3.0.2

@rbmanian75

This comment has been minimized.

Show comment
Hide comment
@rbmanian75

rbmanian75 Sep 16, 2015

I upgraded the azure servicebus to version 3.0.2 and the problem remains.

rbmanian75 commented Sep 16, 2015

I upgraded the azure servicebus to version 3.0.2 and the problem remains.

@nmehlei

This comment has been minimized.

Show comment
Hide comment
@nmehlei

nmehlei Sep 22, 2015

We noticed this as well and are already using the latest versions on NuGet.

nmehlei commented Sep 22, 2015

We noticed this as well and are already using the latest versions on NuGet.

@gregheidorn

This comment has been minimized.

Show comment
Hide comment
@gregheidorn

gregheidorn Sep 23, 2015

Just tried 3.0.0 and 3.0.3 and got this issue. Downgraded back to 2.7.6 until further notice.

gregheidorn commented Sep 23, 2015

Just tried 3.0.0 and 3.0.3 and got this issue. Downgraded back to 2.7.6 until further notice.

@profnimrod

This comment has been minimized.

Show comment
Hide comment
@profnimrod

profnimrod Sep 26, 2015

I have also stuck with 2.7.6 because of the same problem reported above with 3.0.x.

profnimrod commented Sep 26, 2015

I have also stuck with 2.7.6 because of the same problem reported above with 3.0.x.

@slashdotdash

This comment has been minimized.

Show comment
Hide comment
@slashdotdash

slashdotdash Sep 30, 2015

Encountered the same exception as above; resolved by downgrading WindowsAzure.ServiceBus to version 2.7.6

slashdotdash commented Sep 30, 2015

Encountered the same exception as above; resolved by downgrading WindowsAzure.ServiceBus to version 2.7.6

@kunjan13

This comment has been minimized.

Show comment
Hide comment
@kunjan13

kunjan13 Oct 3, 2015

Encountered the same exception as above; in version 3.0.3.
Reverting back till we have any updates on issue

kunjan13 commented Oct 3, 2015

Encountered the same exception as above; in version 3.0.3.
Reverting back till we have any updates on issue

@mb34124

This comment has been minimized.

Show comment
Hide comment
@mb34124

mb34124 Oct 7, 2015

3.0.4 has the same issue. Reverted to 2.7.6.

mb34124 commented Oct 7, 2015

3.0.4 has the same issue. Reverted to 2.7.6.

@sondreb

This comment has been minimized.

Show comment
Hide comment
@sondreb

sondreb Oct 12, 2015

Here is a forum thread with the same issue, for reference: http://forums.asp.net/t/2065443.aspx

Please give us an update on when this is planned to be fixed?

sondreb commented Oct 12, 2015

Here is a forum thread with the same issue, for reference: http://forums.asp.net/t/2065443.aspx

Please give us an update on when this is planned to be fixed?

@noocyte

This comment has been minimized.

Show comment
Hide comment
@noocyte

noocyte Oct 13, 2015

As far as I can see from the code the problem is that the Servicebus Scaleout code is using Begin/End async pattern; this has been removed from Service Bus SDK version 3 (it looks like). So in essence the service bus scaleout code has to be re-written to use async/await pattern.

I have re-written it so it compiles (https://github.com/proactima/SignalR), but not super happy about the implementation. However, as long as the processing is running in a threadpool thread it does not have to be async at all.

noocyte commented Oct 13, 2015

As far as I can see from the code the problem is that the Servicebus Scaleout code is using Begin/End async pattern; this has been removed from Service Bus SDK version 3 (it looks like). So in essence the service bus scaleout code has to be re-written to use async/await pattern.

I have re-written it so it compiles (https://github.com/proactima/SignalR), but not super happy about the implementation. However, as long as the processing is running in a threadpool thread it does not have to be async at all.

@iamshotgun

This comment has been minimized.

Show comment
Hide comment
@iamshotgun

iamshotgun Nov 4, 2015

we upgraded to version 3.0.7, still the same error. we went back to 2.7.6.

iamshotgun commented Nov 4, 2015

we upgraded to version 3.0.7, still the same error. we went back to 2.7.6.

@dersia

This comment has been minimized.

Show comment
Hide comment
@dersia

dersia Dec 7, 2015

Any news here? Just had to rollback to 2.7.6

dersia commented Dec 7, 2015

Any news here? Just had to rollback to 2.7.6

@MaDeRkAn

This comment has been minimized.

Show comment
Hide comment
@MaDeRkAn

MaDeRkAn Dec 25, 2015

We have same issue.

MaDeRkAn commented Dec 25, 2015

We have same issue.

@ucswift

This comment has been minimized.

Show comment
Hide comment
@ucswift

ucswift Jan 3, 2016

+1, just verified with 3.0.9

ucswift commented Jan 3, 2016

+1, just verified with 3.0.9

@kjartanvalur

This comment has been minimized.

Show comment
Hide comment
@kjartanvalur

kjartanvalur Jan 12, 2016

+1 verified with 3.0.9 and the newly released 3.1.1

kjartanvalur commented Jan 12, 2016

+1 verified with 3.0.9 and the newly released 3.1.1

@francescocristallo

This comment has been minimized.

Show comment
Hide comment
@francescocristallo

francescocristallo Feb 16, 2016

Any news on this problem? It's now 5 months, I`m stuck with an old release of Service bus SDK cause of this. The problem persist with 3.1.1 release as well

francescocristallo commented Feb 16, 2016

Any news on this problem? It's now 5 months, I`m stuck with an old release of Service bus SDK cause of this. The problem persist with 3.1.1 release as well

@MaDeRkAn

This comment has been minimized.

Show comment
Hide comment
@MaDeRkAn

MaDeRkAn Feb 16, 2016

@LightCrystal Service Bus is used by SignalR, Therefore I don't think sb team will change something for this. It looks like versioning issue and it's normal if u go 2 to 3. We should wait signalr team to fix it. And they focused on 3.0. So I don't think we will have minor update. If someone digs this issue and starts a branch I would like to help.

MaDeRkAn commented Feb 16, 2016

@LightCrystal Service Bus is used by SignalR, Therefore I don't think sb team will change something for this. It looks like versioning issue and it's normal if u go 2 to 3. We should wait signalr team to fix it. And they focused on 3.0. So I don't think we will have minor update. If someone digs this issue and starts a branch I would like to help.

@kunjan13

This comment has been minimized.

Show comment
Hide comment
@kunjan13

kunjan13 Mar 3, 2016

is this issue solved in 3.1.4?

kunjan13 commented Mar 3, 2016

is this issue solved in 3.1.4?

@evilpilaf

This comment has been minimized.

Show comment
Hide comment
@evilpilaf

evilpilaf Apr 5, 2016

I'm also having this problem, it's incredible that after all this time no one from microsoft is responding to this issue and we're left with an old and obsolete version of the service bus libraries.

evilpilaf commented Apr 5, 2016

I'm also having this problem, it's incredible that after all this time no one from microsoft is responding to this issue and we're left with an old and obsolete version of the service bus libraries.

@erichexter

This comment has been minimized.

Show comment
Hide comment
@erichexter

erichexter Apr 21, 2016

@davidfowl @DamianEdwards Guys, can you help us get some communication of this issue?

erichexter commented Apr 21, 2016

@davidfowl @DamianEdwards Guys, can you help us get some communication of this issue?

@paulirwin

This comment has been minimized.

Show comment
Hide comment
@paulirwin

paulirwin May 5, 2016

It has been almost 8 months and this issue remains. Can we get an update on this?

paulirwin commented May 5, 2016

It has been almost 8 months and this issue remains. Can we get an update on this?

@erichexter

This comment has been minimized.

Show comment
Hide comment
@erichexter

erichexter May 5, 2016

I talked with the head program manager and they are planning on testing
this out after the asp.net core 1 goes into release candidate. Don't know
the dates but they have a plan for how they intended to test this out , and
have given a verbal commitment to get it done.

On Thursday, May 5, 2016, Paul Irwin notifications@github.com wrote:

It has been almost 8 months and this issue remains. Can we get an update
on this?


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#3548 (comment)

Eric Hexter

blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter

erichexter commented May 5, 2016

I talked with the head program manager and they are planning on testing
this out after the asp.net core 1 goes into release candidate. Don't know
the dates but they have a plan for how they intended to test this out , and
have given a verbal commitment to get it done.

On Thursday, May 5, 2016, Paul Irwin notifications@github.com wrote:

It has been almost 8 months and this issue remains. Can we get an update
on this?


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#3548 (comment)

Eric Hexter

blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter

@joelclickpoint

This comment has been minimized.

Show comment
Hide comment
@joelclickpoint

joelclickpoint Jun 1, 2016

I need a SignalR+AzureServiceBus replacement at this point, anyone have any thoughts on options I can move forward with before I start researching independently?

joelclickpoint commented Jun 1, 2016

I need a SignalR+AzureServiceBus replacement at this point, anyone have any thoughts on options I can move forward with before I start researching independently?

@MaDeRkAn

This comment has been minimized.

Show comment
Hide comment
@MaDeRkAn

MaDeRkAn Jun 3, 2016

@joelclickpoint You can try Signalr+Redis.

MaDeRkAn commented Jun 3, 2016

@joelclickpoint You can try Signalr+Redis.

@noocyte

This comment has been minimized.

Show comment
Hide comment
@noocyte

noocyte Jun 3, 2016

It looks like the code has been updated already, it's just waiting to get pushed out... Since the current release is almost 1,5 years old it might be time for another release @DamianEdwards ?

noocyte commented Jun 3, 2016

It looks like the code has been updated already, it's just waiting to get pushed out... Since the current release is almost 1,5 years old it might be time for another release @DamianEdwards ?

@demirag

This comment has been minimized.

Show comment
Hide comment
@demirag

demirag Jun 9, 2016

This issue is getting annoying.

Lifecycle: Nuget-> upgrade all packages -> downgrade servicebus

Anyone knows if there will be a support at all?

demirag commented Jun 9, 2016

This issue is getting annoying.

Lifecycle: Nuget-> upgrade all packages -> downgrade servicebus

Anyone knows if there will be a support at all?

@erichexter

This comment has been minimized.

Show comment
Hide comment
@erichexter

erichexter Jun 9, 2016

I believe they are testing the fix now on https://jabbr.net/

Eric Hexter

blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter

On Thu, Jun 9, 2016 at 9:46 AM, Yusuf Demirag notifications@github.com
wrote:

This issue is getting annoying.

Lifecycle: Nuget-> upgrade all packages -> downgrade servicebus

Anyone knows if there will be a support at all?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#3548 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAHABO_igUXQeeuAPHYVsVHFo7P9Sl5Dks5qKCdKgaJpZM4F73Gv
.

erichexter commented Jun 9, 2016

I believe they are testing the fix now on https://jabbr.net/

Eric Hexter

blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter

On Thu, Jun 9, 2016 at 9:46 AM, Yusuf Demirag notifications@github.com
wrote:

This issue is getting annoying.

Lifecycle: Nuget-> upgrade all packages -> downgrade servicebus

Anyone knows if there will be a support at all?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#3548 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAHABO_igUXQeeuAPHYVsVHFo7P9Sl5Dks5qKCdKgaJpZM4F73Gv
.

@markheath

This comment has been minimized.

Show comment
Hide comment
@markheath

markheath Jul 1, 2016

@erichexter do you have any more information on this? Is the code for the fix available to view anywhere? This is a real problem for us in a project that we are trying to introduce SignalR to and can't easily downgrade to an older servicebus package.

markheath commented Jul 1, 2016

@erichexter do you have any more information on this? Is the code for the fix available to view anywhere? This is a real problem for us in a project that we are trying to introduce SignalR to and can't easily downgrade to an older servicebus package.

@joelclickpoint

This comment has been minimized.

Show comment
Hide comment
@joelclickpoint

joelclickpoint Jul 1, 2016

@erichexter I'd recommend doing what we had to do and just switch to SignalR+Redis, you can spin up an Azure-hosted Redis instance for fairly cheap and the configuration is basically the same:

GlobalHost.DependencyResolver.UseRedis(new RedisScaleoutConfiguration(connString, "appname"));
app.MapSignalR();

joelclickpoint commented Jul 1, 2016

@erichexter I'd recommend doing what we had to do and just switch to SignalR+Redis, you can spin up an Azure-hosted Redis instance for fairly cheap and the configuration is basically the same:

GlobalHost.DependencyResolver.UseRedis(new RedisScaleoutConfiguration(connString, "appname"));
app.MapSignalR();

@erichexter

This comment has been minimized.

Show comment
Hide comment
@erichexter

erichexter Jul 1, 2016

We just built from the pull request it has been in production for months
now. Works just just fine for us.

On Friday, July 1, 2016, joelclickpoint notifications@github.com wrote:

@erichexter https://github.com/erichexter I'd recommend doing what we
had to do and just switch to SignalR+Redis, you can spin up an Azure-hosted
Redis instance for fairly cheap and the configuration is basically the same:

GlobalHost.DependencyResolver.UseRedis(new
RedisScaleoutConfiguration(connString, "appname"));
app.MapSignalR();


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#3548 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAHABMeOM-lc8oo7xfkbKJcwp9IRRHnvks5qRRbGgaJpZM4F73Gv
.

Eric Hexter

blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter

erichexter commented Jul 1, 2016

We just built from the pull request it has been in production for months
now. Works just just fine for us.

On Friday, July 1, 2016, joelclickpoint notifications@github.com wrote:

@erichexter https://github.com/erichexter I'd recommend doing what we
had to do and just switch to SignalR+Redis, you can spin up an Azure-hosted
Redis instance for fairly cheap and the configuration is basically the same:

GlobalHost.DependencyResolver.UseRedis(new
RedisScaleoutConfiguration(connString, "appname"));
app.MapSignalR();


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#3548 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAHABMeOM-lc8oo7xfkbKJcwp9IRRHnvks5qRRbGgaJpZM4F73Gv
.

Eric Hexter

blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter

@maxal1917

This comment has been minimized.

Show comment
Hide comment
@maxal1917

maxal1917 Jul 1, 2016

We switched to Redis. It works.

maxal1917 commented Jul 1, 2016

We switched to Redis. It works.

@markheath

This comment has been minimized.

Show comment
Hide comment
@markheath

markheath Jul 1, 2016

@erichexter thanks, couldn't see anything in the list of open PRs. Was it this one you used?

markheath commented Jul 1, 2016

@erichexter thanks, couldn't see anything in the list of open PRs. Was it this one you used?

@markheath

This comment has been minimized.

Show comment
Hide comment
@markheath

markheath Jul 4, 2016

I've come up with a fairly simple fix of my own (commit here) which seems to work, by simply creating extension methods to fake the missing APM methods. I'll submit a PR if it passes further testing.

markheath commented Jul 4, 2016

I've come up with a fairly simple fix of my own (commit here) which seems to work, by simply creating extension methods to fake the missing APM methods. I'll submit a PR if it passes further testing.

@keithl8041

This comment has been minimized.

Show comment
Hide comment
@keithl8041

keithl8041 Jul 5, 2016

I forked and built the version by @markheath but wasn't able to get it working (surely my own fault rather than Marks), so have downgraded to v2.8.2 until this is fixed officially.

keithl8041 commented Jul 5, 2016

I forked and built the version by @markheath but wasn't able to get it working (surely my own fault rather than Marks), so have downgraded to v2.8.2 until this is fixed officially.

@markheath

This comment has been minimized.

Show comment
Hide comment
@markheath

markheath Jul 5, 2016

@keithl8041 make sure you built from the bug-3548 branch - it's not merged into the dev branch on my fork. Does seem to be working in our initial testing.

markheath commented Jul 5, 2016

@keithl8041 make sure you built from the bug-3548 branch - it's not merged into the dev branch on my fork. Does seem to be working in our initial testing.

@jarlem

This comment has been minimized.

Show comment
Hide comment
@jarlem

jarlem Jul 7, 2016

@markheath Did you only build the "Microsoft.AspNet.SignalR.ServiceBus" project and referenced the dll? Or did you build and include the other SignalR projects as well? Did you make a nuget package out of it? ... I can't get it to work by just building and referencing the new dll...

jarlem commented Jul 7, 2016

@markheath Did you only build the "Microsoft.AspNet.SignalR.ServiceBus" project and referenced the dll? Or did you build and include the other SignalR projects as well? Did you make a nuget package out of it? ... I can't get it to work by just building and referencing the new dll...

@markheath

This comment has been minimized.

Show comment
Hide comment
@markheath

markheath Jul 7, 2016

@jarlem yes, it's a bit of a pain to use the updated ServiceBus DLL as you'd also need to bring in the main SignalR dll you built as well due to strong naming. We ended up making our own company NuGet package of just the SignalR.ServiceBus project, which referenced the main NuGet SignalR package. I've also got a little sample application proving it working with two separate web projects communicating through servicebus that I can share once if strip out our servicebus connection string from the code.

markheath commented Jul 7, 2016

@jarlem yes, it's a bit of a pain to use the updated ServiceBus DLL as you'd also need to bring in the main SignalR dll you built as well due to strong naming. We ended up making our own company NuGet package of just the SignalR.ServiceBus project, which referenced the main NuGet SignalR package. I've also got a little sample application proving it working with two separate web projects communicating through servicebus that I can share once if strip out our servicebus connection string from the code.

@keithl8041

This comment has been minimized.

Show comment
Hide comment
@keithl8041

keithl8041 Jul 7, 2016

Mark, please do share that if you can. I was having the same issue when
trying to get it to run.

keithl8041 commented Jul 7, 2016

Mark, please do share that if you can. I was having the same issue when
trying to get it to run.

@markheath

This comment has been minimized.

Show comment
Hide comment
@markheath

markheath Jul 7, 2016

@keithl8041 try this: https://1drv.ms/u/s!Aoaqn397na7vjakf5oTlQwCG1Rt7VA
Set both web projects as startup projects, and paste in your service bus connection string to both Startup.cs files.

markheath commented Jul 7, 2016

@keithl8041 try this: https://1drv.ms/u/s!Aoaqn397na7vjakf5oTlQwCG1Rt7VA
Set both web projects as startup projects, and paste in your service bus connection string to both Startup.cs files.

@alexjamesbrown

This comment has been minimized.

Show comment
Hide comment
@alexjamesbrown

alexjamesbrown Aug 11, 2016

Looks like someone needs to change their email password

alexjamesbrown commented Aug 11, 2016

Looks like someone needs to change their email password

@iamshotgun

This comment has been minimized.

Show comment
Hide comment
@iamshotgun

iamshotgun Nov 3, 2016

tried last night, same problem...

iamshotgun commented Nov 3, 2016

tried last night, same problem...

@profnimrod

This comment has been minimized.

Show comment
Hide comment
@profnimrod

profnimrod Nov 3, 2016

I'd been waiting for more than a year for this issue to be fixed. Last week I decided to switch over to using Redis Cache for the backplane, and it works fine.

profnimrod commented Nov 3, 2016

I'd been waiting for more than a year for this issue to be fixed. Last week I decided to switch over to using Redis Cache for the backplane, and it works fine.

@snekbaev

This comment has been minimized.

Show comment
Hide comment
@snekbaev

snekbaev Nov 3, 2016

Indeed. We decided to use Azure Service Bus as the backplane, at the moment developing the app based on custom aforementioned fix. Hopefully when we go to production it won't cause any surprises :)

snekbaev commented Nov 3, 2016

Indeed. We decided to use Azure Service Bus as the backplane, at the moment developing the app based on custom aforementioned fix. Hopefully when we go to production it won't cause any surprises :)

@moozzyk

This comment has been minimized.

Show comment
Hide comment
@moozzyk

moozzyk Nov 3, 2016

Contributor

The problem is that because of the breaking changes in the Service Bus 3.0+ updating SignalR packages to this version in a minor/patch release would either prevent people from updating to the latest version of SignalR or would break them. Servicing releases should not have breaking changes. I have not tried it myself but I saw a package on NuGet which claims it is a Service Bus backplane for SignalR using ServiceBus 3.0.

Contributor

moozzyk commented Nov 3, 2016

The problem is that because of the breaking changes in the Service Bus 3.0+ updating SignalR packages to this version in a minor/patch release would either prevent people from updating to the latest version of SignalR or would break them. Servicing releases should not have breaking changes. I have not tried it myself but I saw a package on NuGet which claims it is a Service Bus backplane for SignalR using ServiceBus 3.0.

@snekbaev

This comment has been minimized.

Show comment
Hide comment
@snekbaev

snekbaev Nov 3, 2016

@moozzyk isn't it possible to release a major version then? I believe eventually what matters is the ability to use the latest version of dependencies, which will be minor/patch upgradable themselves, but mainly, get a tested and production ready version from the SignalR team itself.

snekbaev commented Nov 3, 2016

@moozzyk isn't it possible to release a major version then? I believe eventually what matters is the ability to use the latest version of dependencies, which will be minor/patch upgradable themselves, but mainly, get a tested and production ready version from the SignalR team itself.

@moozzyk

This comment has been minimized.

Show comment
Hide comment
@moozzyk

moozzyk Nov 8, 2016

Contributor

@snekbaev - we are working on the next major release but things will most likely look differently there.

Contributor

moozzyk commented Nov 8, 2016

@snekbaev - we are working on the next major release but things will most likely look differently there.

@KeishaW

This comment has been minimized.

Show comment
Hide comment
@KeishaW

KeishaW Nov 23, 2016

Why is a fix for this problem taking so long? I recently encountered the same problem, but this thread was started over a year ago. The use of redis is currently not the best option for my solution, hence I was looking for a fix for the ServiceBus 3.0+ issue.

KeishaW commented Nov 23, 2016

Why is a fix for this problem taking so long? I recently encountered the same problem, but this thread was started over a year ago. The use of redis is currently not the best option for my solution, hence I was looking for a fix for the ServiceBus 3.0+ issue.

@KSemenenko

This comment has been minimized.

Show comment
Hide comment
@KSemenenko

KSemenenko Dec 7, 2016

Hi, I have the same problem, tried different versions but it still does not work. what is the problem? someone fix it?

KSemenenko commented Dec 7, 2016

Hi, I have the same problem, tried different versions but it still does not work. what is the problem? someone fix it?

@bogdangrigg

This comment has been minimized.

Show comment
Hide comment
@bogdangrigg

bogdangrigg Dec 13, 2016

We are experiencing the same issues - is there a planned fix?
Is the Azure Service Bus still a supported scale-out option?

bogdangrigg commented Dec 13, 2016

We are experiencing the same issues - is there a planned fix?
Is the Azure Service Bus still a supported scale-out option?

@philcarbone

This comment has been minimized.

Show comment
Hide comment
@philcarbone

philcarbone Jan 16, 2017

Hello? Anyone paying attention here?

philcarbone commented Jan 16, 2017

Hello? Anyone paying attention here?

@moozzyk

This comment has been minimized.

Show comment
Hide comment
@moozzyk

moozzyk Jan 16, 2017

Contributor

See my comment above: #3548 (comment)

Contributor

moozzyk commented Jan 16, 2017

See my comment above: #3548 (comment)

@isobarfilippis

This comment has been minimized.

Show comment
Hide comment
@isobarfilippis

isobarfilippis Jan 16, 2017

Are you freeking kidding me? Just recompiled SignalR.ServiceBus against WindowsAzure.ServiceBus 3.4.4 and all I had to change is a couple BeginXXX to XXXAsync. It was like 10 minutes and your library is actually broken for 1.5 years. Again are you freeking kidding me?

isobarfilippis commented Jan 16, 2017

Are you freeking kidding me? Just recompiled SignalR.ServiceBus against WindowsAzure.ServiceBus 3.4.4 and all I had to change is a couple BeginXXX to XXXAsync. It was like 10 minutes and your library is actually broken for 1.5 years. Again are you freeking kidding me?

@moozzyk moozzyk self-assigned this Jan 25, 2017

@moozzyk moozzyk closed this in #3845 Feb 9, 2017

@moozzyk moozzyk added this to the 2.2.2 milestone Feb 13, 2017

@itsmaryann

This comment has been minimized.

Show comment
Hide comment
@itsmaryann

itsmaryann Mar 16, 2017

Thanks for fixing the issue. When will 2.2.2 be released? We are awaiting a fix for a long time now. :)

itsmaryann commented Mar 16, 2017

Thanks for fixing the issue. When will 2.2.2 be released? We are awaiting a fix for a long time now. :)

@moozzyk

This comment has been minimized.

Show comment
Hide comment
@moozzyk

moozzyk Apr 13, 2017

Contributor

2.2.2-preview1 is now on NuGet

Contributor

moozzyk commented Apr 13, 2017

2.2.2-preview1 is now on NuGet

@erichexter

This comment has been minimized.

Show comment
Hide comment
@erichexter

erichexter Apr 21, 2017

We just tested this out Microsoft.AspNet.SignalR.ServiceBus" 2.2.2-preview1 and we still get this error when referencing WindowsAzure.ServiceBus 3.1.5 @davidfowl

erichexter commented Apr 21, 2017

We just tested this out Microsoft.AspNet.SignalR.ServiceBus" 2.2.2-preview1 and we still get this error when referencing WindowsAzure.ServiceBus 3.1.5 @davidfowl

@BrennanConroy

This comment has been minimized.

Show comment
Hide comment
@BrennanConroy

BrennanConroy Apr 21, 2017

Contributor

You need to use the Microsoft.AspNet.Signalr.ServiceBus3 package, because changing the normal one to use ServiceBus 3 would be a breaking change we had to make a new package name.

Contributor

BrennanConroy commented Apr 21, 2017

You need to use the Microsoft.AspNet.Signalr.ServiceBus3 package, because changing the normal one to use ServiceBus 3 would be a breaking change we had to make a new package name.

@erichexter

This comment has been minimized.

Show comment
Hide comment
@erichexter

erichexter Apr 21, 2017

erichexter commented Apr 21, 2017

@ranadheerrannu

This comment has been minimized.

Show comment
Hide comment
@ranadheerrannu

ranadheerrannu Aug 4, 2017

Is this issue still exists ? I am still facing it

ranadheerrannu commented Aug 4, 2017

Is this issue still exists ? I am still facing it

@moozzyk

This comment has been minimized.

Show comment
Hide comment
@moozzyk

moozzyk Aug 4, 2017

Contributor

@ranadheerrannu - You need to use the Microsoft.AspNet.Signalr.ServiceBus3 package with ServiceBus 3.0 (see: #3548 (comment))

Contributor

moozzyk commented Aug 4, 2017

@ranadheerrannu - You need to use the Microsoft.AspNet.Signalr.ServiceBus3 package with ServiceBus 3.0 (see: #3548 (comment))

@BayerWhite

This comment has been minimized.

Show comment
Hide comment
@BayerWhite

BayerWhite Aug 8, 2017

Confirmed that using NuGet -package Microsoft.AspNet.SignalR.ServiceBus3 with NuGet -package WindowsAzure.ServiceBus works.

Feel free to remove package Microsoft.AspNet.SignalR.ServiceBus once "ServiceBus3" is installed.

BayerWhite commented Aug 8, 2017

Confirmed that using NuGet -package Microsoft.AspNet.SignalR.ServiceBus3 with NuGet -package WindowsAzure.ServiceBus works.

Feel free to remove package Microsoft.AspNet.SignalR.ServiceBus once "ServiceBus3" is installed.

@juniwang

This comment has been minimized.

Show comment
Hide comment
@juniwang

juniwang Nov 15, 2017

Microsoft.AspNet.Signalr.ServiceBus3 works well with the latest stable WindowsAzure.ServiceBus 4.1.6. And you guys need to update the related documents as well like https://docs.microsoft.com/en-us/aspnet/signalr/overview/performance/scaleout-with-windows-azure-service-bus. Everyone would encounter this problem by following your examples/docs.

juniwang commented Nov 15, 2017

Microsoft.AspNet.Signalr.ServiceBus3 works well with the latest stable WindowsAzure.ServiceBus 4.1.6. And you guys need to update the related documents as well like https://docs.microsoft.com/en-us/aspnet/signalr/overview/performance/scaleout-with-windows-azure-service-bus. Everyone would encounter this problem by following your examples/docs.

@luizs81

This comment has been minimized.

Show comment
Hide comment
@luizs81

luizs81 Jan 10, 2018

For God sake, someone should update the documentation: https://docs.microsoft.com/en-us/aspnet/signalr/overview/performance/scaleout-with-windows-azure-service-bus

I wasted kinda long time trying to find the problem on my code/configuration.

luizs81 commented Jan 10, 2018

For God sake, someone should update the documentation: https://docs.microsoft.com/en-us/aspnet/signalr/overview/performance/scaleout-with-windows-azure-service-bus

I wasted kinda long time trying to find the problem on my code/configuration.

@kotpal

This comment has been minimized.

Show comment
Hide comment
@kotpal

kotpal Jun 7, 2018

Please update the documentation at https://docs.microsoft.com/en-us/aspnet/signalr/overview/performance/scaleout-with-windows-azure-service-bus. The package Microsoft.AspNet.Signalr.ServiceBus doesn't work and only Microsoft.AspNet.Signalr.ServiceBus3 should be used.

kotpal commented Jun 7, 2018

Please update the documentation at https://docs.microsoft.com/en-us/aspnet/signalr/overview/performance/scaleout-with-windows-azure-service-bus. The package Microsoft.AspNet.Signalr.ServiceBus doesn't work and only Microsoft.AspNet.Signalr.ServiceBus3 should be used.

@davidfowl

This comment has been minimized.

Show comment
Hide comment
@davidfowl
Member

davidfowl commented Jun 7, 2018

@kotpal

This comment has been minimized.

Show comment
Hide comment
@kotpal

kotpal Jun 7, 2018

Thanks, @davidfowl . For those of us not yet ready to move to ASP.NET Core, it is also good to have a no-jQuery SignalR ES6 module which we can use in Angular and other modern JavaScript framework.

kotpal commented Jun 7, 2018

Thanks, @davidfowl . For those of us not yet ready to move to ASP.NET Core, it is also good to have a no-jQuery SignalR ES6 module which we can use in Angular and other modern JavaScript framework.

@davidfowl

This comment has been minimized.

Show comment
Hide comment
@davidfowl

davidfowl Jun 7, 2018

Member

For those of us not yet ready to move to ASP.NET Core, it is also good to have a no-jQuery SignalR ES6 module which we can use in Angular and other modern JavaScript framework.

We have no plans to do that work.

Member

davidfowl commented Jun 7, 2018

For those of us not yet ready to move to ASP.NET Core, it is also good to have a no-jQuery SignalR ES6 module which we can use in Angular and other modern JavaScript framework.

We have no plans to do that work.

@kotpal

This comment has been minimized.

Show comment
Hide comment
@kotpal

kotpal Jun 7, 2018

I guess the previous plans - https://twitter.com/davidfowl/status/781391761327304704 - didn't pan out then.

kotpal commented Jun 7, 2018

I guess the previous plans - https://twitter.com/davidfowl/status/781391761327304704 - didn't pan out then.

@davidfowl

This comment has been minimized.

Show comment
Hide comment
@davidfowl

davidfowl Jun 7, 2018

Member

ASP.NET Core SignalR's js client doesn't support jQuery. We have no plans to go back and rewrite the ASP.NET SignalR js client.

Member

davidfowl commented Jun 7, 2018

ASP.NET Core SignalR's js client doesn't support jQuery. We have no plans to go back and rewrite the ASP.NET SignalR js client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment