Tom,

I'm guessing that you have this assembly in the GAC already on your machine and are using an Imports or using statement in your code so that you can take advantage of its functionality. I'm thinking you shouldn't need to actually include this assembly with your module -- but.....

---------

If you need to package an assembly with your module so that when the module installs this assembly is placed in the bin folder.

To accomplish this you will need to:

• Modify your .dnn manifest file to include a section for your assembly
• Place the assembly in the "root" of your zip file

This is an example of including an assembly in your manifest file:

      <files>
        <file>
         <name>EngageModule.dll</name>
          </file>
        <file>
         <name>YourOtherAssembly.dll</name>
          </file>
        <file>
          <name>01.00.00.SqlDataProvider</name>
        </file>
        <file>
          <name>Uninstall.SqlDataProvider</name>
        </file>
      </files>

The Import Directive is for namespaces, not for individual classes.  <%@ Import Namespace="System.Web.UI" %> is more what you are looking for.  However, System.Web (the assembly that holds the class System.Web.UI.HtmlTextWriter) is used by DNN and all ASP.NET Webforms, and is definitely already installed.  Furthermore, it is also imported by default (see MSDN's documentation on the Import Directive).  So, it seems as though the problem that you are trying to solve isn't your real problem.

How are you trying to use the HtmlTextWriter?