Ch 14 generating entity model

AlanWheeler · January 29th, 2014, 10:41 PM

Hi Imar,

I was able to properly generate the PlanetWroxModel in PlanetWrox.Designer.vb, but it didn't come up right away. There were several differences in my system from the text, which I would expect given I am using Visual Studio 2013. Please comment on the following:

This is from the 1st Try it out in Ch 14.

I was given a choice to select EF 5.0 or 6.0 after Figure 14.1 (step 3). I selected 5.0 because it seems like from the various conversations on the web that 6.0 is a little new.

In step 6 the text says to change the 'Entity Set Names' from singular to plural. But there are 2 properties, 'Entity Set Name' and 'Name'. The 'Entity Set Name' properties were Genres1 and Reviews1 respectively. So I wasn't sure if in Visual Studio 2013 we needed to change the 'Entity Set Name' or the 'Name'. I changed the 'Name' property. Do I need to change it around?

Finally, in step 7 the text says to change the Code Generation Strategy from None to Default. Visual Studio 2013 has neither of those; it has T4 and 'Legacy ObjectContext'. I selected T4 and the system didn't generate anything in PlanetWrox.Designer.vb. Therefore my 'Using PlanetWroxModel' statement wasn't accepted in all.aspx.vb. So I tried the 'Legacy ObjectContext' and it generated the Namespace just fine.

I think I can proceed. But I'd like your input if you're able. Thanks,

Best Regards,
Alan

Imar · January 30th, 2014, 04:51 PM

Hi Alan,

Not sure why the sets have the 1 in their name, but what you described sounds good. Legacy ObjectContext is indeed the option to choose to mimic the 2012 behavior.

Cheers,

Imar

ploddingaussie · April 30th, 2014, 07:51 AM

Thanks, Alan. Picking EF 5.0 was an inspired choice! I chose the default EF 6.0 and encountered the same problem: namespace PlanetWroxModel not visible to Code Behind file (All.aspx.cs, p. 503). In 6.0 this error is fatal because T4 is the only available Code Generation Strategy!