Zebus | A lightweight Peer to Peer Service Bus | Pub Sub library
kandi X-RAY | Zebus Summary
kandi X-RAY | Zebus Summary
Zebus is peer to peer, so it does not depend on a broker to dispatch messages between the peers. This allows it to reach a throughput of 140k msg/s and a roundtrip latency under 500µs (have a look at the Performance page for details). It is resilient thanks to the absence of a broker and an optional persistence feature that ensures that messages are not lost if a peer is down or disconnected. It is stable, since we have been using it on a production environment at Abc Arbitrage for more than six years, handling hundreds of millions of messages per day.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Zebus
Zebus Key Features
Zebus Examples and Code Snippets
Community Discussions
Trending Discussions on Zebus
QUESTION
I made a NuGet package which generates C# code from DSL files at design and build time. It works fine in Visual Studio but has some issues in Rider (which I'll describe below).
In Visual StudioThe package declares custom items for the DSL files, and assigns them a MSBuild:Compile
Generator
metadata, which triggers a design-time build in Visual Studio every time a file changes.
Then, a custom target hooks to the build with BeforeTargets="CoreCompile"
. It generates the C# code and adds Compile
items to the project. The target runs in both normal and design-time builds, and supports incremental builds to avoid unnecessary work.
Here's the relevant (simplified and commented) MSBuild code:
The props
file:
ANSWER
Answered 2019-Feb-18 at 16:55I have two stories for you - the short one and the long one =)
The short storyIt should work out of the box in the upcoming 2019.1 EAP 1
The long storyRider (unlike Visual Studio) does not perform design time build during project loading stage. We thinks it is too expensive (especially for .net sdk based projects). So Rider evaluates every project and then builds some set of predefined targets to obtain generated files and assembly references.
Sometimes it cause issues (like this one) so in 2019.1 we have implemented additional algorithm which scans all imported targets and looks for a custom item-factory
targets. As far as I can see, your target perfectly fits so Rider will be able to find it and build alongs with predefined targets.
If it will not work somehow you still will have two options:
- We have rewritten
Build Tools
option page, so you will be able to add any custom target to loading process - Fire an issue here: https://youtrack.jetbrains.com/newIssue?project=Rider and I will try to fix your case ASAP. Such issues have the highest priority for us.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install Zebus
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page