2. BreezeSharp Feature Suggestions
Help us make Breeze.sharp better by letting us know what you’d like to see next.
Suggest new features, vote on existing ones, or fork Breeze in GitHub and send us a pull request.
6 results found
-
Support more platforms
Please support Xamarin.Forms (Droid, iOS and UWP as a least).
Please see this issue:
https://github.com/Breeze/breeze.sharp/issues/22This project looks pretty dead to me, that' such a shame. It's a very compelling project, I'm willing to contribute.
3 votes -
RaisePropertyChanged in Client entities
I find impossible to use Breeze because my business model is based on shared entities.
In order to make Breeze work on the client, the entities have to inherit from BaseEntity.
Which is not a big problem since it can be done with partial classes.
The real issues are:
- It's impossible to reuse existing properties. In my scenario I'm using Fody.PropertyChanged to render all my auto-properties as INPCs. With Breeze, all getters have to call GetValue and setters SetValue.
- Had the BaseEntity exposed a RaisePropertyChanged method, and I could at least call SetValue on that method.So my…
3 votes -
Automate generation of client side entities
add standard T4 templates or some other way of generating client side entities from POCO Models.
It will greatly help people trying to hand-code or come up with their own T4 templates.14 votes -
Sign assemblies with strong names
Would be handy to have signed assemblies especially when installing from nuget.
2 votes -
Breeze.Sharp with EasynetQ
Hi Guys, Love your work. Would love to be able to use Breeze.Sharp with EasynetQ (RabbitMQ). Anything I am missing to be able to do this?
6 votes -
Token Authentication
Breeze Sharp is actually a revolution on the .NET Platform. I have two suggestions.
(1) Make Breeze Server able to be hosted on other Platform. That is untie it from IIS.
(2) Add Token Authentication (or show us how to use it) as is the case for BreezeJS.4 votes
- Don't see your idea?