问题描述
我迁移我的asp.net MVC-3项目到Windows Azure。我有asp.net成员迁移到Windows Azure。我读这篇文章从这个ARTICAL我的理解是以下几点迁移成员：
I am migrating my asp.net mvc-3 project to windows azure. I have to migrate asp.net membership to windows azure. I read this article. From this artical what i understand is the following points to migrate membership :
1）迁移成员指只要改变其中user相关的信息存储在数据存储。手段我的情况下，我使用SQL Server EX $ P $ 2008 PSS作为一个片premises数据存储。我只是要chnage它SQL蔚蓝的数据中心。
1) Migrating membership means just changing the data store where user related information is stored. Means in my case i am using SQL server express 2008 as an on-premises data store. And i just have to chnage it to SQL azure data center.
2）我经历的NuGet下载ASP.NET通用提供商。这将自动扩展到SQL Azure中成员的支持。意味着我只需要更改连接字符串中file.In的连接字符串它需要服务器名称和数据库中的web.config。为此，我必须创建在Windows Azure账号。我在哪里可以创建数据库。并从那里我能得到我所要的只是我的web.config文件粘贴现成的连接字符串。
2) I downloaded ASP.NET Universal provider through Nuget. This will automatically extend the membership support to SQL azure. Means i just have to change the connection string in the web.config file.In that connection string it requires server-name and database. For this i have to create an account in the windows azure. Where i can create the database. And from there i can get the ready made connection string which i have to just paste in my web.config file.
和我想知道做这一切之后的下一个步骤。
And i want to know the next steps after doing all this.
我只是想知道我是否在正确的方向与否。如果有什么我失踪或者我不是在正确的道路上，那么请引导到正确的方向呢？谢谢
I Just want to know whether i am on the correct direction or not. If is there anything i am missing or i am not on the right path then please guide to the correct direction ? Thanks
推荐答案
在除了Sandrino的答案，我西港岛线只需添加一个建议使用的，因为它比ingrated在SSMS的功能要好得多。只是一个简单的〔实施例是，SQL Azure迁移向导将自动为不具有这样的表创建聚簇索引。另一件事是，迁移向导会给你详细的解释为任何非SQL Azure的兼容高清/数据/报表，而itegrated生成脚本，将只是把它是不兼容。
In addition to the Sandrino's answer, I wil just add a suggestion to use the SQL Azure Migration Wizard, as it is much better than the ingrated in SSMS functionality. Just a simple exmaple is that SQL Azure Migration Wizard will automatically create Clustered Indexes for tables which do not have such. Another thing is that the Migration wizard will give you detailed explanation for any non SQL Azure compatible definition/data/statement, while the itegrated "Generate Scripts" will just throw "it is not compatible"..
这篇关于迁移asp.net成员到Windows Azure的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！