Use Separate Date Time

Question

I have a Datahora field and wanted to use it separately, that is, a single field in the database called Datahora of the datetime type, and manipulate this field with two editorfor where I save the date of one editorfor and the time of another editorfor in the same field of the database:

View:

<div class="form-group">
     @Html.LabelFor(model => model.DataHora, "Liberar encomenda as", htmlAttributes: new { @class = "control-label col-md-2" })
     <div class="col-md-10">
           @Html.EditorFor(model => model.DataHora, new { htmlAttributes = new { @class = "form-control" } }) Horas
     </div>
</div>
<div class="form-group">
     @Html.LabelFor(model => model.DataHora, "Liberar encomenda dia", htmlAttributes: new { @class = "control-label col-md-2" })
     <div class="col-md-10">
           @Html.EditorFor(model => model.DataHora, new { htmlAttributes = new { @class = "form-control" } })
     </div>
</div>

Class:

 public DateTime DataHora { get; set; }

Answer 1

If you necessarily want to use a database field, you will need a Viewmodel to consolidate date and time.

SeuModel.cs

public DateTime DataHora { get; set; }

SeuViewModel.cs

[DataType(DataType.Date)]
public DateTime Data { get; set; }
[DataType(DataType.Time)]
public TimeSpan Hora { get; set; }

View

<div class="form-group">
     @Html.LabelFor(model => model.Hora, "Liberar encomenda as", htmlAttributes: new { @class = "control-label col-md-2" })
     <div class="col-md-10">
           @Html.EditorFor(model => model.Hora, new { htmlAttributes = new { @class = "form-control" } }) Horas
     </div>
</div>
<div class="form-group">
     @Html.LabelFor(model => model.Data, "Liberar encomenda dia", htmlAttributes: new { @class = "control-label col-md-2" })
     <div class="col-md-10">
           @Html.EditorFor(model => model.Data, new { htmlAttributes = new { @class = "form-control" } })
     </div>
</div>

Controller

model.DataHora = viewModel.Data + viewModel.Hora;

Or even, you can define your Model already with the separate fields, there does not even need the Viewmodel, nor the logic of Controller above.