outCodeCompileUnit.UserData("AllowLateBound") = False

Solution? A quick macro to remove all shapes from the sheet after I pasted:

Public Sub RemoveAllShapes()
    For Each e In Shapes
        e.Delete
    Next
End Sub

Plugins are certainly not a new concept by any stretch of the imagination, but what impressed me about TechSmith’s implementation is the installation process. Plugins aren’t normally a user-friendly concept because they usually involve putting files in special locations or doing special configuration.

TechSmith take away this complexity by registering a file extension (*.snagacc). These files are effectively a Zip file containing the DLLs and any dependencies of the plugin as well as a “manifest” containing information about the plugin. This file extension is registered to Snagit and the result is that simply double-clicking the *.snagacc file does all of the copying and configuration necessary for that plugin.

For more details and the workaround read:

http://blogs.msdn.com/vsto/archive/2009/05/07/issues-with-installing-vsto-projects-that-were-published-from-visual-studio-2008-on-windows-7-rc-saurabh-bhatia.aspx#comments

My basic advice to you is that you should only strive for a single exit point from your method when it aids in the readability and comprehensibility of that method, if it doesn’t then don’t get caught up in having a single exit point.

http://www.lostechies.com/blogs/chrismissal/archive/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern.aspx

Validating XML files against an XML Schema (XSD) has changed slightly in .NET Framework 3.5 because the XmlValidatingReader has been obsoleted as have XmlReader’s constructors. The correct way to validate an XML file now is to:

1. Create an XmlReaderSettings class, set the ValidationType to ValidationType.Schema, set the validation flags to report warnings, and add your schema to the Schemas collection.
2. Add a handler for the ValidationEventHandler event, unusually this event is raised from the XmlReaderSettings class not the XmlReader class.
3. Use the Create factory method on XmlReader passing in the path to the XML file and the XmlReaderSettings object you created above.
4. Iterate through all of the nodes in the XmlReader (validation is done as the reader processes each node).
5. Close the reader.
6. Remove the event handler.

Here is an example:

Dim settings As New XmlReaderSettings()
settings.ValidationType = ValidationType.Schema
settings.Schemas.Add("http://tempuri.org/MySchema.xsd", "MySchema.xsd"))
settings.ValidationFlags = XmlSchemaValidationFlags.ReportValidationWarnings

Try
    AddHandler settings.ValidationEventHandler, AddressOf ValidationEventHandler 

    Using reader As XmlReader = XmlReader.Create("MyInstance.xml", settings)
        While reader.Read()
        End While

        reader.Close()
    End Using
Finally
     RemoveHandler settings.ValidationEventHandler, AddressOf ValidationEventHandler
End Try

...

Private Sub ValidationEventHandler(ByVal sender As Object, ByVal e As ValidationEventArgs)
    ...
End Sub

One of the features of Unity is the ability to define type aliases that allow you to define the full type name once and then use an alias to refer to it elsewhere in the configuration. For example:

<unity>
    <typeAliases>
        <typeAlias alias="IClipboard"
            type="MyApplication.Services.Clipboard.IClipboard, MyApplication" />
    </typeAliases>
</unity>

While working through the examples in the hands-on labs it occurred to me that this is a good way of advertising the different dependencies that can be injected. By defining a type alias for each of the dependencies that can be injected (both mandatory and optional) then developers wanting to extend your application can easily see the available dependencies.

For example:

<unity>
    <typeAliases>
        <!--Mandatory-->
        <typeAlias alias="IClipboard"
            type="MyApplication.Services.Clipboard.IClipboard, MyApplication" />
        <typeAlias alias="IStore"
            type="MyApplication.Services.Store.IStore, MyApplication" />

        <!--Optional-->
        <typeAlias alias="ILogger"
            type="MyApplication.Services.Logger.ILogger, MyApplication" />
    </typeAliases>
</unity>

Whether one looks at the Custom Date and Time Format Strings used by things like DateTime.ToString(string) or the strings in GetDateFormat or the strings in GetTimeFormat, it is clear that some characters (like H and M) have specific meaning attached to the cased variants.

In my book, since only the lowercase y is used here, the uppercase behavior is undefined — if it works then have fun but you really shouldn’t; if it fails then you kind of asked for that failure….

And more importantly, if the meaning changes in the future then that is also something requested in the improper use. and the nature of H vs. h and M vs. m kind of underscores this.

After some searching I found the following knowledgebase article http://support.microsoft.com/kb/920201 which describes how to resolve the warning.