What is a neutral building?
In computer programming and computer engineering, the neutral assembly of an application that has been compiled from the source code components in a system that contains none of the tools, libraries or other development software that has been used to create a program. The purpose of the neutral assembly is to ensure that the program can work so that it is written without errors resulting from the source code problems that can be uninvited in the development environment. This term can also refer to software that has been compiled in a way, so it does not fit on any particular hardware or proprietary library and is therefore considered neutral in terms of development. Many programming projects create neutral reports - sometimes called night assemblies - a regular project to ensure that there are no major defects at any moment - such as missing files or contradictory configurations - in the current program assembly process.
one of the reasons for the neutral assembly has to do inDoing as some software evolves. In general, computers used to write the application have installed a large number of development software such as integrated development environment (IDE), programming libraries and special hardware or other software interfaces. These development tools are sometimes integrated in a way that causes them transparent during software development. If the software is ready for compilation for use in the system without development, it must be dependent on which application has to explicitly define in terms of development tools so that the program can assemble and run on the neutral system correctly. This is known as a neutral building.
neutral assembly often takes place on a neutral computer or server or in a neutral application space. This means that none of the development tools is present and there is no implicit integration techno, for example, a programming library, is used during development. Creating a program on a clean system meansthat the program can be consistently compiled in its current state and that the finished executable program can be distributed and carried out on systems without development.
6 This may be a problem when the team is working on a project in which some files are updated, some are omitted and some are never registered as modified as part of the development. The neutral assembly also removes the possibility that pre -compiled source files are used again instead of using newly compiled files, as can occur on the development system. Creating neutral assemblies ultimately is more about ensuring that the program can successfully complete the assembly process rather than isolation of logical or function errors.