Move E Forum (http://www.dong-e.com/bbs)lg_netarea translation
The emergence of Borland's C # Builder means that vs.net has a real competitor. But what is the best for you to choose the development tool? As we understand, C # Builder is based on C # language, used to develop a full development environment of the .NET application. It released only a few months later than the Microsoft released VS.NET. Although both products are for the same customer (ie, C # first), they have the same development capabilities; however, they have their own characteristics. Since you have to choose one of them, then you want to know: What is the function of C # Builder? How is it compared to vs.net? Of course, why doesn't you choose this one without choosing another? Below we will answer these questions. From the surface, C # Builder and VS.NET are very similar. They are displayed to users are a source code editing window, visualization window, property menu, toolbar, project manager, and docking / sliding windows. C # bukder gives the first image of many developers is that it is very similar to vs.net. However, the first image is often a misleading. In fact, you will find that C # Builder has a lot of pleasure and practical value. The VS.NET interface is open when there is a label view on the editor and designer surface, which allows you to separate the edit window and move to the multi-document editor. However, C # Builder uses another method, that is, different interface layout types. The default mode is very like vs.net, but you can change it into a floating window type, which is a bit like JBuilder and Visual Basic. In addition, C # Builder also uses a special window when debugging. From the perspective of C # developers, these two IDE tools develop. There is no difference in development capabilities of Net applications. Because Borland gets the .NET Framework SDK license from Microsoft. That is to say, C # Builder and VS.NET use the same C # compiler and class library. You can use C # Builder to develop any .NET technology, including: Windows Forms, ASP.NET, and Web Services. The advantage of VS.NET is that it can be developed in a variety of languages, not just that C # Builder is limited to C # languages, including: C #, Visual Basic.NET, Managed C and J #. C # Builder is really possible to exist vb.net source code in the project, but it is only to provide a convenient additional feature for those who have encoded VB.NET to the project. Get code
Of course, those who have imagination designers and genius use two IDE tools to help them be more quickly developed, I do this. But the code editor is where I spend the most time. Both IDE tools have configurable language coloring and code indentation, but there is a key role in the formatting, annotations, positioning, and code generation / intelligence. When we test an IDE, the first thing to do is to type code. The code editor of the VS.NET has an automatic indentation that will indent a tab when starting the next statement. If the current state is indent, the VS.NET will rearrange the code in an appropriate manner when typing a block end tag. C # builder is not this, you need to use the Tab key; in addition, it will not be arranged automatically when the key is the end tag. Another format feature in VS.NET is that it can highlight a block and automatically format the entire block when you press CTRL K F. Maybe I will be confused by these formats, but I like this feature, it can improve my work efficiency. One of the biggest features of C # is its XML document comments, which have the corresponding priority in terms of document comments for files. VS.NET provides automatic support for XML document comments. You have to do it in what you need "///" ,vs.net can generate a module for document comments. For a multi-parameter, a return type method will be much better. VS.NET also provides a document generating tool for generating an XML document to make a HTML page. Another feature of VS.NET is to add a comment on the selected row while pressing Ctrl K C. Conversely Press and hold Ctrl K U to cancel the comment. In C # Builder's code editor, you must type all your comments without automatic comment / automatically cancel the comment. I am very happy to see C # Builder to let you skip a declaration, just like vs.net. However, they are different from the specific location of the code, and the VS.NET uses the object to check the window (Class View Window) to find the type and their members. The C # Builder uses the prototype view window to achieve a similar function. Members list box (automatically appearing during code editing) This feature is not in C # Builder, but I am often used in vs.net, which allows you to point directly to the members you want. C # Builder and VS.NET include a sensitive context-sensitive help feature in the editor, but they have a subtle difference. In VS.NET, Context-Sensitive helps are called IntelliSense, while in C # Builder called Code Completion. When we select a method from the list, IntelliSense contains a method description, and C # Builder only lists its members. In addition, IntelliSense is designed very well, so that you remember that you use the most frequent options and highlight when you appear. Although the Code Completion is not designed so clever, it can also filter out the relevant options in the list box. Additional features include: supporting new keywords, automatic execution of interfaces, automatic delegate execution, and automatic overlay execution, etc. are not in the code completion. details
Project management in C # Builder and VS.NET can complete the same goal, but their way is different. C # Builder's Item Management window lets you directly control the compile command, but the VS.NET program manager has a respective dialog where you can specify the compile command. The main difference in basic principles is that if you create a project between the two items, the vs.net will automatically determine the compile command and the dependency. But C # Builder will let you maintain your own compilation command. In fact, I know that in vs.net, it will stop your project development, that is why you use project reference and let VS.NET to classify those things. Since C # Builder is just coming out, it takes time to see if people have problems with project management. In this part I have considered some of C # Builder, but also have some experiments, but I still have to have these issues. Both IDE provide a finished help; you can get it only by f1. The help of C # Builder is from a separate window, and the help of VS.NET appears in the IDE window (which also includes dynamic help). Fortunately, if you don't want to see dynamic help you close it, or hide behind other windows. For designers, C # Builder uses a design interface similar to the vs.net, so you have similar feelings for visual user interface. Similarly, the object inspector of C # Builder is also an improved property grid that has been improved .NET Framework base library (Property Grid). For both, the design interface differs in the toolbar of C # Builder, which is similar to the toolbox of VS.NET. The configurable classification list is listed in the toolbar, and you can change the appearance of color, commands, and options in this list. VS.NET controls in a possible sliding list box, in the code editing mode, the toolbar displays a list of lists, which is usually often used. VS.NET has a clipboard ring that contains the most common copy code. It is not this for C # Builder, it is lasting, and the content in the vs.net will not exist as it is closed. In addition, C # Builder's toolbar has a search bar, which can be filtered according to the control names you typed. When you open a file, VS.NET opens a new window for each file. When you work in a multi-file, your workspace will soon be accounted for, this is a very annoying thing. Its forms and code are also separated, which makes you have to look at the interface to find the corresponding code. In C # Builder, the form and code are organized together, and you use the label for easy replacement in the bottom of the workspace. Another good feature is that the shutdown button of each workspace window is just a single, and the vs.net needs you to find the label, select it, then click the shutdown button in the upper right corner of the work area. In addition to SQK Server, Oracle, OLEDB, and ODBC supported in .NET Framework, C # Builder also supports Borland Data Provider (BDP). DBP is an extensible data provider that allows you to connect to a variety of databases using the same code. Current database support includes: Borland Interbase, IBM DB2, Microsoft SQL Server, and Oracle 9i. When completing this article, Borland is increasing support for many new databases, in which it is in the foreseeable future, it will continue to do so. VS.NET and C # Builder have code browsers to use the relationship between the individual.
But C # Builder's professional and higher also include an application chart called Model View. It is a basic standard UML chart that allows you to view the relationship between the applications, thereby further viewing their content, but also navigate between modes and code. Although these are just viewing features, it is best to help you put an app with an app. And vs.net has no such function. Finally, the Modeling Technology of UML is introduced in the IDE in C # Builder, which provides a function of design, namely: developer and modeling can create a UML model, and its code is also updated. Similarly, the change in code will also immediately cause a change in the UML model. There is no internal model conversion and descriptions to have a direct interaction between the code and the model. Another exciting is that C # Builder modeling is the core object of the company, or ECO (Pronounced Eek0). ECO is a target that can be modeled at runtime, which is the goal pursued by Object Management Group MDA (Model Driver Architecture). With ECO, you can create a new model or import an XML model that already exists from other modeling tools. The main features of Eco include: support for durability, data processing, security, and data binding. The ECO model can also adapt to changes arising from the database plan. VS.NET does not provide this feature. Lifecycle management
Borland first named Application Cycle Management (ALM), containing this management tool into our project, we can coordinate our work. ALM is divided into six clear phases, including: Define, Design, Development, Test (DEPLOY), and Manage. The importance of ALM is: integration and interoperability of tool collection in the environment of C # Builder. For example: CaliberRM (tools for defining phase demand management) is directly integrated into C # Builder to connect users directly with the developer. ALM did not specify a specific methodology, but it describes a way to support flexible processes. VS.NET can be integrated with other Microsoft technology. If the third party seller gets VSIP (Visual Studio.Net Integration Program), they can also integrate. Microsoft specifies the MSF (Microsoft Solutions Framework), but it does not have a process and wizard program in VS.NET to create a process like ALM. In this article, I also involved many aspects, but I chose the most important issue I think. C # Builder and VS.NET are very excellent tools in the various .NET applications you want to develop, and different points are only the code you created. For editing code, I like the source code editor of vs.net. But from a development team, for the entire development cycle, C # Builder is much better in terms of integrity and effectiveness of tools. My personal point is to enjoy Borland into the .NET stage, and hope that C # Builder has more innovations in the future version. In the .NET stage competition, there is no doubt that C # Builder and VS.NET will have more surprising, and these aspects are in order to improve the development efficiency of developers. (Finish)
