aspnet Membership table portability?

[glgcag1991]

I've created the ASP.NET Membership tables for my database on my dev server. I have two questions:

1. I am sending some of the ASP.NET development work to an outside consultant. I need to send him the complete database so he can create the web forms I need. Since the Membership setup creates so many tables and procs plus all my tables, what would be the best way to send the updated database to him every few days? (I'm using SQL Server 2005 Standard and he's using Express)

2. As I'm developing the architecture for the database, I'm building it by sections- periodically I need to delete all tables and run newer scripts to build the adjusted tables. Since I don't want to delete the membership tables, am I safe just deleting all tables except ones that start with 'aspnet%' in my proc?

Thanks for the help!

 

[markros]

1. One of the ways would be to send him a backup of the database.

2. Yes, I think deleting everything except aspnet should work (assuming you don't use custom profile).

PluralSight Learning Library

 

[glgcag1991]

Markros,

Thanks for the reply. I think you're right, I don't know how he will be able to develop without the complete Membership portion of the app. The more I think about it, I might be better off sharing my dev server with him instead. Shipping him backups will be a lot of work.

I'm not using a custom profile and in fact, I stay away from the aspnet tables altogether and create my own user tables that link to the aspnet tables. I'm too inexperienced yet to dig into them.

Thanks for the help!