In the history of programming. Net, no other tool having a climb and fall so fast as noisy as the Dataset. Used as a emblematic item at the early .Net versions, was abused commercially as the solution to all problems of programmers to access and manipulate database. Big mistake, the obvious gap between the development team which created a powerful and versatile object, and the final link with the client (whether msdn or technet) which basically is the visible face to the community of developers and purely commercial court has completely clueless about the skills and dangers of its use. This component is the living example of such a great idea is misleading and manipulated in order to achieve sales, and their way of promotion is an easy way to badly stop the product.
Clearly, not all the fault of the seller, but many times the speed of the market and the decisions on the fly without knowing either the products they mistakenly used the tools. The big problem here is that he blamed the bad component of the publishing being generated or its poor implementation practice, and as the customer is always right, just goes to Microsoft for leaving out the playing field in this component with each new version of Visual Studio, and worse, the solutions are in place as Linq and Entity Data Model not only away from the road, but their benefits are not enough to cover or replace the possibilities offered by DataSet. I will comment on details of usage or best practices in use, and its comparison to highlight the major differences. I just hope to claim their profits before they disappear completely.

(tiny)

Anonymous access is configured during a web site creation  from SharePoint Administration site, which prepares the permissions in IIS.
However, access to lists and pages is restricted in many cases. So we must resort to stsadm command to leave ready access at least.
This is a behavior unwanted, but it was documented by Microsoft with the instructions of the case.
Obviously, the reason for this deficiency is that the product main target for use is under logon or authentication; which makes sense since its main consistent security of access and user management enviroment make it a too robust application to only create (or use their adapted features) with static sites with anonymous access.

(tiny)

The UML (Unified Modeling Language) has a number of extremely useful system tools, essential for any architect or information systems professional needs of application documenting requirements. “States machines” diagrams are part of its behavior modeling, and those who have more evolved from early versions up to the current version of UML 2.2 (-2/2/2009).

However, in the field of the administration-oriented applications generally based on electronic documents that change States primarily by interaction with users; a Machine States Diagram exceeds the possibilities of modeling and using a subset of items is enough to give a valuable contribution on designs. So let me define these basic guidelines of diagrams construction we can call “States diagrams” to differentiate them from his big brother “States machines chart”.

To do this we use the following basic elements, whose definition are exactly the same UML 2.2, and to which I refer to not extend this article:

• Initial state: black circle.
• Final State: concentric circle.
• Status: edges rounded rectangle.
• Transition: Unidirectional arrow.

The rules for chart it are detailed below:

Diagrama de Estados tipo

• A diagram applies only to an electronic document and absolutely contains all States which can passing.
• There is only an initial state and only one final by diagram and they are only “virtual”. This means that they do not correspond to real States themselves but are qualifiers of States directly attached to them .
• A State which only leave arrows fall outside any, are initial and are always connected to the initial state node(State 1 in the example) .
• A State which only reach arrows but doesn’t leave any, are final and are always connected to the final State node(State 3 and 4 State in the example) .
• Arrows are always drawing vertical and/or horizontal, avoiding the diagonal; provided that do not hard the reading of the diagram.
• Arrows that reach a State will do so by the top and the emerging will from the bottom; trying to prevent lateral fittings if no obstacle the reading of the diagram.
• States will always have a synthetic and representative name.
• Transitions can lead a name but it is not strictly necessary.

These elements and rules are very elemental, but this simplicity is its power; and that I will be explaining in successive post.

(tiny)

Those who treat with the information systems development area, repeatedly found difficulties to develop and deploy a system if either extremely transparent; but for some developers, and/or end-users, meet some difficulties that with a little investigating seems unexplained or quite unjustifiable, and in some cases arbitrary. Commonly it is designated as “resistance to change”, and there is a multitude of work relating to the scope of management dealing with it. But actually I should here like to bring another point of view that has application to this topic remembering philosopher Gaston Bachelard, “The formation of the scientific spirit” (year 1938).

In this book a concept raised since the first pages and becomes the centerline of the rest of the thesis is that referred to as “epistemological obstacle”. In all its chapters behind the idea that there are psychological barriers that lead people to generate themselves difficulties in advance of their understanding of new topics, sometimes based on personal opinion than the scientific reasoning, others by inertia to sustain known models trying everything necessarily adapted to them, and also by sociological features nearly bordering the costumes that fall simply in confusion, and disorientation vs. what is new.

In development groups I have seen in several ways this problem since information systems programming is purely creative cutting, and even if the computer class companies want to regulate their operation to decrease uncertainties, at least the task always lies with some creativity developers’s capacity. And there is showing these obstacles, which can simply be like “mind blank”, not knowing at the moment how to resolve a situation. The stress and always present deadlines compliance accentuated this sense of panic on the developer that feel impossible to resolve the problem, and no additional documentation is enough to help him. Moreover, within systems users is also highlighted this problem, especially if not properly accompanied the system development process. A system can resolve a business process to perfectly achieving the goals, but if the user feels somehow overtaken by the methodology acquisition of application using during training or already in a full operation of the system, can undermine the deployment in a somewhat tortuous process of adaptation. This is very common since the design decisions are agreed by managers and media directives, and the product arrives and imposes its final behaviour fully towards operating strata, which often are the main users of the system. The requirement of having to understand a new product, still rely on the willingness to address change, can also lead to a type of locking and feel that somehow the system is exceeding the effort that is logically expected in these processes; so finally suffers the mood and user patience.

In both cases, the task of training or “educational effort” which is attentive to this problem that arises naturally since the epistemological obstacle is inherent part of the process of investigation or knowledge acquisition; and to act in a non-confrontational way to help this it’s extremely important to evolve the different development and implementation processes actors of the new systems. Although you can expect the problem and on the basis of a task joint recognize it from operating costs and its managers, initiating a re-learning phase to have mechanisms to resolve itself and overcome these difficulties, generally organizations not covered these educational functions, then often derive the trouble task relying on other resources or taking more drastic action thereon if the situation is often repeated in an individual subject. In this regard, it is best that each team member be sufficiently prepared to detect this obstacle since the solution in such cases mainly begins by themself and this only be accomplished by timely and scheduled training. So far, and whereas the latter proposal may be utopian in the area of most organizations, I invite to individually study these theoretical aspects describing Bachelard so well in the book cited in paragraph 1.

(tiny)

Entity Framework

With the last version of Visual Studio 2008 libraries were incorporated to add LINQ and EDM (Entity Data Model) as part of the Framework 3.5 , which apparently offered a more specialized model to work entities. In fact both have classes and specializied namespaces in entities. More natural would seem to be working in these new frameworks, since generating and entities maintaining facilities strongly typed were resolved; knowing that uncomfortable work for n-tier is falling into the trap of creating and maintaining manually countless endless classes or data structures and methods for go translating them as they are moved from the database to the presentation layer; especially if handled messages instead of referenced libraries.

Well, LINQ and EDM not are the panacea of promised happiness. Unfortunately they are designed essentially to be applied on a single layer, strongly oriented objects; where the connection to a database context instance is permanently alive in application architectures. In fact, its internal logic points more injected by dynamic sql queries work which is not only inefficient on databases with medium or high weight, but it also disconnected from layered architecture scenario left obsolete or unnecessary already 70 % of its methods or objects; mostly devoted to direct consultations an instantiated context. And if you still want to keep these entities for ease of generation, binding controls and control changes or updates is extremely complicated since the internal state of the entities property is read-only, and is modified for use by the context, so those objects are not a support or reusable resource in offline mode.

Try to adapt this and other aspects of connection and transactional management leads to complement the entities by defining classes, partial or inherits, with properties and methods that becomes to a virtual DataSet. Therefore, the best tool for the time to create strongly typed entities remain datasets; or if you want to suffer a little more, but still preferred by lovers of the coupling by messages, helped by seralizables properties attributed xml-based classes.

(tiny)

In the technological world of computer applications, where products are guiding the superior training towards a utilization and ephemeral specialization techniques and languages that are obsolete insofar as these products are marketed, place the profession in information systems rescuing and doing grow the essences and principles which raised it as science is a balance which costs get. This problem is not proprietary within the computing, but are severely exacerbated by the fact that the systems engineering is one of the most recent engineering family branches.
Indeed, Ludwig von Bertalanffy the creator of the general theory of systems raised its foundations ‘ 40 decade mainly oriented biology, and spread quickly; as an ambitious susceptible model to be applied to any branch of science, which was somehow sneaking in areas as psychoanalysis or physics; and reaching especially form the basis of the information systems study. It came at the same time, their development pass simultaneously to emerging computing techniques that empowered it and affirmed in the recognized (and sometimes questioned) systems engineering and their computing derivatives. Compared to other disciplines, such as the civil engineering or architecture with hundreds of years of evolution, by the recent is relatively the weak and most susceptible strong amendments; especially since its development takes place at a time of corporatism that leads to research based and almost exclusively oriented succession of false exits and immediate short-term benefits. On the other hand, from other specialties are questioned  its foundations to each step that progresses, when not arise new pillars of creative methodologies that conflict between them, giving the impression of go forward on insecure steps.

The position of the Professional computer systems in this sense, must achieve a balance between the benefits expected to result of pursuit and keep the focus on go with the permanent evolution on the topics and foundations of the area in constant review. The task is not easy, but has in its favour precisely that to be the general theory of multidisciplinary application systems allows you to nurture the professional that handle his technique and language with experiences in other professional branches supporting their models in it. Enclose exclusively at the computer area, and especially in computing products, leads to a wrong way and leaves obsolete quickly the professional path. Nurture concepts and studies of seemingly unrelated to the professional responsibilities areas, but with the criterion and the implementation vision of systems and his general theory is significantly in the opening of concepts and give a management and vision context that ultimately will improve  the professional performance and your ability to make decisions better and more quickly-based on these new knowledge acquired.

The invitation is clear, as well as the theory of systems is considered interdisciplinary application, go with these experiences in the same way. This article inaugurates a special section of this blog, so-called philosophy and information systems, where I shall explain issues that will appear at a glance unrelated to the themes of programming and software; but are topics that enrich and facilitate professional duties in the most diverse areas tours and often where need of these services.

(tiny)

(this note refers to the SharePoint 2007 and SilverLight 2.0 versions).

Mount Sharepoint based web sites have the direct benefit of saving much time in the effort to develop a custom platform and with the management and security features that are resolved in this product. In a short time can have a standard looking site, and relatively adaptable to different needs

At the beginning of the new Millennium was installed strongly the concept of “digital identity ” increased significantly in recent years with the proliferation of social networks.” In fact, simple e-mails (type MSN, Yahoo! or Google) added elements of interaction and content that are converting messaging space in a social network like Facebook or Linked In style.

Within this universe, the digital generation has dump almost playing and keep up their virtual identity interchangeably linked to real life. Generations not digital native, as mine, still see with some distrust so easily dump data personal and professional, with a minimum in securing your data security trimming. For those who have some experience, we know that people databases are extremely valuable goods in the commercial field and organizations (both private as Government), and excessively costly for the difficult to achieve with updated data.

Under this context, I find too innocent to dump experiences, photos and personal data on such networks as free and virtually sacrificing any type of use rights; can and is used by proprietary companies social networking commercial law. But although the rise of the digital identity is pushing a little ordinary people to join in some way in this world for purposes not be excluded from market. In this regard the compromise which I find, solution can temporarily, is to open this blog where I keep certain information rights that I have, that is a little more protected than in a Facebook or Linked In.

Finally, welcome those who wish to learn more about my activities, or casually pass through here on the basis of timely questions.                                   

(tiny)