Pragmatic Programmer

http://stackoverflow.com/questions/2757357/visual-studio-2010-recommended-extensions

Spire.Doc  :  도움말 It has many restrictions. It's not totally free. It's evil.

GhostDoc  : 유명한 코멘트 생성 헬퍼 http://www.atomineerutils.com/  : 자동 코멘트 생성 등등 VSdocman : 도움말 생성 프로그램 Doxygen  : 도움말 생성 프로그램(프리)

Content컨트롤에 템플릿을 로드시키면 실제로는 Content의 자식인 ContentPresenter에 할당이 된다. 따라서 먼저 VisualTreeHelper.GetChild(컨텐트, 0) 해서 찾자 ApplyTemplate() 해줘야 반영이 되는 경우가 있다. 컨텐트컨트롤.ContentTemplate.FindName("이름", 찾은 contentPresenter) 해서 찾자.

Setters.Add(new EventSetter(이벤트, 이벤트 핸들러); 이벤트핸들러는 new ......EVentHandler(메서드); 이렇게

The Component Object Model (COM) was Microsoft’s previous technology for building components. Many organizations have legacy COM objects that they need to use in their applications. A goal of COM was to ensure that different technologies could use one another’s components, and so a COM object written in VB 6 could be used from COM code written in C++—or at least that was the theory. The problem was that VB was not multithread aware and so internally made assumptions about which thread it was running on. C++ code could quite happily be multithreaded, and so by calling a VB component directly from a C++ one could potentially cause spectacular crashes. Therefore, thread-aware and thread-unaware code needed to be kept separate, and this was achieved by the notion of apartments. Thread-unaware components lived in Single Threaded Apartments (STAs), which would ensure they were always called on the same thread. Other components could elect to live in the Multithreaded Apartment (MTA ) or an...

http://msdn.microsoft.com/en-us/library/x13ttww7.aspx http://www.codeproject.com/Articles/31283/Volatile-fields-in-NET-A-look-inside 여러 스레드에 의해서 접근되는 경우에 사용. 그 이유는 JIT컴파일러가 옵티마이즈를 위해, 해당 필드를 cpu 캐시에 올려놓을 수 있기 때문이다.