Believe it or not, we've had quite a few developers not wanting to use uComponents as they only want to use a small subset of its functionality, say MNTP - they consider the rest of it as bloat ... or becoming more bloated over time!
The idea of the separation would be to put all the areas of functionality into their own assembly; e.g. DataTypes, XsltExtensions, UI, uQuery, etc.
Then developers/users can take which parts they want/need.
On top of this, as an addition, we are planning to use ILMerge to bundle them all up into an "uComponents.Ultimate" assembly ... for those who are happy with a standalone assembly.
We haven't started development on this yet... so still open to ideas/suggestions.
Why? separation of uComponents into logical / standalone assemblies.
Hi
Just out of curiosity why would the team separate ucomponents into standalone assemblies? (taking from the roadmap)
Hi Christian,
Believe it or not, we've had quite a few developers not wanting to use uComponents as they only want to use a small subset of its functionality, say MNTP - they consider the rest of it as bloat ... or becoming more bloated over time!
The idea of the separation would be to put all the areas of functionality into their own assembly; e.g. DataTypes, XsltExtensions, UI, uQuery, etc.
Then developers/users can take which parts they want/need.
On top of this, as an addition, we are planning to use ILMerge to bundle them all up into an "uComponents.Ultimate" assembly ... for those who are happy with a standalone assembly.
We haven't started development on this yet... so still open to ideas/suggestions.
Cheers, Lee.
Thanks for answer.
BTW I think uComponents is really well structured and with the nice use embedded resources - kudos to the team :-)
If anything, uComponents should all be in core - it's that good.
is working on a reply...