After a holiday, I went to 9CBS. I found the VC.NET version for the first time, because I have always been a .NET community (not arrogant, I don't understand), I saw a question asked about Vc.Net The articles of concern suddenly remembered that some people asked similar problems on the BBS of the school, suddenly wanted to say two sentences. So a very mad question, said some people's opinion, I hope to help the later people.
There is a concern about the transfer of VC6 to VS.NET, this kind of concern, I used to be. For example, I don't want to learn .net, then vc.net can be used in my C What about the program? If you learn vc.net, is it necessary to learn .NET? Many people have lost their confidence in the huge in front of .NET, still use VC6, still suffering from hundreds of Warning in the use of STL, VC6 turns to VC7, is it really so difficult?
You may see it, I don't use the name of Vc.Net like most people, but use VC7, although MS is called like this, because I think this is called ambiguity, maybe I should clarify a few concepts first:
.NET is a Framework provided by Microsoft. For this framework character, I don't dare to say, proficient. Net's prawn can tell me. Vs.Net is Visual Studio.NET, is an IDE provided by MS, which can edit the source of C , C #, Basic and other languages and compile. In fact, it is as if it is a representation, and it is not necessarily necessary to use. Net. C is a language, you can write it with a BCB, you can write with VC6 IDE, you can write it with VS.NET, and you can use Notepad, these have no relationship, because it is just a language, and the above It is a tool. VC7 is a C compiler with VS.Net (I am calling this first, there is no official saying), is the upgrade version of the VC6 compiler - of course it can compile the C source program with .NET managed code, that is Another thing - supports C standards and features powerful ancient Windows Framework MFC with MS. VC.NET is a C of .NET Framework, a variant of C , is an expansion of MS to C , there is a new keyword such as #using, __ gc, __property, so that C can use .NET Framework; It can be understood that a compiler is a specific C compiler that compiles C on the .NET Framework. Another one is our title for VC6, is VC6? Is it an IDE? Yes it is. Is VC6 a compiler? Also. VC6 is a version with an MFC class library, is it? It can also be considered this.
So you understand why I use VC7 without using VC.NET?
In this way, we can understand the transformation of VC6 to VC7 from several levels. These layers are in progress: IDE and the C language strict level (or compiler) level: This transition should be said to be VC6 to VS .NET's transition, just how to adapt to new IDEs and some subtle compilation differences, should not have any difficulty. On the MFC level: This shift is actually a big obstacle, due to the downward compatibility of the MFC, this level of obstacles is only a small change caused by the subtle compiler of the previous level and integration of MFC and IDE. Adaptation of the way, such as the disappearance of ClassWizard, etc., which is still easy to solve. Platform level: This shift is the most worrying, because only one framework can be used in VC6, it is MFC (or you think that ATL is also a framework), or you will use SDK naked to adjust the API, in fact they finally Win32 Platform; however, in the vs.net development environment, you can use SDK, you can use MFC, the most important thing is that a new platform is .NET Framework. If you decide to transform from Win32 to .NET Framework, then this will be a vast project, which may be a reason why everyone is looking for. So, which level are you worried?
From the situation I saw on 9CBS and BBS, many people don't know the difference between the three-layer transition, so I think that the transformation of the first two levels is intimidated by the third level, and then talk about .NET color change, It is done to .Net, keeping the VC6 to continue to do this.
In fact, this is no wonder that they are not used by vs.NET. It is impossible to understand that it is different from vc6ide, so it is better to use my energy today, soon someone suffer. ^ _ ^.
Sarrely, it is actually one meaning, don't think that the name is .NET is .NET, use Visual Studio .NET, you can write the driver, which can write C programs like you under VC6, use the STL library (and. NET supports STL's support better), you can use your MFC, you can write something you want to write ... Everything as long as one premise, as long as you don't have to #using, just like __gc, __property, etc. VC7 expansion .NET keyword, then the written program is not any relationship with .NET, what is it .NET.
Since we use VC6 to vs. VS.NET concerns on the .NET framework, what is the concerns about the VC7 and .NET frameworks, what is the concerns? This turn is the same as the VC5 turned to VC6. It is blamed, and it is blamed .Net, resulting in .NET abuse, everywhere, so everyone is inevitable ...
Moreover, VS.NET has more powerful and easy to use than VC6. Try how to break down in vs.net, see the vs.net class view, boldly install VS.NET, leaving only Visual when installing C , 400M hard drive, then the mouse is movable, you can create its interface as the interface you are familiar with, then run a cup of tea, Enjoy the New IDE and Enjoy the New Compiler!
