re: Software Programmer Professionalism

opejulgelaype — Mon, 23 Mar 2009 11:14:33 GMT

<a href=http://ertwerhsdzgnh.es>ertwerhsdzgnh.es</a>">http://ertwerhsdzgnh.es>ertwerhsdzgnh.es</a> not at any outdated <a href=http://ertwerhsdzgnh.es>ertwerhsdzgnh.es</a>">http://ertwerhsdzgnh.es>ertwerhsdzgnh.es</a> 959 http://ertwerhsdzgnh.es

re: Being as an Architect is not the same path with Project Management has

Miko Saeri — Wed, 05 Nov 2008 03:04:27 GMT

I know how you feel mate!

cheers

re: Software Engineering, bukan hanya Software Technologist...

buhe — Tue, 30 Sep 2008 04:07:58 GMT

tolong information Engineering itu apa tolong yah.......?

nya cari yah

Why mostly Software Projects are always late?

Novum Organum — Fri, 07 Mar 2008 09:14:47 GMT

In the middle of seclusion day, I'd like to write a good question to be thinked of. This article

re: How to publish a single dynamic service and utilize Generics

Wirawan — Mon, 25 Feb 2008 03:13:07 GMT

Wondering what brain do you have guru :D.

re: Summary Aggregate Entity to cater aggregate entity CRUD enhancement

adityapurwa — Mon, 24 Dec 2007 01:25:30 GMT

I have same problem in the past, when I should display a DataGrid with many columns from many tables inside it, therefore, I manipulate the DataGrid in its ItemDataBound event.

And then, I do the same thing just like you did, created one more entity which act just like a view in database-it aggregates many tables.

It works faster when binded to DataGrid's DataSource, because I'm not used ItemDataBound again to manipulate the Column's content.

Thanks God I have a time to start blog again | time management

Thanks God I have a time to start blog again | time management — Wed, 19 Dec 2007 03:09:26 GMT

Pingback from Thanks God I have a time to start blog again | time management

re: What is Novum Organum?

Arif.Budimartoyo — Mon, 21 Aug 2006 21:07:00 GMT

berani explore (terutama explore wanita) dan peranak pianak.... hehehehehe :P

re: Enjoy NEO (.NET Entity Object), the simple powerfull adaptable ORM for Agile development

Arif.Budimartoyo — Fri, 18 Aug 2006 13:26:00 GMT

Waduh papi bikin tambah mumet aja.... :D

re: Enjoy NEO (.NET Entity Object), the simple powerfull adaptable ORM for Agile development

Arif.Budimartoyo — Wed, 16 Aug 2006 17:16:00 GMT

1. You can use aggregate and calculation by iterating the ObjectListBase implementation. Otherwise, you can implement view then make it as table.

2. Make query from entity's responsible. Then you will have a Context responsibility. And do saving by always in the same Context. Ex: use PurchaseOrder.GetObject(POID), then from the instance objPurchaseOrder.GetPurchaseOrderDetailList() by using this.PurchaseOrderDetailRef as the Relation object then you get one Context to maintain Header /Detail entities.

3. You can use its entity's Context.DataSet to do serialization, otherwise you can build XML string from the collection then transfer it to the wire as data and schema as SOA implementation is to share the schema instead of classes.
I have been using Neo on Distributed apps. Rich client implementation and Transaction aware.

cheers,

re: Enjoy NEO (.NET Entity Object), the simple powerfull adaptable ORM for Agile development

Arif.Budimartoyo — Tue, 15 Aug 2006 20:50:00 GMT

I use NEO as well, but I have to say that I encounter some problem with it.

1. I can't find a way to do aggregate query (e.g.: sum, count, avg) in NEO. I wonder if we could? We have inssuficient resource available for NEO anyway.

2. I have difficulty in determining the best practice for its concept of ObjectContext. In its example, it uses one object context for whole application, which obviously won't work in real world. Uses many contexts in the application is even trickier. We cannot know exactly what entities are saved when we call entitiy.Context.SaveChanges();.. Moreover, uses multiple context can potentially cause runtime exception on executing following line: book.Author = author (if they are of different contexts, this causes exception)

3. I have difficulty in applying it in distributed environment. Each entity is a heavy data object which is not serializable. Worse, it contains ObjectContext which is clearly not a suitable object to share accross processes. I'm very interested if anyone has used NEO for distributed / client-server environment.

re: Yoyo theory of Software Engineering Road Map

Arif.Budimartoyo — Tue, 27 Jun 2006 04:30:00 GMT

re: Enjoy NEO (.NET Entity Object), the simple powerfull adaptable ORM for Agile development

Arif.Budimartoyo — Mon, 24 Apr 2006 19:25:00 GMT

Please find the sample code of Neo implementation here http://blogs.netindonesia.net/arif.budimartoyo/articles/9421.aspx

re: Enjoy NEO (.NET Entity Object), the simple powerfull adaptable ORM for Agile development

Arif.Budimartoyo — Wed, 19 Apr 2006 15:03:00 GMT

As the ADO.NET fully compatible, ofcourse NEO follow the raising of .NET 2.0 . The upcoming NEO2005 still in preview phase.
http://weblogs.asp.net/pgielens/archive/2006/04/15/443017.aspx .
There are a lot of adjustment in template generator to cover generics, partial classes, and nullable types.
And I believe there will be launched soon.

The Neo.Transaction was required before System.Transaction has been launched. And it just a add-on class and not being package in Neo source as it need while some dev required to implement MSMQ /Queing solution using Neo. It used declarative Transaction and implement COM+ support inside them. While actually we just need to place TransactionAware attribute to our class. The idea was taken from http://people.apache.org/~hammett/articles/dotnettransactions.html.
With System.Transaction, I believe all the problem will be covered better. Thats why Neo team didn't included Transaction in the 1.4 version.

Neo use Metadata Mapping as using the xml file of database representation (usually I generate this domain.xml using codesmith). And from this xml file, we use custom tool (NeoVsTool.dll) to make auto generation of all entity classes required (entitylist, entityfactory, entitybase, entitymap, entityrelation) while it saved.
No need of Reflection to create such objects as all of the classes are generated in the codeline.

re: Enjoy NEO (.NET Entity Object), the simple powerfull adaptable ORM for Agile development

Arif.Budimartoyo — Tue, 18 Apr 2006 23:36:00 GMT

Interesting.

Is it okay for .NET 2.0?
The Neo.Transaction, how is it compared to System.Transactions?
What Pattern Neo used? Data Mapper or Metadata Mapping? If it's Metadata Mapping, where's the metadata? XML file like NHibernate or Attribute like DLinq? or we just don't care just like DevExpress XPO?
Does it use Reflection?

He..he.. banyak tanya ya?

Novum Organum - All Comments

re: Software Programmer Professionalism

re: Being as an Architect is not the same path with Project Management has

re: Software Engineering, bukan hanya Software Technologist...

Why mostly Software Projects are always late?

re: How to publish a single dynamic service and utilize Generics

re: Summary Aggregate Entity to cater aggregate entity CRUD enhancement

Thanks God I have a time to start blog again | time management

re: What is Novum Organum?

re: Enjoy NEO (.NET Entity Object), the simple powerfull adaptable ORM for Agile development

re: Enjoy NEO (.NET Entity Object), the simple powerfull adaptable ORM for Agile development

re: Enjoy NEO (.NET Entity Object), the simple powerfull adaptable ORM for Agile development

re: Yoyo theory of Software Engineering Road Map

re: Enjoy NEO (.NET Entity Object), the simple powerfull adaptable ORM for Agile development

re: Enjoy NEO (.NET Entity Object), the simple powerfull adaptable ORM for Agile development

re: Enjoy NEO (.NET Entity Object), the simple powerfull adaptable ORM for Agile development