Yeah
>By assembly yuo mean it's own project?
>
>
>>One option: Put the class that you want to instantiate into a separate assembly. You could then fire it up using:
Assembly a = Assembly.Load("AssemblyName");
>>var x = a.CreateInstance("AssemblyName.ClassName");
Store the string representing AssemblyName.ClassName in the DB - parse out the assembly name for use in the first line.
>>
>>
>>
>>
>>>So is it possible to set this up at this point? So that I can use reflection?
>>>
>>>>Hi Viv,
>>>>
>>>>If you create a website without project files you do not get namespaces in the files. The aspx page will look like this:
>>>>
>>>>Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default"
>>>>
>>>>
>>>>And the class will look like this:
>>>>
>>>>sing System;
>>>>using System.Collections.Generic;
>>>>using System.Linq;
>>>>using System.Web;
>>>>using System.Web.UI;
>>>>using System.Web.UI.WebControls;
>>>>
>>>>public partial class _Default : System.Web.UI.Page
>>>>{
>>>> protected void Page_Load(object sender, EventArgs e)
>>>> {
>>>>
>>>> }
>>>>}
>>>>
>>>>
>>>>That said, there is a namespace involved but much more tricky to deal with. I am assuming based on Kevins response he has a file based website and no project. Anyone know what the namespace actually is? Paul?
>>>>Tim
>>>>
>>>>>>
>>>>>>I think so. It's an ASP.Net app and there are only 3 pages and the report. I thought I read somewhere that I needed to include
>>>>>>the namespace, but I don't see any namespaces in a web app.
>>>>>
>>>>>There's always a namespace (unless you deliberately removed it). In the ASPX page you can see it in the Inherits attribute of the Page. Or, of course, in rhe aspx.cs file......