Wiki
This website is a wiki. If you like and use our processes, techniques and tools, please add your experience and best practices. Just register and share.


Contents


User


Smart


Community

















Interpretation of analysis results

As you can see in the MoMA analysis results there are major issues in the MS Enterprise Library and log4net assemblies. However since the MS Ent lib EULA prohibits the use of the library on other operating systems except Windows, we have to figure out a workaround.Since these are pluggable components we have to do without on Mono.


For now the best strategy for the ADM project is to create the proof of concept with at least ADF components as possible. Given this strategy this results in a solution which uses the following components:
  • ADF.Autorization
  • ADF.Business
  • ADF.Core
  • ADF.Data
  • ADF.Database.SQL
  • ADF.Logging.Custom
  • ADF.Process
  • ADF.Web


    The only real issue with this minimal list of components is ADF.Core's dependency with ObjectBuilder, which is part of the MS EntLib. Another issue is whether or not the use of MS SQL server is acceptable for the PoC.


    Because we didn’t like the ObjectBuilder anyway, the solution will be to refactor the dependency with ObjectBuilder to a component of our own making. I guess we'll have step up the effort for this change request.


    With regard to SQL Server it's decided we leave this issue for now. Later on we'll see if we can refactor to MySQL to create a true open source solution.