Apr 16, 2012 at 9:48 AM
Edited Apr 16, 2012 at 9:48 AM
I ran into the same error when trying to run it from vs2010 in dot net framework 4.0. And a workaround seems to work fine
Inside the SageFrame.Core project, there are two other sub projects that use LINQ. One is the SageFrame.ListManagement and other is SageFrame.ModuleControls.
Open their .designer.cs and change the name of the connection string in both
public ModuleControlsDataContext() :
i.e. Change the connection string from SFBetaConnectionString to SageFrameConnectionString
Next what I did was opened the "Modules/FeedBack/ContactUs.ascx.cs" and changed the namespace