Monday, July 5, 2010

An attempt to attach an auto-named database ... aspnetdb.mdf failed.

I had an issue trying to open the aspnet membership database on IIS over the weekend. I would get the following error.
An attempt to attach an auto-named database for file C:\Users \administrator.WESTCHASE\Documents\Visual Studio 2010\Projects\ClaimsEnableWebSite2\ClaimsEnableWebSite_STS\App_Data\aspnetdb.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

And the fix is simple. This was the connection string I was using when I was getting the error. add name="LocalSqlServer" connectionString="data source=.\;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient"

and all that I had to do was add Database=aspnetdb to the connection string.

Friday, July 2, 2010

WF Services And Windows Identity Foundation

In the next couple of weeks I am going to be rewriting a project that caused me a lot of pain. originally the project was done in Asp.Net 2.0. I am going however, to redo it from scratch and try to fix some the pain points with WF Services.

I just finished going through the example of WF Services and Appfabric Server in the Visual Studio 2010 Training kit. So armed with that and a few videos that I downloaded from the Tech-Ed site. I am going to tackle a real world situation.

And just to make things a little more interesting I am going to add Claims Based Authentication to the mix.

Thursday, July 1, 2010

So easy

It's so easy to get distracted and postpone things that need to be done now for later. Never again!