Nope...this is the way to go...we will be adding the import support for views, etc. later on.  This is on the enhancement requests list.

Yes, it is supported.  There is a topic in the help about this...you have to logon by manually calling the AuthenticateUser() method, etc...but you can use it there.

It is really up to you which direction to go...you would be a better candidate of determining which avenue would be suite your needs.

Oops this belongs in WebForms.



Also, I am not using SF security Module for two reasons.



1) Is it even supported in webforms (websites) ?



2) I am somewhat familiar already with the membership/role based stuff in .NET and need to make immediate progress with the project. I haven't had time to familiarize myself with SF Security yet even tho we purchased it.



Thanks.

Keith Chisarik

First of many questions I am sure.



I am adding the security tables required to use ASP.NET 2.0's membership API to a database using aspnet_regsql.exe.



I then used the import function (SQL Server) in DDT to import these tables along with my database, it gets the tables but not the views or stored procs (of which there are about 45). So of course when I deploy it blows off all that good stuff I need for my app.



So here is the rub, I want to use DDT for my web applications (website) database. My thought is that I will manually add the views and stored procs to the metadata and then be able to use the DDT exclusively from that point on. I can just use SQL Management Studio's "CREATE TO" functions to get the stored procs and view definitions.



Do you guys see any issue with this? It will be a decent amount of work up front, but then I am centralized and able to use both ASP.NET role/membership based security and Strataframe. That is my thinking.

Keith Chisarik