So I can't quite understand what's going on here... I've watched the video tutorial on ASP.NET about creating and securing my site using Membership (configuring roles and users), and I noticed that it creates a database in my App_Data folder (ASPNETDB, I think it's called). And I've got all that working on my local machine, but I'm confused as to how to move it to my server.
My hosting provider is M6.net, and they've told me that if I want to upload a database to their server, I have to create it using my admin panel, then upload the file and they'll fill it in for me. My question is this: if I give them the database that's automatically created when I use login controls on my website LOCALLY, will that database still provide the correct membership functionality for my website when it's run from the web server? Such that I can give them (M6) the ASPNETDB (containing all the usernames/passwords/rules? I've already specified for my local site), have them populate the similarly titled database on the server, and have it still work with my pages?
I'm also confused as to why that database doesn't have a connection string specified in the web.config file...can anyone shed some light on that?
As I have no direct access to the database server on my hosting provider, I need to create the membership database with all the correct details prior to uploading it to my server - if simply using the locally generated copy won't work, what should I do?
Lastly, the video tutorial says to go to the ASP.NET Configuration page to manage users, roles, security settings, etc., but I don't seem to have access to that through M6. Instead, I have access to a FrontPage configuration page that is strikingly similar in content to that ASP.NET Configuration page featured in the video, in that it also allows user and role management capability - is this the same thing under a different guise?
Hi the ev,
My hosting provider is M6.net, and they've told me that if I want to upload a database to their server, I have to create it using my admin panel, then upload the file and they'll fill it in for me. My question is this: if I give them the database that's automatically created when I use login controls on my website LOCALLY, will that database still provide the correct membership functionality for my website when it's run from the web server? Such that I can give them (M6) the ASPNETDB (containing all the usernames/passwords/rules? I've already specified for my local site), have them populate the similarly titled database on the server, and have it still work with my pages?
the ev:
What format's they'll accept it in will be up to them. To be sure you should probably provide them a script instead of a database as it will guarantee they can use it. You can generate the script within Management Studio or by using something like thedatabase publishing wizard.aspnet_regsql.exe also has a command line switch to generate the statements required to setup the database but won't include your data.
I'm also confused as to why that database doesn't have a connection string specified in the web.config file...can anyone shed some light on that?
If you don't define the providers in your web.config the defaults will be used, which includes trying to use an sql instance running out of your app_data folder. This will need to be changed to work on your hosted platform. You'll need to specify a connection string matching what M6 tell you to use and setup the providers to use that. Seehere for an example of configuring membership in your web.config.
To make use of the existing information you'll have to make sure your applicationName in the config file matches, I believe it defaults to "/".
Lastly, the video tutorial says to go to the ASP.NET Configuration page to manage users, roles, security settings, etc., but I don't seem to have access to that through M6. Instead, I have access to a FrontPage configuration page that is strikingly similar in content to that ASP.NET Configuration page featured in the video, in that it also allows user and role management capability - is this the same thing under a different guise?
I doubt it. I have always steered clear of Frontpage so I can't say for sure, but I'd assume this is going to manage permissions at the Webserver level and won't interact with your membership provider.
To provide some sort of user/role management after it's been deployed to your host you'll have to implement it yourself. There's atwopart article on doing just that which you may find interesting.
I hope that helps.
||| Thanks for the reply! I'm checking out what you wrote now and will report back later! :)
Its funny -- your questions seem very familar to me--
I find MS's way of handleing these things to be perplexing and scary all at the same time - so far i have not been able to get a membership DB to work on a server.
To be honest I don't really see how the thing works at all. Farther I love the tools that make my life easier but there is something fairly Freaky about giving anything this much controll of the development process. Granted theres no need to re-invent the wheel but why the hell is the wheel so inflexable you'd think you would be able to mount it onto anything and have a wheel that works...
Yet microsoft shrouds fundimental things such as this in total mistery...
Maybe im missing the ahh-hah moment here but if you've ever developed in Linux or with any other DB platform you'd know that getting to the db is stored some place and connected to with a db account. Why complicated with attaching, local file permissions and membership 'provider' voodoo?
</rant>
No comments:
Post a Comment