N
Newbie
Hi all,
Just want to comment on this thread.
Seems like every discussion about this matter (setting up DB provider for membership) and all the samples/references given by some MVPs always refering to LOCALHOST in their solution. Aren't they all forget that people build an ASP.NET appl are plans to host their appl in an commercial hosting provider, whom most of them can't afford the fancy of dedicated servers - most of them hosts on shared hosting, like me, so they just CAN'T touch or tweak or reconfigure the IIS, or run the aspnet_regsql.exe utility from within their Control Panel.
Anyone of you know - or even developed - of an ASP.NET 2.0 application, runs on the shared hosting, implemented .NET 2.0's built-in Authentication/authorization classes 'right-out-of-the-box' runs on the shared hosting? If so, that I might humbly
) request your advice please.
I built one. It works perfectly. Every thing just runs smoothly, the Login control, the new-user registration form, change password, login view, role management. Set up all my roles and authorizations with that handy 'Website Administration Tool'. I'm so happy. Man, I have to admit, I save a lot of tedious works of working with that security measures in ..NET 2.0 than I was using .NET 1.1.
Then come the time to upload all those hardwork to my production server, which is a shared hosting. And I just to face the real thing that it's not working just like on my development machine.
I then posted this issue on forums like this (where MVPs and ASP.NET hotshots gathers and give their valuable advice to novices and newbies like me...), never got a definite answer that pinpoint my error or ways how to solve the problem. Funny... coz those hotshots can answers and advices some more advanced topics/problems easily. but just passed out on my questions.
Just a little bit dissapointed though, but still got my hope because of all investments I made in this 6 months on this new technology.
It's just reminds me on how easy it is to do things like these with classic ASP and with tools like Dreamweaver MX. A TRULY Drag-and-drop development tool available that even VS2005 can't beat.
Regards,
Just want to comment on this thread.
Seems like every discussion about this matter (setting up DB provider for membership) and all the samples/references given by some MVPs always refering to LOCALHOST in their solution. Aren't they all forget that people build an ASP.NET appl are plans to host their appl in an commercial hosting provider, whom most of them can't afford the fancy of dedicated servers - most of them hosts on shared hosting, like me, so they just CAN'T touch or tweak or reconfigure the IIS, or run the aspnet_regsql.exe utility from within their Control Panel.
Anyone of you know - or even developed - of an ASP.NET 2.0 application, runs on the shared hosting, implemented .NET 2.0's built-in Authentication/authorization classes 'right-out-of-the-box' runs on the shared hosting? If so, that I might humbly
) request your advice please.I built one. It works perfectly. Every thing just runs smoothly, the Login control, the new-user registration form, change password, login view, role management. Set up all my roles and authorizations with that handy 'Website Administration Tool'. I'm so happy. Man, I have to admit, I save a lot of tedious works of working with that security measures in ..NET 2.0 than I was using .NET 1.1.
Then come the time to upload all those hardwork to my production server, which is a shared hosting. And I just to face the real thing that it's not working just like on my development machine.
I then posted this issue on forums like this (where MVPs and ASP.NET hotshots gathers and give their valuable advice to novices and newbies like me...), never got a definite answer that pinpoint my error or ways how to solve the problem. Funny... coz those hotshots can answers and advices some more advanced topics/problems easily. but just passed out on my questions.
Just a little bit dissapointed though, but still got my hope because of all investments I made in this 6 months on this new technology.
It's just reminds me on how easy it is to do things like these with classic ASP and with tools like Dreamweaver MX. A TRULY Drag-and-drop development tool available that even VS2005 can't beat.
Regards,