. Net is the future trend, why?

. NET has come a long way. But finally I think I should talk about the future of. Net. The reason is very simple, I now receive almost 50 emails every day inquiry. NET in the future and compared with other technologies, it has the advantages and so on. So here, I will present my personal views on the future development of this technology.

I will start with the expectations of the developers and end with the company (software industry Enterprise) perspective.

All right!

When a developer starts to develop a software, what he asks for or needs is:

1. Appropriate programming language knowledge to write business logic into a program
2. Database knowledge to store his data
3. Tools to connect business logic to a database in a distributed environment
4. Know how to package applications
5. If you need to provide user transparency on the client side, you need to develop a web solution
6. Want to get some components to use the results of his hard work or other people efficient solutions
7. Want to be able to complete the task of updating clients through scripting or server-side logic
8. Want to be able to authorize a group to reuse your components in order to promote your business or work
9. Want to provide a concise user interface
10. Want to avoid creating a Web page you have already done trouble

There are many more ... (I can't include or discuss all aspects because all of these things are actually different from one person to another.)

But I think the 10 points mentioned above should be considered by all serious developers. So technically, before. NET arrives, we know the solution to these problems is: * * Here I assume you want to select one from a list of all possible options and I will only provide the names of these pop technologies.

1. Appropriate programming language knowledge to write business logic into the program: C,c++, java.
2. Database: Oracle,sol Server and so on.
3. Tools for connecting business logic to database components in a distributed environment: CORBA, RMI, DCOM, etc.
4. Packaging for distribution applications: Setup (independent of environment), binaries, and then final registration of components
5. Provide online solutions via (display): HTML, DHTML, CSS, and XML.
6. Want to use software reuse mechanism: Java Beans, COM, etc.
7. Client update: Java Script, JScript, Applets, and server-side logic: Perl, ASP, PHP, etc.
8. Component release: Physical copy and registration component or full server access
9. Concise user interface: VB, VC + +, GTK, etc.
10. Reusable Web Components: At present, no popular software in industry has been used frequently.

For example, I have used for my development environment: C + +, SQL Server, DCOM, HTML, COM, JScript, ASP, server and client registration utilities, VC + + (on Linux) and XML. So the problem I have is that I need to spend a lot of time Time to learn these techniques and almost every time I doubt whether these technologies can be popularized or survive. I'm not saying that all developers have to learn all this technology all at once, but to be sure, If you want to design something new and creative then you have to have a good understanding of at least one of the points we discussed above and the people who do it are indeed the leaders of the industry.

But for. NET, Microsoft integrates almost everything in a software package with several distinct lines of technology. It means you have everything but you don't mix it up.

So if you start learning. NET, all you need to learn is:
Main technology: C # (VB. NET is also a good choice)
asp.net
XML.

There are only three kinds of .......... Oh, yes!

C # can be used to write client-update scripts, create business logic, do server-side programming, write Windows applications, write console programs, do component design, and it can use XML as data, metadata (self-describing data), business logic, and database connectivity tools, But at the same time you need to ado.net C # implementation, and further is if you want to publish things 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, like VC + + developed windows Services, but without physical limitations.

There is only one language that we can use in almost every place. No more confusion ... No, no, there's no com/dcom. The component registration process for system main memory is also without the authorization process on the system (except for some special cases).

So it's a high degree of success from a programmer's or developer's point of view.

Now let's think about it from the company's point of view (of course!). Here I'm talking about small companies that work as stand-alone projects. For example, a company recruited four VC + + programmers because their projects will be developed with VC + +, but in the next 6 months they have a project developed with VB.

What's going to happen now?

They will ask their developers to learn VB to start work, of course, another way is to fire them and recruit a group of VB developers!
So this is a major problem.

But for. NET, you don't need to learn a new one because of the excellent compatibility. NET language because you can introduce the components of one language into another. NET language.

So for. NET there is no need to convert your VB programmers into managed C + + programmers or convert C # programmers into JScript.NET programmers.