“Managed code” is one of the most important progresses between .Net Framework and VC++. Althouth you can know about how efficiency and how productivity the “managed code” is. but how to proof the efficiency and productivity? How efficiency? In this link, Brad Abrams and Anders Hejlsberg describe the importance of Managed Code. They are taking about lots pregress in managed code, for example: gabage collection, buffer over flow even more you don’t have to write addtional destructor for a object, because GC (gabage collection) will help you to automatically destroy this object. What’s different between Managed code and Native code? **The most different between managed code and unmanaged (native) code is “Managed extension”. Use managed extension is not a easy thing for me, you can refer Richard Grimes’s article in Visual C++ magazine “Feel at Home with Managed Extensions**” (mm.. I think maybe this article can not find in WWW just...
學習新的語言,一直是身為軟體工程師不可躲避的宿命與責任。而微軟的C#,更是身為視窗系統研發的我們,必須學習的一個新技術。最近除了學習將VisualStudio的Porting之外,C#應該是讓我們進入.Net Framework 最快路徑。這裡提供幾個鏈結關於C#:
C# Station: Introduction to the C# Tutorial
A Quick view from C/C++ to C#
Patrick也在這篇文章中提到Applied Microsoft .Net framework programming這本書,也是一本利用C#來了解.Net Framework ,是本不可缺少的好書~~
Patrick’s Article is talking about bug reporting best proctice. Somehow in the such big project like Visual Studio .NET IDE. They usually MedDog to do testing case management. A good and sysmantic testing case can find bug more easier.
There are some link about:
Introduction to DevDiv’s Test Case Management System
Investigating a test case failure in the lab
_Analyzing a Test Case Failure _
_Finding and Logging a Bug _
You can find other link in vs2005news’s WebLog and Got Dot Net can find some useful information. About ASP .NET you can reference this document to find more information.
Naming is alway difficult thing for me. But when look the speech which Brad Abrams talking about naming convension, I think he provide more detail situation what we have to do when we need naming our variables. Some interesting about this speech as bellow: “Google test”: he just talk about avoid abbreviation. He say you can use google to test the abbrebiation. About casing rule: Just use camelCase in parameter naming,otherwise use PascalCase. (I think this rule give me some help) Do not use underscore: Do not use it when naming. Just like Some_Variable~~ Don’t use Hungarian Notation: Brad Abrams also talk about although Hungarian Notation is usefull in the past, but according the IDE progress more and more. Microsoft already ban their engineer using Hungarian Notation. So~~ in the public API do not use it, just use it in your function implementation(if you still want to use it). There still have...