OMG: I appeared to have made a commitment to show how to build a dll in a previous blog and Angelina Jolie tells her story about DLLs
I am sorry, I made the statement:
Back to DLLs, a way to store your programming stuff. In one of the previous blogs, I talked about DLLs. Let’s examine how the DLL is referenced in the Visual Studio environment. To set a reference, in any of the Visual Studio tools you would use the reference and then right click it to add the DLL assembly reference to you IDE. To add the reference to a DLL, you would right click on the reference for the project (you can have more than one project in a solution), select “Add Reference”, another dialog box opens. One of the tabs you would select from the .NET tab, in the case of XNA, you might pick Microsoft.Xna.Framework.Pipeline, which isn’t selected by default when you start with building a new XNA project. The following are brief explanations of the tabs:
Lists all .NET Framework components available for referencing.
Either the full or "friendly" name of the component.
The version number of the component.
The version number of the .NET Framework that the component was created with.
The folder path and filename of the component.
Lists all COM components available for referencing. COM is a type of class library that has some added features and legacy features. COM is only used in Windows and not Windows Mobile or Windows CE.
Lists Visual Studio projects in the current solution available for referencing. Select assemblies from this tab to create project-to-project references. This tab is used if you wish to reference another project either that are in the IDE or in the Projects Folder, you have to navigate the folder to find the DLL
Displays the names of referenced projects.
Displays the folder path for referenced projects.
Allows you browse additional files to find a component not listed in the current tab and add it to the list.
Displays recently added references.
Next blog will discuss how to use these references in your code.