What is the best architecture for such app ?

Question

Each user will have independent block with info.
For example
- picture with info
- timetable
- favorite books
He can show or hide each block.
Some block can be obsolete in the future.
Another block can be added in the future.
First idea is put every info in user table.
public class User
    public int UserId {get;set;}
    public string UserName {get;set;}
    //First block info
    public byte[] Image {get;set;}
    public string Deskription {get;set;}
    public bool IsInfoEnabled {get;set;}
    //Second block info
    public int TimeTableId
    public int TimeTableName
    public bool IsTimeTableNameEnabled {get;set;}
So I get table which will be growing up in width ( i mean columns ).
But I don't like to delete columns from these big table.
That's why I decided to move all content block to separate table.
Second idea :
public class User
    public int UserId {get;set;}
    public string UserName {get;set;}
    public int InfoBlockId {get;set;}
    public int TimeTableBlockId {get;set;}
public class InfoBlock
    public int InfoBlockId {get;set;}
    public byte[] Image {get;set;}
    public string Deskription {get;set;}
    public bool IsInfoEnabled {get;set;}
public class TimeTableBlock
    public int TimeTableBlockId {get;set;}
In second way scalability is better, but I will get more queries through numerous tables.
What is the best way ? If you have your additional idea share it!
My .NET Blog with projects and feedback.
Since May 30, 2014 I am waiting for Microsoft fix
these 2 bug. If you know how to speed them up, please help

Answer 1

As your question is about architecture..
The first question is: Do you want to follow a Code-First or Database-First design.
Then you may choose the appropriate forum. From your post, I guess, it's Code-First. So take your wording as an outline. Thus you need a User class and blocks. As blocks can have different types, we need some polymorphism here. Thus it could be an IBlock.
So that your concrete types derive from it:
Instead of an interface it could be also an abstract base class: