I've been using VS2013 since shortly after it was released. I only code in VB and frequently use ListView and GridView. I've been struggling with EF6 and its relationship to these controls without using EntityDataSource. Of course, there is a hack for using EF5 in VS2013 and therefore EntityDataSource - but, I prefer to move ahead with EF6 and the so-called model binding methods (selectmethod, updatemethod, etc). On one hand, I like the concept of using entities with linq in the VB code behind - it seems like a more logical way of providing data for the controls and responding to user actions.
The problem for me is the near total lack of documentation and examples for VB. The link mentioned above is nearly useless for a VB programmer. There is some VB download code that is almost impossible to get running. I've been putting together a set of examples for the 4 methods and some variations - like sorting when the select filters. Some issues could be solved with dynamic data - lots of luck with getting EF6-linq-VB documentation. I've spent a huge number of hours trashing about with trial and error to get some pretty simple things working. It seems to me that Microsoft is really missing the boat by not providing better documentation and examples. If not for Stack Overflow, and the author, Imar Spaanjaars, I would simply have given up.
It really makes me wonder if Microsoft is serious about continuing with VB? I could probably re-train in C# (I was a C programmer years ago) but I find VB to be far more productive for my needs.
The problem for me is the near total lack of documentation and examples for VB. The link mentioned above is nearly useless for a VB programmer. There is some VB download code that is almost impossible to get running. I've been putting together a set of examples for the 4 methods and some variations - like sorting when the select filters. Some issues could be solved with dynamic data - lots of luck with getting EF6-linq-VB documentation. I've spent a huge number of hours trashing about with trial and error to get some pretty simple things working. It seems to me that Microsoft is really missing the boat by not providing better documentation and examples. If not for Stack Overflow, and the author, Imar Spaanjaars, I would simply have given up.
It really makes me wonder if Microsoft is serious about continuing with VB? I could probably re-train in C# (I was a C programmer years ago) but I find VB to be far more productive for my needs.