Normally this goes in the App.config. VS2008 designer wizard automatically creates this file and puts it in the same location as the assembly in which your database layer resides. But if you’re calling that assembly from an ASP.NET app, you’ll need to move that connectionString to the Web.config. Otherwise, you’ll get this error upon instantiation of the ObjectContext:
The specified named connection is either not found in the configuration, not intended to be used with the EntityClient provider, or not valid.
1 comments:
Great info! I recently came across your blog and have been reading along. I thought I would leave my first comment. I don’t know what to say except that I have.
syringe filters
Post a Comment