其他

the growing heterogeneity of hardware architectures and diversity of operating system and communication platforms makes it hard to build correct, portable,efficient, and inexpensive applications from scratch.1. Library VS frameworkFrameworks are

【來自百度百科 】記憶體虛擬硬碟（ramdisk）是指通過軟體技術，將實體記憶體進行分割，將一部分記憶體通過虛擬技術轉變為硬碟以較大幅度提升電腦資料讀取速度和保護硬碟。【技術優勢】1、對於電腦系統來說，記憶體的讀取速度大約是硬碟的20倍，使用記憶體虛擬硬碟能夠快速有效地提高資料訪問速度。 　　2、傳統的機械硬碟經過長期的讀寫會出現壞道，而在使用過程中，IE快取檔案和系統快取檔案需要大量重複的讀寫資料，長時間使用會造成硬碟損壞。而記憶體並不存在此類隱患。

Gains:1. What will you do if you were not afraid? (如果你無所畏懼，你會怎麼做？)--------"Who moved my Cheese" 2. 馬上去做下一件事。3. 行動之前想得越多，害怕越多。 要三思，不要思太多-遍。4. 看下《窮爸爸，富爸爸》--平凡人要理財。5. When you move beyond your fear, you feel free.6. Keep positive about your future!

Configure to make a app run against the same dotNet FrameworkFor every app, if it has assemblies that are built based on dotNet framework, then it can have a app.exe.config file to support a application level configuration for its running behavior.

I recently met a issue that: when starting our app by command line way (passing several arguments to the app), on Win7, the specified file can always be opened after lanuching our app, while on XP, the file is always NOT able to be opened! The final

1. AnyCPUFirstly, there are 32bit/64bit CLR. For executables, it's up to the CPU bit to decide whether it will load as a 32/64bit process with corresponding CLR; for assembly, it's up to the process it's to be loaded into NOT the CPU or OS bit. 

Basic1. VS has only x32bit version, NO x64 version.2. DotNet Framework including basic library (System.*), CLR, JIT compiler, etc, have x32 and x64 version. For example, I have a C:\Windows\Microsoft.NET\Framework and a

We are developing a app called Fusion. It's a strange app, as: it's a MFC app while internally MFC app is just its clothes and it makes use of C++/CLI and mainly C# assemblies to do the real job. Its startup mechanism can be summarized as:1. Firstly,

1. For a native C++ project in VS, once you create resource.h + res file in the project, you can manually add resources (forget about the stupid resource editor!). By default, the resources will be embedded into the module. Usually, we create

CRT provides a set of debug routines for helping debugging issues. About assertion, it provides two:1. _ASSERT. This macro will only evaluate the expression and pop up diagnostic dialog if assert fails. It's only available when _DEBUG defined.2.

cmd.exe下可以乾的事情，bat都可以幹，並且批量。幾點常用：1.  批次檔的參數批次檔還可以像C語言的函數一樣使用參數（相當於DOS命令的命令列參數），這需要用到一個參數表示符"%"。%[1-9]表示參數，參數是指在運行批次檔時在檔案名稱後加的以空格（或者Tab）分隔的字串。變數可以從%0到%9，%0表示批處理命令本身，其它參數字串用%1到%9順序表示。 2. IF ERRORLEVELIF ERRORLEVEL

We are so used to adding dotNet module references and project references, but rarely meet situations requiring adding other dotnet module directly. The Other dotnet module consists of 3 kinds:    --precondition of installing my app. Like installing

軟體開發中的三類東西組合在一起成為一個軟體產品：應用程式架構（catalyst），眾多類庫（toolkit，ASM，OGS，AIRMAX），及兩者基礎上開發出的應用程式。

.net 支援三種檔案類型的resource：.txt　　.resx　　.resources system.resources 名字空間支援三種資源檔： .txt 檔案，只能有字串資源。因為不能被嵌入到 assembly 中，所以非常容易暴露，被客戶修改。最大缺點是僅支援字串資源，所以不推薦使用。 .resx 檔案，由 xml 組成，能加入所有資源，包括二進位。同樣不能被嵌入到 assembly 中。在 system.resources 名字空間中有專用讀寫的類。vs.net

碰到一個問題：需求是：對於同一個app，可以建立多個進程instance。如果一個進程instance已經啟動並正在使用一個temp file， 這個temp file作為進程間exclusive使用的資源，是不允許被其他這個app的進程instance所訪問的。方法：使用System.Threading.Mutex建立系統mutex--相當於進程層級的全域變數。In fixing。。。。。。。。。。。。。。。。。。。。。。。。。。。。學到的：The System.Threading

MSDN Returns a string array containing the command-line arguments for the current process. Input at the command lineResulting command line argumentsMyApp alpha betaMyApp, alpha, betaMyApp "alpha with spaces" "beta with spaces"MyApp, alpha with

1. API他有三種API（這裡不討論API所處層次的問題）：c++ API, COM API and .net wrapper API. COM API的存在是因為有些ACAD的東西比如classic menu等，只能用COM來訪問。2. 版本a. 每個版本的Autocad對應一個arx版本。保持一定程度的向下相容，比如AutoCAD2011可以支援用autocad2010 arx編寫的app，但是2010以下就不一定了。 b.

Gains:0. Dependency Management. By good dependency (dependency brings in coupling) management (interface-oriented, depend on abstraction, dependency injection, IOC, design pattern), we can restrict the dependency between two modules / classes the

一般來講，做任何task，都有一個必須的過程來總體上指導實現過程的有效進行：1. 瞭解清楚要做什麼。包括spec的基本把握（同樣的，第一步只需要總體把握+適當細節，不是全部細節的把握）。2. 怎麼做：    1）弄清楚相關的背景知識，專業知識，以及相關的代碼邏輯。這是開展工作的基礎。   

You can get Debugger Roadmap from MSDN to know everything about VS debugger.Exception Handling:There is a Exceptions dialog box in VS to configure how the debugger behaves with exceptions. In general, if there happended unhandled exceptions in your