Question: I'm working on an FAQ type project using AngularJS. I have a number of questions and answers I need to import into the page and thought it would be a good idea to use a service/directive to load the content in dynamically from JSON.

The text strings are quite unwieldily (639+ characters) and the overall hesitation I have is adding HTML into the JSON object to format the text (Line breaks etc). 

Is pulling HTML from JSON considered bad practice practice, and is there a better way to solve this? I'd prefer to avoid using multiple templates but it's starting to seem like a better approach.

Thanks

Answer: 
I replaced 

```
var listeRef = from r in db.refAnomalies
                   select r;

```

with 

```
String sql = @"select * from refAnomalie";
        List<refAnomalie> listeRefference = new List<refAnomalie>();
        var con =  new SqlConnection("data source=(LocalDb)\\MSSQLLocalDB;initial catalog=Banque;integrated security=True;MultipleActiveResultSets=True;App=EntityFramework");
        using (var command= new SqlCommand(sql,con)){

            con.Open();
            using (var reader = command.ExecuteReader())
            {

                while (reader.Read())
                    listeRefference.Add(new refAnomalie
                    {
                        code_anomalie = reader.GetInt32(0),
                        libelle_anomalie = reader.GetString(1),
                        score_anomalie = reader.GetInt32(2),
                        classe_anomalie = reader.GetString(3)
                    });
                    }

        }

```

and it worked fine
@Omar, Changing the complete approach is not the solution of the problem. The way I see this problem is you're having naming convention issue with Navigation properties. Which sometime confuses the EF and results in generating a "Guessed" column name which doesn't exist. 

I would recommend to thoroughly go through this [Discussion](https://stackoverflow.com/questions/11079863/entity-framework-navigation-property-generation-rules/11081568#11081568) about navigation property and name generations. Also check how to overcome this using [InverseProperty](https://stackoverflow.com/questions/24454938/invalid-column-name-error-when-trying-to-associate-objects-with-entityframework) attribute.

Since We don't have complete details of your EF code first entities it's really hard to point out the problem area. But hope above suggestions will help you re-visit your code and identify the problem.