[NaCl Addin] Fix building of libraries in MSVS

[NaCl Addin] Fix building of libraries in MSVS.

This also adds unit tests that build static and shared
libraries so this cannot happen again.

I've also added copyright header to all C# files.


BUG=

Committed: https://code.google.com/p/nativeclient-sdk/source/detail?r=1465

[Sam Clegg, 2012-11-06 23:02:43]

Clearly this points to a missing unit test.  I guess I'll do that now.

[noelallen1, 2012-11-07 00:20:55]

Removing a variable which the AddIn was not expecting for the Archiving step.

LGTM

[Sam Clegg, 2012-11-08 00:24:40]

Significantly changed patch.. now includes unit tests.

[binji, 2012-11-08 19:13:06]

lgtm w/ comments.

http://codereview.chromium.org/11360111/diff/6001/visual_studio/NativeClientV...
File visual_studio/NativeClientVSAddIn/NaCl.Build.CPPTasks/GCCUtilities.cs
(right):

http://codereview.chromium.org/11360111/diff/6001/visual_studio/NativeClientV...
visual_studio/NativeClientVSAddIn/NaCl.Build.CPPTasks/GCCUtilities.cs:15: ///
Untility functions for dealing with gcc toolchain on windows.
sp: Utility

http://codereview.chromium.org/11360111/diff/6001/visual_studio/NativeClientV...
File visual_studio/NativeClientVSAddIn/NaCl.Build.CPPTasks/NaClCompile.cs
(right):

http://codereview.chromium.org/11360111/diff/6001/visual_studio/NativeClientV...
visual_studio/NativeClientVSAddIn/NaCl.Build.CPPTasks/NaClCompile.cs:241: //
Remove rtti items as they are not relevant in C compilation and will produce
warnings
nit: wrap at 100

http://codereview.chromium.org/11360111/diff/6001/visual_studio/NativeClientV...
File visual_studio/NativeClientVSAddIn/UnitTests/CompileTest.cs (right):

http://codereview.chromium.org/11360111/diff/6001/visual_studio/NativeClientV...
visual_studio/NativeClientVSAddIn/UnitTests/CompileTest.cs:74:
TestUtilities.CleanUpVisualStudioInstance(dte_);
seems strange to have this here. Doesn't this get cleaned up in ClassTearDown?

http://codereview.chromium.org/11360111/diff/6001/visual_studio/NativeClientV...
visual_studio/NativeClientVSAddIn/UnitTests/CompileTest.cs:168:
SetProjectType("Executable", platform);
Is a pepper "executable" a shared library? If it is an actual executable then it
doesn't make much sense to try compiling this -- it can't be run.

http://codereview.chromium.org/11360111/diff/6001/visual_studio/NativeClientV...
File visual_studio/NativeClientVSAddIn/check_test_results.py (right):

http://codereview.chromium.org/11360111/diff/6001/visual_studio/NativeClientV...
visual_studio/NativeClientVSAddIn/check_test_results.py:50: elif exit_code:
exit_code is performing two functions: here it is used to determine if this test
failed...

http://codereview.chromium.org/11360111/diff/6001/visual_studio/NativeClientV...
visual_studio/NativeClientVSAddIn/check_test_results.py:53: return exit_code
here it is used to determine if any test failed.

Unless I've misunderstood this, you probably should use two variables.