I think I know the answer to this, but as I'm working through publishing the ContactManager sample MVC app, I keep getting the error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) Do I have to modify connection strings to use a "real" SQL server? or can I just publish my SQL .mdf files directly to DASP? Is there another option? To be really clear, this error occurs when I attempt to register a new user on the Account page. thanks! /mark
Yes. If you are referring to dropping the .mdf file into a directory and telling the application to access it there, no, that will not work.
Yea, sounds like you're trying to use SQL Express which is not supported in our hosting environment. Make sure you're using the SQL Server addon.
follow-up question... MVC role providers makes sense. Is there some way to hook the out-of-the-box MVC user/role membership framework with DASP or do I aim that at a SQL addon also? That is, I think the username/password/roles information is kept in another mdf file. There must be somewhere to configure that connection string also. unless it's kept elsewhere or can be modified to leverage the username/roles stuff in IIS6?
