I had actually seen your post before posting my question above. It does
not provide much in the way of tangible help. The connection string in
the post in incomplete; it worked after I added Server= to the
beginning, making it Server=./SQLEXPRESS (...) and removed the User
Instance=true param.
I have installed the VWD and SSE February CTP editions (.net 2.0.50110)
on a clean Win XP SP 2 machine. Both installed without a problem.
I am trying to implement the <a
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsse/html/VWD_SSE.asp">solution</a>
that Dan Burman outlines in his three part series on working with VWD
and SSE, the StudentActivities application.
When I go to the ASP.NET Configuration admin pages, there is no option
for AspNetSqlProvider that I can configure. If I choose the "use
different providers" option, I can see the AspNetSqlMembershipProvider
and AspNetSqlRoleProvider options, but clicking test fails.
I modified the LocalSqlServer key in the connectionStrings section of the machine.config to look like this
>add name="LocalSqlServer"
connectionString="Server=.\SQLEXPRESS;Integrated
Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;"
providerName="System.Data.SqlClient"/<
which generated a "SQLExpress database file auto-creation error"
message when I clicked the test link. Then I created the aspnetdb.mdf
file in my project's App_Data folder. After that the connection
succeeded in the admin tool. However, when I click on the security tab,
I get this error.
Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'
So, the question remains....
How do you configure VWD to use SSE as the membership data store?!? Is
the membership feature undergoing massive changes and I should not
bother with it right now?
Thanks,
Sam