This step-by-step article describes what meta data assemblies are and in what scenarios you can use them. This article also explains how to use the Soapsuds tool with the nowrappedproxy flag to generate a meta data assembly.
The following list outlines the recommended hardware, software, network infrastructure, and service packs that you need:
- Visual Studio .NET
- Microsoft Internet Information Services (IIS)
This article assumes that you are familiar with the following topics:
- Visual Studio .NET
- Microsoft .NET Framework
- Microsoft .NET Remoting
What Are Meta Data Assemblies?
Meta data assemblies are .NET Framework assemblies that contain only meta data and type information. Meta data assemblies are similar to type libraries in COM, but meta data assemblies do not contain any implementation code.
Together with a distributed client application, you can deploy meta data assemblies that contain enough information for that client application to create a remote proxy and use that remote proxy to invoke methods on the actual assembly, which may reside on a different computer.
The following guide demonstrates how to generate a meta data assembly from a simple .NET-based component.
Create a Simple .NET Framework Component
- In Visual Studio. NET, on the File menu, click New, and then click Project. Under Project Types, click Visual C# Projects. Under Templates, click Class Library.
- Change the Name to MyRemoteComp, and then click OK.
The class library project is created. Class Class1 in the MyRemoteComp namespace is created in Class1.cs by default.
- Copy and paste the following code in Class1:
public string SayHello(string sName)
return "Hi, " + sName;
- On the Build menu, click Build Solution to build the class library. The assembly is named MyRemoteComp.dll.
Use the Soapsuds Tool to Generate the Meta Data Assembly
This section explains how to use the Soapsuds tool (Soapsuds.exe) and it's nowrappedproxy flag to create the meta data assembly. The simple assembly file that you created in the previous steps is used as input:
- On the Start menu, point to Programs, click Microsoft Visual Studio .NET, click Visual Studio .NET Tools, and then click Visual Studio .NET Command Prompt.
- At the Visual Studio .NET Command Prompt, change to the directory where you created your simple class library assembly. By default, the assembly is in the project\bin\debug directory. Type the command dir, and then note that assembly named MyRemoteComp.dll appears in the file list.
- Run the Soapsuds tool against your assembly. To do this, type the following command (as one command line) at the Visual Studio .NET Command Prompt:
You now have a second assembly .dll named Myremotecomp.metaonly.dll. This is the meta data assembly.
You can use this meta data assembly in remote client development and deployment. When you develop the remote client, add a reference to this meta data assembly instead of a reference to the assembly that contains the implementation code. If you are developing in Visual Studio .NET, follow these steps to add the reference:
- On the Project menu, click Add Reference.
- Click Browse, locate your meta data assembly, and then click Open.
Your assembly appears under Selected Components.
- Click OK.
You can now reference and use the class in your client code.
Alternative Use of -nowrappedproxy
You can use a meta data assembly after your clients are compiled, also. In this scenario, you must generate a meta data assembly file that has the same name as the original input assembly. To do this, run the Soapsuds tool by typing the following command (as one command line) at the Visual Studio .NET Command Prompt:
This command creates the new meta data assembly file in the directory project
\bin\debug\metaonly, and gives the new meta data assembly file the same name as the input assembly file. It is helpful to give this new file a meaningful name temporarily, while you are manipulating the file before deployment. When you deploy the new meta data assembly, change the name to the original name.
You can deploy this new assembly to remote clients that have already been compiled against the original input assembly. In this deployment configuration, when the client application loads the assembly, the client looks for the original assembly file by name, but the client finds the meta data assembly by the same name. The client requires only the meta data and type information that is contained in the assembly file to invoke the remote methods, so the meta data assembly is enough for this purpose.
- When you run the Soapsuds.exe command, verify that you do not include the .dll file name extension when you specify the input assembly file.
- You can abbreviate the Soapsuds.exe arguments, as described in the Microsoft Developer Network (MSDN) article that is listed in the "References" section.
- Be careful when you change the name of the output assembly file after it has been generated. As with any .NET Framework assembly, the name of the .dll file is a part of the meta data. An error will occur when the assembly is loaded if the name is different from the name that appears in the meta data.
For more information about the Soapsuds tool, visit the following MSDN Web site:
Soapsuds Tool (Soapsuds.exe)
For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
INFO: Configure .NET Remoting When the Remoting Client Is an ASP.NET Application or the Client Is Another Remoted Component That Is Hosted by IIS
Article ID: 323491 - Last Review: April 22, 2004 - Revision: 3.4
- Microsoft Visual Studio .NET 2003 Professional Edition
- Microsoft Visual Studio .NET 2002 Professional Edition
- Microsoft .NET Framework 1.1
- Microsoft .NET Framework 1.0