I have setup dnn 4.9 locally on my pc running win xp pro sp3. It works fine and I am using the dnn 4.9 starter kit which installs the local app_data\database.mdf file. This setup is what I am using to develop dnn modules.

 

When I use codesmith to generate my dataprovider, sqldataprovider, controller, and info classes, it removes the aspnet local account completely from having access to the database.mdf file. It instead adds the sqlexpress local user account in its place.

 

I understand that this is necessary so codesmith can attach the database.mdf file and get at the tables, however, this then makes my dnn local portal not work since the aspnet local user account must have full privileges on the database.mdf file and it has been removed.

 

So, I run my codesmith templates, then manually go back and add the aspnet local user account to the database.mdf file and grant it full rights to the file so my dnn local portal will work.

 

This is cumbersome since I must repeat this process every time I need to generate codesmith classes or stored procedures. Does anyone know how to have this process of using codesmith and a local dnn 4.9 install work together so that the codesmith, or actually the sql server 2005 express local user, not remove the aspnet local account from the database file? In other words, is there a way to let them both have access to the database.mdf file without removing the aspnet local account?

 

When I close the database connection with vs 2005, and then open up sql studio manager express, it removes the aspnet local account from the database.mdf file so closing the connection from within vs 2005 doesn't seem to keep the aspnet local acount from being removed from the database.mdf file that sql studio manager express is removing. I still have to manually re-add the aspnet local account back on the database.mdf file every time I quit codesmith or sql server studio manager express. Any other ideas? Thanks!

Thanks for the follow up post. The real problem is using codesmith which is outside of the vs 2005 IDE. I am using codesmith dnn templates to generate my data access layer and my info/controller classes. Since I am using a local mdf database file, the only way I can get codesmith to log into the database is to attach it in my connection string. Once it is attached, I then can use the dnn codesmith templates. However, as previously mentioned, when attaching the database.mdf file in the codesmith connection string, it literally removes the aspnet local account from the file. By attaching the database.mdf file in teh codesmith connection string, codesmith completely strips the local aspnet account off the file and never puts it back once I exit codesmith. I then must manually go to the database.mdf file and re-apply the local aspnet account to it so my dnn local portal will run. Do you or anyone else happen to use codesmith on a local install of a dnn portal and using the database.mdf file? If yes, how are you able to get the local aspnet account to not be removed from the database.mdf file when you use codesmith outside of the vs 2005 IDE? btw I am using codesmith 2.6 to execute the dnn templates - I found the dnn templates referenced in the book professional DotNetNuke 4.