Open Source with XAF?

Topics: Architecture
Sep 26, 2009 at 12:57 PM

Not understand the Open Source philosophy if we use a tool like XAF...

We should see the possibility of using some other as CSLA, Sculpture(in codeplex) , NHibernate, etc...
Sep 26, 2009 at 5:32 PM

Good Morning Carlos,

Emilio, Oscar, and Garth are having a Skype and SharedView session now and are answering together.

Our mission statement was intended to explain this.

We need a solution that works immediately.

To cobble together a functional solution with open source and standard MS technology would be a new undertaking that is outside of the scope of this project.

We encourage all of you that are interested to create a "sister" codeplex project with the goal in mind to create an evironment for all open source tools.

We are going to be more than happy to collaborate and share everything that we are doing.

However, to be clear, we are on a very short timeframe to accomplish the development of an open ERP using the existing XAF technology as an initial ERP solution for C# developers.

BTW:  We have friends that are very interested in developing OpenERP with an open source ERP with ASP.NET MVC technology.   Others are very interested in Silverlight.   Others are very interested in IronPython with Silverlight.   We would love to see all of these technologies advance to meet the needs of developers chosing these technologies.

Please let us know if you have further questions.

Sep 27, 2009 at 4:22 AM
I understand the need for speed... but with XAF a large community of programmers would be excluded, not everyone can buy a license of XAF ... of course, unless the project does not watch a large community of developers to support it.
it is perhaps a little more clear the scope and objectives of XERP.
Sep 27, 2009 at 7:16 PM

.NET Framework and XAF Helper

Currently engaged in design walk diagramming what may be the structure of XERP, that includes a lot of documentation ERP great deals and of course the software architecture.

An ERP project is complex enough to require that in my view are basically 3 types of fronts programming support.

  1. Core Developers;
  2. Extension Developer;
  3. Hard Users.


Core Developers

Encapsulate and remanufacture methods, properties, events and specific controls on DX, develop for developers.

As an example of this class programmer can start:

using DevExpress.Xpo;

using DevExpress. ExpressApp;

using DevExpress.Persistent.Base;

using DevExpress.Persistent.Base.General;

namespace XERP.Core.BusinessBase {

                                public class XerpAddress : BaseObject, IAddress {}}

Extension Developers

Partner License.

At this stage of the program that is used is the core built inside the box, helper extension, extension of the model at design time, runtime reports...

These extension modules are attached at runtime.

As an example of this class programmer can start:

using XERP.Extension;

using XERP.Extension.Helper;

using XERP.Extension.Controls;

using XERP.Core;

namespace MyXERP.BusinessExtension {

                                public class VerySpecificAddress : BusinessBase {}}

Hard User

Extended model, reports, reviews, attache different modules of extension developers commercial purpose (final goal) at runtime.