Commented Unassigned: Computed columns not yet supported [23]

Hi,

First of all: thanks for creating the Reverse POCO Code First Generator, saves me tons of work!
The code produced by it is clean and very well documented.

While using it I came across a scenario which is not yet supported:
My database contains computed columns: My Contactperson table contains a field FullName which is dynamically composed from the FirstName and LastName. The code generator does not yet recognize this so it creates the following output for the field's configuration:

```
Property(x => x.ContactPersoonVolledigeNaam).HasColumnName("ContactPersoonVolledigeNaam").IsRequired().HasMaxLength(53);
```

Where I would expect it to be:
```
Property(x => x.ContactPersoonVolledigeNaam).HasColumnName("ContactPersoonVolledigeNaam").IsRequired().HasMaxLength(53).HasDatabaseGeneratedOption(DatabaseGeneratedOption.Computed);
```

Because of this, EF complains when validating and saving the model.

Best regards,
Jeroen
Comments: I think the bug is in the file "EF.Reverse.POCO.Core.ttinclude" at this line: ``` private void SetupConfig() { bool hasDatabaseGeneratedOption = false; ``` when I change it to: ``` private void SetupConfig() { bool hasDatabaseGeneratedOption = IsStoreGenerated; ``` it's fixed.