Skip to content
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

Q: Can't receive messages when object published is not exactly the same shared #37

Open
mivewi opened this issue Aug 5, 2023 · 1 comment

Comments

@mivewi
Copy link

mivewi commented Aug 5, 2023

When trying to solve my issue with not receiving messages, I tried playing with this sample: "https://github.com/rebus-org/RebusSamples/tree/master/PubSubNative" and found that the object, which is published from the publisher to the subscribers, have to be the exact same shared object "StringMessage". It does not work when I create classes by the same name and properties in each project. I like it to not have the shared files but have their own classes - if it's possible?

@JanRou
Copy link

JanRou commented Aug 6, 2023

Hi mivewi,

You can create a nuget packet with the definitions of data transfer objects, dtos, when you don't like a shared project. Then you can control all projects use the same version of the packet.
Hope it helps!

/Jan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants