How will. Net affect us? (2)

How does Microsoft. NET affect our way of doing things?

There will be no impact. Currently. NET is a prospect, not a reality. However, if everything is as planned, it will have potential impact on three types of people: users, network administrators, and developers.

Microsoft has a lot to say about the benefits that users can get .. . NET applications tend to provide a unified interface for users to browse, edit, and create documents from an application. This data model should allow the application to have the ability to query data from different sources and merge the data into a visual document. Users will be able to access their applications and personal settings from any device through a compatible browser. Working in the corner of a coffee shop will be the same as working at home ;-)

The flexible platform means that user data is automatically adjusted according to their working environment: In the Desktop client and smaller browser of the handheld PC, the same data will be displayed in different ways.

What does this mode bring to network administrators? It is estimated that. NET applications will be loaded into their own directories and remain independent of each other. This will produce two results. First, the DLL trap will be terminated following the "share data rather than code" model agreed by Microsoft. Thus, different applications may overwrite the Helper library with the same name. Second, it is estimated that the application will not "Trigger" the registry, thus solving the Registry "tattoo" problem: even if the application is not installed, it still leaves configuration information in the registry. In addition,. NET applications use Kerberos-based security mechanisms to ensure that only authorized users can access user data.

. NET applications will be centrally installed at the same time, which reduces the management of re-installing their clients when programs are lost. It is expected that. NET applications can monitor their own memory vulnerabilities. How bad is the memory vulnerability in a single user environment. If we move to a server-based computing environment that provides services for many people, they will be fatal.

. NET and developers

For developers,. NET makes it possible for them to create applications in the language they are most familiar with and query information from heterogeneous data sources. Developers do not have to trade in different programming modes from the COM Object to the DLL, or use different debugging tools, or write installation packages for. NET applications. In the near future, developers will be able to write applications in the language they want to use, create the support files required by the application, and enable it to run.

. NET will not mature soon. Browsers require reliable XML analyzer, and servers need to convert raw data into XML engines. Data not formatted in XML format cannot be provided to applications. Inertia will make it difficult for a large number of existing Windows applications to completely disappear overnight. Until 2001, before the Whistler system was completed, the first part of the client operating system that supports. NET would not appear. In addition, it will not be fully implemented until the Blackcomb system is listed. DataCenter will also take effect for a long time.

Some developers pointed out that Java, as an example of good ideas, is not flying, but Microsoft is different, and she has a wealth of market energy. Although they are not invincible, they are excellent. Remember: when Windows appears, no one needs it.