Natty Gur

I wasn’t at work for couple of days (that flu … ). When I came back, one of the development team leader ask to consult me about the right pattern that matches his task. The guy is responsible for a module that responsible for getting request from inner system modules for outer system modules (actually dedicate products) and return the returned data from calling outer modules to the calling internal module. As part of it work, the module need to transform data back and forward from internal modules to outer modules.

After discussing models of data sharing across enterprise users we want to make some rules to distinguish between sector data versus shared data. First of all we want to define sector data. Actually our enterprise data split into information worlds. Each information world contains data that serve the needs of certain professional workers group and act as a part of that professional group business logic. Such professional group could be finance peoples, human resource peoples, marketing peoples and so on.

My family has been expanded two month ago so I don't have much time to deal with NWAF. in the last days I managed to go through the last (unread :-)) article that I wrote and to make it readable and hopefully understood. You can find it at : http://weblogs.asp.net/ngur/articles/168365.aspx.

If you use <OBJECT> tag to download assemblies and embed them into HTML document you should download and use SP 1 of .Net CLR. Due to a bug in mscorie.dll, this is part of the .Net download mechanism. It appears that sometimes certain or all assemblies simply not being download to the client. This behavior cause the user to work with unappeasable version of the software without any indication to the user that he is working with the wrong version or at least that something has been failed.

http://letitblog.com/epic/

Our Information architecture group has been discussed models for sharing enterprise data. The following lines summarize of our discussions.

 I’m working on asp.net page compilation for new webcast. As part of the work I found out that page compilation mechanism is using System.Web.RegularExpressions to parse ASPX file. Actually there are some useful regular expressions there for analysing page parts as well as certain HTML elements.  

One of our development teams summoned for open architecture day in our local MS office. MS want to present how they think certain project architecture should be. Well they don’t know nothing about our business architecture nor information architecture or project demands but they surly know what is the right architecture for certain project needs …ummmm  sounds fishy, so I gave up this experience.