.NET is late. But I finally think I should talk about the future of .NET. The reason is very simple, I now receive almost 50 emails. Net's future and other technologies, what is it? The advantage. So here, I will introduce my personal view of this technology future development. I will end from the expectations of the developer and end with the point of view of the company (software industrial enterprises). Ok! When a developer When starting to develop a software, he asking or need is: 1. Appropriate programming language knowledge to write business logic into procedures 2. Database knowledge to store his data 3. Connect business logic to the database in distributed environments Tool 4. Know how to pack applications 5. If you need to provide user transparency on the client, you need to develop Web Solution 6. I hope to get some components to multiplex the results of his hard work or other people's efficient solutions. 7. Hope Ability to complete the update client's task 8. I hope to be able to authorize a community to reuse your components to promote your business or work 9. I hope to provide a simple user interface 10. I hope to avoid building a one you have made There are still a lot of trouble for the web page ... (I can't include or discuss all aspects because all these things are different from those of the individual) but I think the 10 points mentioned above should be all serious developers. It is necessary to consider it. So, in terms of .Net arrival, we know that the solution to these issues is: ** Here I assume that you want to select one from the list of all possible options, I only choose one and I only The names of these popular technologies will be provided. 1. Appropriate programming language knowledge to write business logic: C, C , and Java.2. Database: Oracle, SOL Server, etc. 3. Connect business logic in distributed environments Tools to database components: CORBA, RMI, DCOM, etc. 4. Packaged for distribution applications: installer (independent), subsequent registration components 5. By (display) Provide online solutions: HTML, DHTML, CSS , And XML, etc. 6. I hope to use software reuse mechanism: Java Beans, COM, etc. 7. Client update: Java Script, JScript, Applets, etc., etc. Copy and registration components or access 9. Simple user interface: VB, VC , GTK and other 10. Reuse Web components: At present, there is no popular software in the industry, for example, I have developed for my development. Environment: C , SQL Server, DCOM, HTML, COM, JScript, ASP, Server, and Client Registration Utility, VC , GTK (On Linux) and XML. So what I encountered is that I need a long time to learn these technologies and almost every time I doubt whether these technologies can spread or can survive. I am not all Developers have to learn all the technologies, but they can be sure that if you want to design new and creative things, then you must have a good understanding of at least one of every point we discussed above. And people who do this are indeed the leader of this industry. But for .NET, Microsoft rely on several technologies with significant boundaries in a package. Means that you have all things but Will not confuse them. So if you start learning .NET, everything you need to learn is: Main technology: C # (VB.Net is also a good choice) ASP.NETXML. Only three ...... ............ Yes! C # can be used to write a client update script, create business logic, do server-side programming, write Windows applications, write console procedures, and make component design And it can use XML as data, metadata (self-descriptive data), connection tools between business logic, and database, but at the same time you need ADO.NET C # implementation, and further if you want to release something to Online, you need to install ASP.NET on the server side, if you want to create reusable web components, you need the concept of web services, just like VC
