Note that there are some explanatory texts on larger screens.

plurals
  1. POIs the combination of ADO.NET Entity Framework and ASP.MVC wrong by any chance?
    primarykey
    data
    text
    <p>I have one solution with three projects. </p> <ol> <li>DomainModel (C# Library with ADO.NET Entity Framework)</li> <li>DomainModelTest (Unit Testing for Business Logic)</li> <li>WebApp (Using DomainModel)</li> </ol> <p>For some reason, I cannot even bring the view if I pass any of the objects in the DomainModel, not even simple. I get the error below:</p> <p>Any ideas?</p> <blockquote> <p>Compiler Error Message: CS0012: The type 'System.Data.Objects.DataClasses.EntityObject' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.</p> <p>Source Error:</p> <p>Line 146: Line 147:<br> [System.Runtime.CompilerServices.CompilerGlobalScopeAttribute()] Line 148: public class views_home_index_aspx : System.Web.Mvc.ViewPage, System.Web.SessionState.IRequiresSessionState, System.Web.IHttpHandler { Line 149:<br> Line 150: private static bool @__initialized;</p> </blockquote> <p>I thought this might be helpful, the actual error comes up on the Default.aspx file in the line pointed below:</p> <pre><code>public partial class _Default : Page { public void Page_Load(object sender, System.EventArgs e) { // Change the current path so that the Routing handler can correctly interpret // the request, then restore the original path so that the OutputCache module // can correctly process the response (if caching is enabled). string originalPath = Request.Path; HttpContext.Current.RewritePath(Request.ApplicationPath, false); IHttpHandler httpHandler = new MvcHttpHandler(); httpHandler.ProcessRequest(HttpContext.Current); //**HERE** HttpContext.Current.RewritePath(originalPath, false); } } </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload