DOTNET first Development Note

Copyright statement: original works can be reproduced. During reprinting, you must mark the original publication, author information, and this statement in hyperlink form. Otherwise, legal liability will be held. Http://blog.csdn.net/mayongzhan-ma yongzhan, myz, mayongzhan

DOTNET first Development Note

C # + sqlserver2000 application developed

The first is installation. The installation is painful. The installation is 2003. I wanted to install 2005.

Development is very simple. It is to create a form, drag controls, modify properties, and add events.

The code you may need to write yourself is the operation on the attributes of each object, the jump of the form and the database operation.

I encountered a lot of problems during development, but it was successfully completed with the help of reading books and online articles.

By the way, why don't I look at msdn... I really want to see it. But the msdn website does not have version 2003, and I have no installation files here.

I am deeply touched and summarized as follows:

1
It is very easy to drag controls to connect to the database, but it doesn't matter how they are connected, how they are encapsulated, and how they are operated.
It took the longest time to get involved. At last, I wrote in a book that I should first have a connection, then an adapter, and finally a dataset,
After these are all set up, we actually mainly use the DataSet object. The DOTNET object-oriented object is quite cruel, and almost everything is an object.
The most important one is to read data by fill (). If there is any change, update () is required ().
2
For conversions, it may be because C # Is a static language with a strong type. It is not very convenient for conversions of types. However, this also limits the occurrence of many inexplicable errors.
The most impressive thing is tostring (). It seems that all things have tostring, but a problem occurs during use. The result is a solution found on the Internet.
Smoothly converted the type.
3
Debugging: the perfect place for DOTNET is here. The debugging information is quite complete and accurate. Compared to debugging JS and PHP with alert () echo.
This is an increase from the age of cold weapons to the war of the universe. Efficiency and efficiency.
4
Compilation, fully automated. No parameters are provided. one-click generation directly. This is the favorite. MS has this advantage. This is called a programmer's behavior,
Programmers need to be lazy. To be lazy and manually compile the program, they have a sense of accomplishment.
5
Speed. The speed of DOTNET development is really satisfactory. In the past two days, I have never finished writing a management system. I can't trust my own capabilities.
It may take four or five days to develop the program in PHP. Besides, I have never used DOTNET to write formal things.
6
Documentation. Too full! Too many articles! It seems impossible to find a problem that no one has solved. That is to say, your current development work is repeating others' actions.
All the problems have been solved. I remember when I went to school, the teacher asked us to chat. Finally, I took the example in msdn directly.
7
The automation is too high. Some code is very spam. But the garbage is very beautiful. I really don't like the code that is useless. Maybe it takes too long to develop PHP.
I am very disgusted with the codecomon code. If I leave a blank line, it will feel inefficient. The most admirable thing is that the source code remains neat after numerous controls are dragged.
8
Execute the program. This may be a little worse, because there is a. netframework. I heard that there is a method that does not use. netframework. Feixin is the method used.
9
It is estimated that we will not be able to use DOTNET in the future. It is totally two worlds. DOTNET is too far away from me.