In order to add new threads or reply to existing posts, you have to be logged-in. If you are not registered yet, you need to register first, and then login with your personal credentials.
We are still working on the first release of CslaFactory. Although we have considered dropping out an early version, we are now sure the DSL itself has to be more comprehensive until we do that. This is mainly because changes to the DSL may have a strong impact on the templates and, even worse, might force you to abandon a model and start all over again. We will provider versioning in a later version, but at this point, changes of the DSL are simply too dangerous.
The documentation is very sketchy at the moment, but we decided to make it available for registered users, because it might give you a first impression of CslaFactory and its capabilities. Do not hesitate to ask any questions. We will try to answer your questions as soon as possible and fill in the gaps in the documentation.
Hi guys. This looks very interesting (Pity it wasn't around when I started writing my own attempt). I look forward to seeing as much documentation as you can let me have. The demo looks good but I look forward to something a liitle deeper. Still it is an excellent start. I wish you the best of luck in this venture. CSLA is an excellent framework and deserves to attract tools development of this type. I am always interested in comparing notes if that is of interest to you.
Regards
Simon May
Hi Simon,
please have a look at the About-Tab - as I mentioned before, the documentation is quite sketchy at the moment, but it is the only one we have...
Regards,
Marcel
Very interesting. May I ask, when sis you start using the VS DSL stuff. I looked at it around July 2006 and after some futile attemps to use it, in a proof of concept project, abandoned it as far too complex to use at that time. How much better is it now.
FYI. I attempted to start a new thread for this in the DSL forum but got an error. I thought that taht forum was the appropriate place for this post
Our first contact with the DsL-Tools was in September 2007(Release 1.0) . Since then Microsoft has fixed some bugs. For VS2008 ths main change is to move the runtime into ervery Visual Studio box, including the new VS2008 shell (redist of runtime no longer required) . Microsoft has also improved the path editing experince in the DSL-Designer. The roadmap plans support for interacting designers, amongst other things.
Our understanding ot the DSL-Tools was improved by the book "Domain Specific Development with Visual Studio DSL Tools" by Cook, Jones, Kent and Wills.
Thanks for the info. the DSL stuff sounds vastly improved from what I saw 18 months ago. I'll have another look when I move to VS2008 and have finished the modelling stuff I am working
Awsome demo. I was thinking about building one myself. It is the future.
Durring my research, I stumbled across the guys who helped design the DSL toolkit. They have a foctory for facories that may speed and ease your development.
It seems that they have taken the hard work out of allot of the recipe hookup ect.
I strongly reccomend them. softwarefactoriestoolkit.net
The Linq in CSLA 3.5 looks very cool as well.
Thanks for your hard work.
Hi Ben,
thanks for the hint. We are always interested in other SF projects and tools and I will definitely have a look at the toolkit.
Regards, Marcel
Hi --
I'm very excited to try out your product! The home page said to expect a CTP a few days ago... any update to report? Speaking for myself, I'd prefer ANY sort of deliverable, regardless if it has some bugs. I like how other projects have nightly builds available for those willing to take the risk.
Hi CJF,
I am very sorry for the delay, but we are currently struggling with some serialization issues. We are aware of other (minor?) bugs and the community is going to reveal new bugs while playing around with the CTP. Anyway, we want your models at least to be saved properly before we release the CTP (It is very annoying to edit the same properties or rules over and over again...believe me: I am currently testing it ). Thank you for your patience.