Hi,
On 4/5/06, Pathogenix <[EMAIL PROTECTED]> wrote:
>
> I'm currently converting a fairly complex ASP.Net 2.0 page over the
> Ajax.Net professional framework, I've noticed, being the good
> refactoring coder that I am, that my page class is becoming very thin
> to the point where half my methods are as simple as
>
> [AjaxMethod()]
> public SomeClass(...)
> {
> return Data.SomeMethod(...)
> }
>
> where Data is my data access layer. I'm considering factoring the page
> into two separate classes, one to manage initial page state and perform
> any rendering, and a second class to enforce business logic and perform
> those mini data-access methods; has anyone got any suggestions for neat
> architecturing with Ajax.Net?
I always create own classes that a running as AJAX data access layer
to the business logic. I never use methods directly in pages.
> Secondly, a bit of a grumble, I love how much support you're giving us
> Michael, and I love how quickly new versions are released, but would it
> be possible to maintain a stable and experimental branch? I've found
Do you really have this often that something is not working because of
switching to a newer version? Would be nice to get such feedbacks
earlier because I use the library in different projects and never had
such problems. There are changes between the old one and the
Professional one. Can you give me an example where changes are made
that makes big code changes for you?
> that quite often, I'll change versions and that the deserializers have
> altered and all my code breaks; while I understand most of the changes
> you're making, and think you're doing a fantastic job, I'd like to have
> a bit more faith that a bug fixing version won't throw my code out of
> whack. Please don't take this the wrong way, I still love you Mr
> Schwarz :) I don't know what kind of source control you're using to
> maintain this, so this might be more trouble than it's worth.
I'm running source safe since beginning of this year, since I got the
MVP status.
> Lastly, I'm thinking about rewriting the serialization to make use of
> Generics and get rid of the object signatures. I'd be thinking about,
> for example IJavaScriptConvertor<T> for serializing to and from T, and
> a method SerializeArray<T>(IEnumerable<T>, IJavaScriptConvertor<T>); is
> this any use to you, do you have any plans of your own, can I submit
> patches to you, and do you have any words of warning or advice?
Yes, if you have patches, changes or new ideas, send me the files and
I will check if they fit in the library. Would be nice to get help, of
course!
Regards,
Michael
>
> Love the framework as it stands, keep up the good work
>
> -- flinky wisty pomm
>
>
> >
>
--
Kind regards,
Michael Schwarz
Microsoft MVP - Most Valuable Professional
Microsoft MCAD - Certified Application Developer
http://www.schwarz-interactive.de/
mailto:[EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ajax.NET Professional" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/ajaxpro
The latest downloads of Ajax.NET Professional can be found at
http://www.ajaxpro.info
-~----------~----~----~----~------~----~------~--~---
