Native Client Visual Studio Add-in

visual_studio/NativeClientVSAddIn/NativeClientVSAddIn/AssemblyInfo.cs

Index: visual_studio/NativeClientVSAddIn/NativeClientVSAddIn/AssemblyInfo.cs
diff --git a/visual_studio/NativeClientVSAddIn/NativeClientVSAddIn/AssemblyInfo.cs b/visual_studio/NativeClientVSAddIn/NativeClientVSAddIn/AssemblyInfo.cs
new file mode 100644
index 0000000000000000000000000000000000000000..5d4bdac59d61c2065acafd56d0cc564a0bb2dcf5
--- /dev/null
+++ b/visual_studio/NativeClientVSAddIn/NativeClientVSAddIn/AssemblyInfo.cs
@@ -0,0 +1,35 @@
+// Copyright (c) 2012 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+using System.Reflection;
+using System.Runtime.CompilerServices;
+
+//
+// General Information about an assembly is controlled through the following
+// set of attributes. Change these attribute values to modify the information
+// associated with an assembly.
+//
+[assembly: AssemblyTitle("Native Client Visual Studio Add-in")]
+[assembly: AssemblyDescription("An add-in for Visual Studio aiding Native Client development")]
+[assembly: AssemblyConfiguration("")]
+[assembly: AssemblyCompany("")]
+[assembly: AssemblyProduct("")]

[elijahtaylor1, 2012/07/11 20:56:18]

Should we be filling in more information here?  If we're distributing as a
binary it might make sense.

[tysand, 2012/07/12 23:56:15]

Done.

+[assembly: AssemblyCopyright("")]

[noelallen1, 2012/07/11 22:16:46]

Add Copyright & Company?

[tysand, 2012/07/12 23:56:15]

Done.

+[assembly: AssemblyTrademark("")]
+[assembly: AssemblyCulture("")]
+
+//
+// Version information for an assembly consists of the following four values:
+//
+//    Major Version
+//    Minor Version
+//    Revision
+//    Build Number
+//
+// You can specify all the value or you can default the Revision and
+// Build Numbers by using the '*' as shown below:
+
+[assembly: AssemblyVersion("1.0.*")]

[noelallen1, 2012/07/11 22:16:46]

How do you plan to update this?

[tysand, 2012/07/12 23:56:15]

The Visual Studio functionality can be updated by replacing this dll. To
maintain backwards compatibility with project settings we can provide a utility
to update project settings from older versions. Versions of the Add-in need to
be backwards compatible with several versions of the SDK, as such I am
considering refactoring the code, for example, to have PluginDebuggerHelper as a
base class, and overriding functionality depending on the SDK version in classes
like PluginDebuggerHelperSDK22. Yay or nay?
On 2012/07/11 22:16:46, noelallen1 wrote:

+
+[assembly: System.Runtime.CompilerServices.InternalsVisibleTo("UnitTests")]