CODEWITHSUNDEEP
asp.netazure
Cory
Cory

Reputation: 1283

Used ASP membership in past and now want to go to MS Azure and I don;t know where to start

I have a web form application (asp.net vb back) running membership and roles on SQl Server (hosted on godaddy). It works fine. Godaddy has an ASP.net schema option when setting up the SQL server, which was great for me using Visual Studio. The wizard set up membership and roles no problem (I code as a hobby and just learning). Now that the demands on the app are too much for Godaddy, I am looking at MS Azure; however, from what I read, Azure doesn't support classic asp membership/roles . I have found reference to custom scripts that can be installed, but those links are now broken e.g. like this one

My question is: If I were to start a new webform app that provides membership / roles via some sort of Visual Studio wizard, what type of project should I use? ASP.NET mvc3,4 ? Does this require great changes? Or, should I forget about a new type of project and just look at finding a SQL server host that is better than Godaddy but still supports classic asp schema?

Sorry for the basic nature of the question.

Upvotes: 0

Views: 74

Answers (1)

Scott Prokopetz
Scott Prokopetz

Reputation: 472

I'd recommend you look at Identity for your new membership system - it is Code-First so will work great for spinning up new instances without a complicated setup procedure. That being said, if you need to port your existing application to Azure you have two options:

  1. Run an Azure Virtual Machine and install your SQL database on it (using MS SQL Server, any flavor you choose, or MySQL or whatever your existing app uses) -- you can run your website on this VM as well or run the website using Azure Websites which would allow for easier scaling, etc.
  2. Use SQL Azure and convert the membership tables, stored procedures, etc. to run on SQL Azure. There are a number of significant changes that would have to be made based on differences between MS SQL and SQL Azure (and some limitations) but I have done this successfully for an older project (which I'm now refactoring to use Identity -- get the idea? Best to modernize the app to use a supported membership system)

Hope this helps.

Upvotes: 1

Related Questions