Saturday, July 30, 2005

My Blue sky holiday - KL (Malaysia) trip

Just came back from a _small_ vacation in KL, Malaysia with friends. We drove all the way to KL and drove back... phew...
Nothing much to do there except to eat and drive around..
Please be carefull driving in KL, all the women seem to be F1 trained!
Lovely place, except the killer traffic!
And The Pertronas looks _amazing_ in the night time, so beautifully lit up... worth a second trip...

Tuesday, July 19, 2005

VS.NET 2005 and VSS 2005 July CTP

VS.NET 2005 and VSS 2005 July CTP were released on 12th of July. Now upgrading my version from June CTP to July CTP.June CTP has some major changes over its predecessor including the Membership API changes which was pretty scary to fix. But we got all the api differences fixed and now anticipating what changes will the July CTP bring.. Hopefully nothing that breaks the code...
Anyone working with July CTP yet?

Friday, July 15, 2005

Major Change - Bloodline

We have been using typed datasets(which are heavy as we all know) for LoneStar. But as we slowly move forward, more and more disadvantages are showing.
So we made a drastic decision. Change the blood line from Typed Data Sets to custom objects...
Considering the existing work that we have done, it will definetly take some time to change the business entity from datasets to custom objects, but there is a good news, we are still using the same typed datasets! Where? inside the custom classes!
We get some advantages here...
1) We still retain the typed tables in our custom classes making the job of the develope a lot easier, compared to classes with untyped datatables or untryped datasets or simple classes or even typed datasets!2) We make the bloodline of our projects ( the business entities) a lot more leaner compared to typed datasets!!3) We still have those typed datasets in the project, but they are now arranged logically accroding to the modules and all the dirty work is done by the lean custom entity classes.4) We still get to enjoy the benefits of Typed DataTables because of custom enties still contains those typed DataTables, but they are more leaner as the objects utilize _only_ the requried tables!

I will be posting a skeleton of how the above is done although most of you already get the idea!

Thursday, July 14, 2005

LoneStar Framework

LoneStar - which is the codename given to the project that i am working on is finally taking some shape. So after much sweat and blood, this is what is currently being formed in the new .net 2.0 application

UI Layer
UIPC Layer
can call either BusinessFacade or WebService(in case of distributed system) - read from Web.Config
Web-Service layer or BusinessFacade layer.
If Web-Service is called, the web-service will call BusinesFacade in turn.
BusinessFacade will call the BusinessComponents
The job of BusinessFacade is to orchestrate the processings. I am also planning to plug in a Business Rule Repository into the Facade.
BusinessComponents call the DAL
I have kept the DAL in such a way that it is configurable as to which DAL should be used, we have a SQLDAL and a OracleDAL.
And finally DAL talks to the database -> we have a Microsoft.ApplicationBlock.Data dll here which is temporarily being used to to data transactions(as the app is still not in any solid stage)
Typed DataSets are being used as the bloodline of the application, which makes the developers job much easier (yes i did example the pros and cons of typed datasets in .net 2.0 :) )

Sorry, Been quite busy and the didnt post much for the last couple of months..

This page is powered by Blogger. Isn't yours?

© Copyright 2005, Rohan Thomas
This Blog contains findings that are self-explored and expressions that are self-evoked. They are by no meanss representions of my employer's view.