'System.Net.Http.HttpContent' does not contain a definition for
'ReadAsAsync' and no extension method 'ReadAsAsync' accepting a
first argument of type 'System.Net.Http.HttpContent' could be
found (are you missing a using directive or an assembly reference?)

static IEnumerable<Foo> GetAllFoos()
{
  using (HttpClient client = new HttpClient())
  {
    client.DefaultRequestHeaders.Add("appkey", "myapp_key");

    var response = client.GetAsync("http://localhost:57163/api/foo").Result;

    if (response.IsSuccessStatusCode)
      return response.Content.ReadAsAsync<IEnumerable<Foo>>().Result.ToList();
  }

  return null;
}

I understand that most of the enthusiasm displayed is conspicuous, learned behavior. In other words, developers pretend to be in love with JavaScript just because they see, hear or read other developers pretend to be in love with it, who pretend because they see, hear or read other developers...you get the idea.

Reading and debugging JavaScript code is a serious, unremitting pain in the posterior. I don't understand why this alone shouldn't reduce its popularity with developers.

29 minutes ago, wkempf wrote

*snip*

I think you read that wrong. It's a famous quote. I'll write it different to clarify.

There are only two hard things in computer science:

1. cache invalidation

2. naming things

3. off by one errors

 

Eureka! Splendid.

Anyway, now that I know her, I'll remember to be more careful.

1 minute ago, figuerres wrote

*snip*

LOL .... I worked on one system and I always tell folks the DB diagram they printed out looked like one of the micro pictures of a CPU with so many lines going all around and tiny blocks.

That's still something. I'm worried mine might look like a swarm of worms on top of each other having sex.

That's a tough answer to guess. I would guess that the check one doesn't throw any exception because it is only meant to check and report; and verify seems a bit assertive. But then if the answer turned out to be the opposite, I might find that I find no difficulty convincing myself of it.

What's naming things off and on by one?

I think threading is difficult, too. There's too much to learn there.

From a business point-of-view, that's not such a bad thing. There's good news in that.

While it means that they will not have much immediate revenue from it, the good thing is: it will get talked about a whole lot. That will give Microsoft feedback and time to fix things until the product matures.

In time, I think Windows 8 will be a robust and successful operating system. All ground-breaking products take time to mature. In a sense, Windows 8 is a trail-blazer but they took it out too soon.

While in the short term, it seems like bad news for everyone, from the long looks of it, it's good business sense.

My weird review here: http://sathyaish.net/writing/WindowChange.aspx

Variables in statically typed langauges ask a lot of questions before you give them anything. And they still throw errors sometimes even if you make a slight mistake. They're very unforgiving. You know, just like the...

18 hours ago, vesuvius wrote

*snip*

Whatever the result, the issue is not with EF. Sounds to me like someone went mad with denormalization.

Conceptually how you deal with a model with 800 classes is going to be hard, you would be best to group the tables by functionality, or refactor the database if it is young

As in most real world situations, the database comes as a given to me from the year 14 B.C. It was first created then by the Barbarians and then immediately dropped as it was too heavy a load for them to carry.

Activity on it resumed a couple of a hundred years later when King Chatushpada of the Mauryan empire defeated the Mughals in Delhi and began his reign. Right then, on another side of the world, some people were busy finding Columbus while he went to find a piece of land.

Our beloved database came back to life precisely then. This time, when the year was 1497, it was graciously re-created, and in a spur of kindness, left over in posterity by a dozen or so excited African monkeys who recorded their observations of Lord Kelvin as he sailed through the Atlantic collecting a variety of rocks.

You're right. Someone went mad. But it wasn't me.

A hint of relief, albeit just a hint, is that there's a lot of junk tables in the database and I probably won't be needing about half of them. But still, even a half of them are as strong as the whole.

21 hours ago, kettch wrote

If you absolutely have to have a model with lots of tables, EF5 lets you split your model into multiple EDMX files. It's still one model, but multiple designer files.

However, as was said, you most likely don't need all of those at once.

Thanks much, kettch. That's probably an answer to my problem. I am going to do just that.

19 hours ago, Dr Herbie wrote

@Sathyaish Chakravarthy: Well, given the lack of response so far, I guess there's only one way to find out ...

Let us know what happens

Herbie

Thanks, Dr. Herbie. I was thinking along the same lines actually.

I would get frighteningly confused everytime I encountered this line when I was learning to use the HttpClient class, until I read its meaning in the MSDN. It left me wondering how a client could ensure that it received a 200 status code.

I think a more appropriate name for it should have been ThrowExceptionIfNotSuccessStatusCode or just ThrowIfNotSuccessStatusCode.

I still read the Web version of MSDN but I get the feeling that I am not in control because I don't know how to locate the topic I am reading again, except for bookmarking it in my browser. I would like to be able to see the entire MSDN content tree so as to get a perspective of the way content is organized.

This will also enable me to see regular columns that I might be interested in reading on a regular basis. Back in the day, I used to love reading the usability column from Scott Berkun and a few others.

I would love to get back to reading MSDN with some feeling of control as to what I am reading as I still find reading the MSDN an immensely enjoyable activity.

How do I do that?

<customErrors mode="On"
       defaultRedirect="~/Views/Shared/Error.cshtml">
      
      <error statusCode="403"
        redirect="~/Views/Shared/UnauthorizedAccess.cshtml" />
      
      <error statusCode="404"
        redirect="~/Views/Shared/FileNotFound.cshtml" />
    
    </customErrors>

public static void RegisterGlobalFilters(GlobalFilterCollection filters)
        {
            filters.Add(new CustomHandleErrorAttribute());
            filters.Add(new AuthorizeAttribute());
        }

You can copy them to HashSet<T> and then do all the possible Set theory operations on them like Union, Intersection, etc. without writing the code for it yourself.

HashSet<T> has a parameterized constructor that accepts an IEnumerable<T>, so you can copy the data easily.

HashSet<Foo> hashSet1 = new HashSet<Foo>(myObservableCollection1);

HashSet<Foo> hashSet2 = new HashSet<Foo>(myObservableCollection2);

hashSet1.UnionWith(hashSet2);

hashSet1.IntersectionWith(hashSet2);

and so on.

1. In MVC 4, we do not need to create a ModelMetadata class to annotate with data annotations for data validation. We may simply annotate the model classes themselves.
   
   In other words, if we are using the EDM generator to generate a model and corresponding classes for us, then we may create a new set of partial classes with the same names and use data annotation attributes on those partial classes themselves.
   
   We do not need to create a new type of model metadata class and decorate *that* class with data annotation/attributes, like here: http://www.asp.net/mvc/tutorials/older-versions/models-%28data%29/validation-with-the-data-annotation-validators-cs
   
   
2. For data annotations to work, we need a reference only to System.ComponentModel.DataAnnotations and not to Microsoft.Web.Mvc.DataAnnotations.
3. We do not need to instantiate the default model binder in the Application_Start event in the Global.asax file.

Could you please confirm if my understanding is correct?

I've otherwise been a fair member of this community for long. I feel awfully guilty and awkward doing this but I can't help it. I want to spread the word.