I inherited a DNN 7 app, and they want a new column added to a custom table.  I am able to do that, but how do I get DNN to recognize the schema change?  

The custom module is just an .ascx page, and it is only used in this application.  There is no version per se in the manifest.

Do I do something to the SQLDataProvider?

Update the .xsd file somehow?

Add something to the "controller" file they've created?

I am basically trying to get DNN to recognize database changes that I've made manually.  I feel like there is something I need to "run" to get DNN to pick up the changes....kind of like update-database in Entity Framework.

Thank you for any insight you can give me.

Thank you for your quick reply.  

I wish they were using IHydratable.  It seems like even though this is DNN 7, none of the newer features are being used.  It's not the cleanest code I've seen, so I have had to stop thinking logically about anything I see....it's definitely a mashup.

Here is what I have determined....maybe someone will see something familiar.  Believe me, I have searched high and low for a simple answer (I have been coding for years).

User control (.ascx) saves a new "row" like this:

Instatiate:

EventsDataSet.u_EventsDataTable table = new EventsDataSet.u_EventsDataTable();

EventsDataSet.u_EventsRow row = table.Newu_EventsRow();

****

bunch fields to be saved

*** 

Then it calls this:

eventID = DataProvider.Instance().InsertEvent(row);

Which in turn accesses a DataProvider.cs, and the SQLDataProvider - both of which are in the App_Code folder. 

In hacking around, I was able to go into the .xsd file, which represented all the custom tables they've created.  Just for kicks, I added a new column.  I then went into the SQLDataProvider and manually added the field to the insert statement.

Somehow, this feels wrong.  At this point, I will take anything:  "Oh this is the way it used to be" or "Don't mess with stuff in the App_Code folder".    Even if you think it's vague - I might be able to search for something.

Btw, as far as the controller....one of the controller files does have a bunch of fields - like you would expect from a normal class.  The one that I'm working with does not.  

Yes, you are correct - this isn't a poster child for best practices.  I have been a .NET developer for a very long time, and datasets are definitely a blast from the past.  

I agree...I think I am just over thinking it....confusing what I think are DNN practices with just old crappy code.  There has been more than one occasion where I've said, why, why are they doing XXX this way?

Thanks!