These seem like a long awaited addition, not something I may use too often myself, but I could see this becoming far nicer for code-to-database scenarios utilizing down the line
Awesome feature, there are lots of instances for me where I only want the time or the date. Thanks for putting this into the 10 minute format. Perfect amount of explanation.
Awesome, this was a long time coming! Finally we won't need to write unnecessary code and use up resources because we just wanted the "dateOnly" or "timeOnly" in our code. I don't know about the rest of the community, but we sure use dates a lot in our software, so this is going to help a lot. I also love the format of the 10 minute video, but I do feel that the longer, more in depth discussions, are still needed for those topics that you would not be able to explain in 10 minutes or less.
A great short video on little topics or changes to keep people up to date. It seems like they could have just broken up more methods to the DateTime object to show dates or times, but it gives other options.
I also like the 10 minute format as many others here have commented. Would also have liked to see the DateTimeOffset also mentioned quicly too (as it also appeared in the intelisense at one point - especially when you also mentioned the timezone handling stuff - that the DateTimeOffset handles far better than just DateTime. Once again, a great little snippit.
The DateTime object doesn’t contain time zone information either (as you could believe from the video). DateTimeOffset is the object of choice to store the time zone along with the DateTime as DateTime is limited to specifying whether is is considered local (the computer’s time zone), UTC or unknown.
Wouldn't be better if the DateOnly property of a model could be translated to sql by the fluent api?! Nice 10min format!! Congratulations Tim and thanks a million for helping us
Lovely explanation. Currently enrolled for C# Foundation series. Keep them coming Tim. Also appreciate the 10 minute format videos like others have said.
I think where this is gonna really be useful is when we're presenting or displaying what dates and times are. I think from a calculation standpoint I would probably keep using DateTime. Thanks for showing this!
This is one type of video. It is meant for more experienced developers to get up to speed quickly. I’ll still be doing full videos as well, since those are much better training tools for new to experienced developers.
1. Thank you for a 10 minute video. you have alot of good information, but sometimes as you said, you just want the basics to get up and running. 2. Many times i just wanted the date only or the time only. this will help a lot.
Thank you very much for the content and this new-to-me shorter video style. As a paid TH-cam Member, I really appreciate not having “paid promotions” in your videos to include an overview of your channel. If you could at least embed a “skip intro” to quickly get past the channel overview I would like it.
I assume one of the reasons they added this may be the size of objects in memory (back in the old days: 60's, 70's memory was finite hardware resource it was expensive, so reducing memory consumption of objects had a immediate gain in the software performance, it was basically mandatory). Nowadays, memory isn't much of an issue depending of what kind of software you're developing, but I still think it's quite important to keep things simple and small specially when coding APIs, gRPCs, etc... if you have 500k users / second requesting execution of your code. So good to see this feature available for such cases. "He who never brushed bits after coding a software, may throw the first blob array". Great video as always Tim, thank you, cheers !!!
Memory may be exponentially cheaper today, but it doesn't mean we shouldn't strive to optimize it's usage as much as possible. As a general rule, for every byte you use, there's an impact on performance and memory no matter how small. For instance, an extra byte in an object that's allocated 1 million times is an extra megabyte of RAM and CPU time needed to handle it. This is especially important when developing foundational code such as .NET framework where it is used in numerous ways across multiple applications.
I'll use it quite a bit. The times I used timestamps is in the database - I put a timestamp in to mark when the the record was added or updated... outside of that date is usually sufficient.
Dealing with date and time is a pain in most languages.. so this is always welcome! Not the same thing but C# has had other date'ish objects like TimeSpan.
I work with a lot of databases that have separate date and time columns. Will be nice to have more specific datatypes to use on the CLR side of things.
Hey Tim. Thanks for the video and I liked the new option for date. But question is how does it work if we use this in EF Core Entity model with Code First approach. Thanks in advance
The DateOnly is so good that I decided to redo my custom blazor calendar control to use dateonly instead of datetime since using a calendar is intended to choose date but not time.
Great video, new Time raises with C#10 I guess. How this compares with DateTimeOffset where you also not getting rollovers due to date offset stored? Is this not solving the issue already, or is there a missconceotion on my side?
Yep. That’s the best recording time for me right now. I’m building a recording studio so that I can record during the day. I’m hoping to have that up and running next month.
@@IAmTimCorey that is amazing news, I hope you continue to grow and share your knowledge with us. Congrats on the studio, we hope to get you back to day hours soon 😎
This looks great, really curious how it integrates with SQL/SQLClient, many times when needing to deal with dates/dateTimes we will find out in certain use cases there will be issues. You look at what MS provides and think great this should be really nice, only to find out later what seems logical for how things should work then won't in some edge cases. I'm certain we will see some issues around edges cases when interacting with the different SQL's DateTime column types, code i've had before would have issues depending on the underlying DateTime for the column definition itself, but more the interaction between Sql, ADO.Net and Entity Framework. Would suggest make you test this good...
This is great, not something need all the time but I definitely have use cases when I only need the date or the time only. Will EF Core support the mapping to a date/time column?
That's more of a full Monday video format rather than a 10-minute video format. I will be covering DateTime (and these new ones) in a future Monday video.
Finally! It only took like 20 years for Microsoft to do it! Almost no time at all! 😂. Buy seriously, I have been wanting this since the first day I started programming!!!!!!!
The main question is that how does this look like 'under the facade'? Do DateOnly and TimeOnly have their separate implementation that is not depending on DateTime class? Because if not than it's just some heavy syntax sugar thing going on there=))
I don't but that sounds like a good video suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/
it take 21 years for Microsoft to come to this solution which was very simple from the beginning itself. Even here there was no need for only in those data types. Date is just date no need to tell DateOnly when the other alternative is already DateTime.
The problem is that we always see others' problems as easy and our own as difficult. In this case, if they left off the only, they would have caused problems for literally hundreds of thousands of people. It isn't a "simple" problem. It was a complex situation brought on by a desire not to make breaking changes. They made a hard decision with few good options.
I think this is probably only useful for weird edge cases, if at all. All the benefits for string conversions can also be gained from just learning the relevant formatting symbols. The “weird rollovers” are important because they are telling you something true about that moment in time. To pretend time zones simply don’t exist will lead to more user confusion.
I don't think it is that limited. Think store hours. When you post store hours in the window, you don't include time zones. It is a physical location, so the time will be in that location's time zone. The same is true for birthdays. I don't specify a time for my birthday, just a date. I don't specify which time zone that birthday is in either. Christmas is on December 25th. There are a lot of dates and times that do not relate to a specific time and date in a specific location. They aren't the majority, but there are a lot of them and so far, we have been working around them by specifying date or time parts that are ignored.
@@IAmTimCorey Fair, but those examples are typically just for the purposes of display, no? The moment you try to do any work (math) with them is where you can run into trouble. In my day job role, I set the standards for the developers, and I build a time tracking app that is used by geographically distributed teams on the side. Because I've seen far more than my fair share of temporal arithmetic problems and I spend a lot of time trying to cordon off pitfalls for others, I may be overreacting here. I have been annoyed multiple times by having to deal with DateTime & TimeSpan when it comes to things like binding to UI controls, etc., so I can see why this kind of thing is exciting. I'm just concerned that some folks might see this as an upgrade that resolves the weird things they sometimes see because of timezones, leaps, etc. and not know they're really just sweeping them under the rug.
Useful but need to be careful as it cannot be converted to UTC to compare with other DateOnly and TimeOnly objects. Example: you said the TimeOnly can be used to show the open and close times of a store. What if someone from a different time zone wanted to know if your store was open right now so they could call to place an order. The website might be misleading showing it was open when it was closed and vice versa. In some ways this feels like a throwback to the way things were done in older languages.
Think of this more like the writing on the door for the hours rather than the times on Google. But even the times on Google take into account the time zone of the location. You don't need the time zone on each time if you know what time zone the store is physically located in.
oh, man.. I'm really gonna need the source code for this one.. not like that async await stuff, that's so obvious it's self evident.. but this. man.. I just don't know.. even with source code, will any of us understand? lol. :) Seriously though, thanks again for a great explanation, Tim!
So used to having to write TheDate = DateTime.Now.ToString("dd.MM.yyyy") and TheTime = DateTime.Now.ToString("HH:mm:ss"). Glad things have improved over the years.
But seriously what good are these types without out-of-the-box JSON and EF SQL Server support? Looks like we have to wait until Dot Net Core 7 for this.
@@IAmTimCorey Yes C#10 only works with .Net 6, but how can this be a new "language feature"? There is nothing new in the language for that, its just new datatypes added in .net 6. There is no new keyword or language feature to learn for using this. I'd say its just a .net 6 feature - and yes you will have to use C# 10 for this, but its not a language feature.
I like these new types; I'm just concerned/worried how they would translate when using them with Entity Framework!? If they do, how well will they do so!?
Will this mean that EntityFramework will now parse SQL DATE and TIME into these rather than a getting confused when a DateTime object translates back into a SQL DATE?
could you transform a DateOnly + TimeOnly in a Datetime?, i say because theres sometimes for example when you have a picker for dates and other for hours, you save them in this DateOnly and TimeOnly but you need the DateTime for googlecalendar or any other calendar. Or maybe you want to do some operations with the hours or date and after that get the new datetime.
I'd like se how to work with timezones in Blazor: displaying the date in the timezone of the client, editing the date and sending the date back to the server. With normal dates, but also with DateOnly and TimeOnly.
I like this format of focusing on a topic for 10 mins or less. It's easier to consume for me. Nice job!
I'm glad it is helpful. Just remember to practice what you see so you can actually learn the topic.
Agreed, this is a great idea
@@IAmTimCorey This sort of mini tutorials will come very handy while quickly searching for something or recalling something. Keep up the good work!!
@@IAmTimCorey You won't believe how many of your videos I haven't seen - but wants to see - because I can't spend half an hour on a video 😁
@@IAmTimCorey thanks a lot, this is very useful; like this new compact format, it is convenient and allows to digest info in an effective way
These seem like a long awaited addition, not something I may use too often myself, but I could see this becoming far nicer for code-to-database scenarios utilizing down the line
I agree.
I really like the 10 min. concept, I think it's a great addition to this wonderful channel, keep up the good work Tim!
I’m glad.
I think the same, New to the channel, I wanted to check some other videos of you but don't find the TimeOnly... muhahhahah lol
I think the same, New to the channel, I wanted to check some other videos of you but don't find the TimeOnly... muhahhahah lol
I agree with everyone in that concepts of 10 min or less is a good strategy. Thanks for all you do!
You are welcome.
Actually, I really like these 10 minutes series. Watching a long video is difficult to me. Nice :)
Great!
This 10 minute series make a huge difference. Thank you Tim
You are welcome.
I just love this feature 😍😍😍 waiting for this since I first learned DateTime in C# ❤️
Great!
Thank you Tim! Love the ~10 min format.
You are welcome.
I guess you could say that the “10 minutes or less” format helped me save a lot of TimeOnly 😉
Excellent!
Awesome feature, there are lots of instances for me where I only want the time or the date. Thanks for putting this into the 10 minute format. Perfect amount of explanation.
You are welcome.
Awesome, this was a long time coming! Finally we won't need to write unnecessary code and use up resources because we just wanted the "dateOnly" or "timeOnly" in our code. I don't know about the rest of the community, but we sure use dates a lot in our software, so this is going to help a lot. I also love the format of the 10 minute video, but I do feel that the longer, more in depth discussions, are still needed for those topics that you would not be able to explain in 10 minutes or less.
Thanks for the feedback. The Monday videos are still going to be the long-format training.
Thanks for a shorter video, convenient enough for a busy schedule. I managed to watch this to the end!
Glad you enjoyed it!
Long overdue.
I built an app once that stores the time employees are supposed to come to work each day.
It was hellish working with dateTime
Yeah, that’s not fun.
Just made an appointment manager and my gosh was working with DateTime the most frustrating thing ever.
A great short video on little topics or changes to keep people up to date. It seems like they could have just broken up more methods to the DateTime object to show dates or times, but it gives other options.
They didn’t want to mess with the existing because they wanted to keep compatibility and they wanted to keep the objects small.
I also like the 10 minute format as many others here have commented. Would also have liked to see the DateTimeOffset also mentioned quicly too (as it also appeared in the intelisense at one point - especially when you also mentioned the timezone handling stuff - that the DateTimeOffset handles far better than just DateTime.
Once again, a great little snippit.
Glad you like it and thanks for the suggestion.
This 10 min format is so good to follow your content and learn important stuff! Thank you very much!
I’m glad you like it.
Good addition Tim. You always come up with new ways to present ideas that stick.
Thanks!
Been waiting for this for 20 years!!
Better late than never.
Nice to find what I’m looking for from Tim. Always the first watch
Great!
this is much better, will help a lot with date/time comparisons without worrying about an the time
I knew it!! I knew you could do short to the point videos. Please keep it up.
lol. I’m still going to do long-form videos too because they are really beneficial for actually learning a topic but I’ll do these quick ones as well.
Loving these 10 minute guides, Thank you Tim!!
You are welcome.
The DateTime object doesn’t contain time zone information either (as you could believe from the video). DateTimeOffset is the object of choice to store the time zone along with the DateTime as DateTime is limited to specifying whether is is considered local (the computer’s time zone), UTC or unknown.
Finally! Just not sure why it took them soooo long to do this! By the way, great vid! Love the 10 minute video concept! Very direct to the point!
Thanks, please share them around!
Wouldn't be better if the DateOnly property of a model could be translated to sql by the fluent api?! Nice 10min format!! Congratulations Tim and thanks a million for helping us
Lovely explanation. Currently enrolled for C# Foundation series. Keep them coming Tim. Also appreciate the 10 minute format videos like others have said.
Thank you!
I think where this is gonna really be useful is when we're presenting or displaying what dates and times are. I think from a calculation standpoint I would probably keep using DateTime. Thanks for showing this!
You are welcome.
Hey Tim. Good te see 10 minutes series. Good idea.
Thanks!
@@IAmTimCorey Is this an automatic reply :). You are great in relation with your watchers. Cool for you.
Nope. I don’t have automatic replies.
Short and simple! Please keep this approach in future videos as well !
This is one type of video. It is meant for more experienced developers to get up to speed quickly. I’ll still be doing full videos as well, since those are much better training tools for new to experienced developers.
@@IAmTimCorey Alright! But please do continue these shorter ones as well!
I feel like they should have added a static "Now" property to both the DateOnly and TimeOnly structs.
Yeah, I would have liked that too.
I agree with you Tim. Not always but a lot of time I just want the time. I love it!
Great!
1. Thank you for a 10 minute video. you have alot of good information, but sometimes as you said, you just want the basics to get up and running. 2. Many times i just wanted the date only or the time only. this will help a lot.
I’m glad these will help.
Lovely that it is so short, can watch it while I'm waiting on something. While the longer videos require me to look further at another time or date.
Great!
This is what I've been looking for. Thanks.
You are welcome.
great as allways! Thanks. You are my #1 source for c# tutorials
Thanks!
Thank you very much for the content and this new-to-me shorter video style. As a paid TH-cam Member, I really appreciate not having “paid promotions” in your videos to include an overview of your channel. If you could at least embed a “skip intro” to quickly get past the channel overview I would like it.
Thanks for the suggestion.
Thanks Tim!!
You are welcome.
I’ve been wanting this feature for 20 years.
Better late than never, I guess.
@@IAmTimCorey just in time for a major rewrite of our systems 😁
Love the new DateOnly and TimeOnly.
Great!
It's very nice. Thanks for you
You are welcome.
Very nice. Thanks Tim!
You are welcome.
I like these, I wonder about saving them to a data source though.
It is going to take some time for the data connectors to properly handle these new types.
Good point m exactly what I thought of as i watched the video.
I assume one of the reasons they added this may be the size of objects in memory (back in the old days: 60's, 70's memory was finite hardware resource it was expensive, so reducing memory consumption of objects had a immediate gain in the software performance, it was basically mandatory). Nowadays, memory isn't much of an issue depending of what kind of software you're developing, but I still think it's quite important to keep things simple and small specially when coding APIs, gRPCs, etc... if you have 500k users / second requesting execution of your code. So good to see this feature available for such cases. "He who never brushed bits after coding a software, may throw the first blob array". Great video as always Tim, thank you, cheers !!!
Glad you liked it.
Memory may be exponentially cheaper today, but it doesn't mean we shouldn't strive to optimize it's usage as much as possible. As a general rule, for every byte you use, there's an impact on performance and memory no matter how small. For instance, an extra byte in an object that's allocated 1 million times is an extra megabyte of RAM and CPU time needed to handle it. This is especially important when developing foundational code such as .NET framework where it is used in numerous ways across multiple applications.
Good format. Consider using C# interactive for these quick demos, that way you can present inputs and outputs in one window, without popups.
Thanks for the suggestion.
I'll use it quite a bit. The times I used timestamps is in the database - I put a timestamp in to mark when the the record was added or updated... outside of that date is usually sufficient.
Great!
Great Series. Thanks!
You're welcome!
Dealing with date and time is a pain in most languages.. so this is always welcome! Not the same thing but C# has had other date'ish objects like TimeSpan.
Yep, I agree.
Thank's Tim. very helpful
You are welcome.
Response: I really like this 10 minute short "on point" tutorials .... Great move!
Thanks!
I work with a lot of databases that have separate date and time columns. Will be nice to have more specific datatypes to use on the CLR side of things.
Great!
You`re a star! Keep up the good tuts :)
Thank you!
Hey Tim. Thanks for the video and I liked the new option for date. But question is how does it work if we use this in EF Core Entity model with Code First approach. Thanks in advance
The DateOnly is so good that I decided to redo my custom blazor calendar control to use dateonly instead of datetime since using a calendar is intended to choose date but not time.
Sounds like a good use.
10 minutes or less. Love it 👍
Great.
Great video, new Time raises with C#10 I guess. How this compares with DateTimeOffset where you also not getting rollovers due to date offset stored? Is this not solving the issue already, or is there a missconceotion on my side?
Thanks Tim.
You are welcome.
I think this feature is a very nice one!
Great!
Love this...
Great!
Thank you! And going hard at 11:43pm, we see you
Yep. That’s the best recording time for me right now. I’m building a recording studio so that I can record during the day. I’m hoping to have that up and running next month.
@@IAmTimCorey that is amazing news, I hope you continue to grow and share your knowledge with us. Congrats on the studio, we hope to get you back to day hours soon 😎
Thrilling stuff.... How in earth did you make that last 7 minutes.
Not sure what you mean.
This looks great, really curious how it integrates with SQL/SQLClient, many times when needing to deal with dates/dateTimes we will find out in certain use cases there will be issues. You look at what MS provides and think great this should be really nice, only to find out later what seems logical for how things should work then won't in some edge cases. I'm certain we will see some issues around edges cases when interacting with the different SQL's DateTime column types, code i've had before would have issues depending on the underlying DateTime for the column definition itself, but more the interaction between Sql, ADO.Net and Entity Framework. Would suggest make you test this good...
So far it isn't integrated yet. That is coming.
This is great, not something need all the time but I definitely have use cases when I only need the date or the time only. Will EF Core support the mapping to a date/time column?
Eventually but not yet.
would’ve been nice to see some old code
Refactored this new way to show the clarity benefit.
That's more of a full Monday video format rather than a 10-minute video format. I will be covering DateTime (and these new ones) in a future Monday video.
Excellent ! thank you
You are welcome.
Finally! It only took like 20 years for Microsoft to do it! Almost no time at all! 😂. Buy seriously, I have been wanting this since the first day I started programming!!!!!!!
Yeah, it has been a long time in coming but I’m glad it is here.
I like these, thanks
You are welcome.
I like this series. Please go to some advanced topics
Advanced topics typically cannot be covered in 10 minutes or less.
Can you do a video showing DateTimeOffset and how to work with time zones?
I'll add it to the suggestion list.
Reduce the time to 1 Minute for such a simple thing. Thank you. ;-)
Sorry, no. If you want that type of content, just read the docs. The problem is that you don't get the context. That's what I provide.
Finally they added it, i hated the DateTime type in .NET
The main question is that how does this look like 'under the facade'? Do DateOnly and TimeOnly have their separate implementation that is not depending on DateTime class? Because if not than it's just some heavy syntax sugar thing going on there=))
I do not believe they rely on DateTime.
Hi tim, thanks for everything.. do you have topic about naming convention.. I think it's very basic important
I don't but that sounds like a good video suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/
What I learned from this video: Tim, you need to go to bed earlier! It’s 11:45pm bro, get some sleep! Lol
It is my best time to record. The house is quiet. I’m building a studio to make this better.
it take 21 years for Microsoft to come to this solution which was very simple from the beginning itself. Even here there was no need for only in those data types. Date is just date no need to tell DateOnly when the other alternative is already DateTime.
The problem is that we always see others' problems as easy and our own as difficult. In this case, if they left off the only, they would have caused problems for literally hundreds of thousands of people. It isn't a "simple" problem. It was a complex situation brought on by a desire not to make breaking changes. They made a hard decision with few good options.
I like it. Thanks!
You are welcome.
Excellent.
Thanks!
I love that feature too
Great!
I think this is probably only useful for weird edge cases, if at all. All the benefits for string conversions can also be gained from just learning the relevant formatting symbols. The “weird rollovers” are important because they are telling you something true about that moment in time. To pretend time zones simply don’t exist will lead to more user confusion.
I don't think it is that limited. Think store hours. When you post store hours in the window, you don't include time zones. It is a physical location, so the time will be in that location's time zone. The same is true for birthdays. I don't specify a time for my birthday, just a date. I don't specify which time zone that birthday is in either. Christmas is on December 25th. There are a lot of dates and times that do not relate to a specific time and date in a specific location. They aren't the majority, but there are a lot of them and so far, we have been working around them by specifying date or time parts that are ignored.
@@IAmTimCorey Fair, but those examples are typically just for the purposes of display, no? The moment you try to do any work (math) with them is where you can run into trouble. In my day job role, I set the standards for the developers, and I build a time tracking app that is used by geographically distributed teams on the side. Because I've seen far more than my fair share of temporal arithmetic problems and I spend a lot of time trying to cordon off pitfalls for others, I may be overreacting here. I have been annoyed multiple times by having to deal with DateTime & TimeSpan when it comes to things like binding to UI controls, etc., so I can see why this kind of thing is exciting. I'm just concerned that some folks might see this as an upgrade that resolves the weird things they sometimes see because of timezones, leaps, etc. and not know they're really just sweeping them under the rug.
Love 10 minutes…a lot of times I want to watch the longer ones but don’t have the time
Great!
I like short video like this. Some time you need just to get some info.
Useful but need to be careful as it cannot be converted to UTC to compare with other DateOnly and TimeOnly objects. Example: you said the TimeOnly can be used to show the open and close times of a store. What if someone from a different time zone wanted to know if your store was open right now so they could call to place an order. The website might be misleading showing it was open when it was closed and vice versa. In some ways this feels like a throwback to the way things were done in older languages.
Think of this more like the writing on the door for the hours rather than the times on Google. But even the times on Google take into account the time zone of the location. You don't need the time zone on each time if you know what time zone the store is physically located in.
Thank you!
You are welcome.
@@IAmTimCorey , where do you take time for answering)
oh, man.. I'm really gonna need the source code for this one.. not like that async await stuff, that's so obvious it's self evident.. but this. man.. I just don't know.. even with source code, will any of us understand? lol. :) Seriously though, thanks again for a great explanation, Tim!
lol yeah, not exactly huge code but some people will want it.
So used to having to write TheDate = DateTime.Now.ToString("dd.MM.yyyy") and TheTime = DateTime.Now.ToString("HH:mm:ss"). Glad things have improved over the years.
Glad you will find them valuable.
very helpful tankYou
You are welcome.
thanks, more about features
You are welcome.
Thank you sir🎉🎉🎉
You are welcome.
Teacher can you introduce us about Clean architecture
It is on the suggestion list.
How about working with international formats, and storing that data. Then working with both the US and International formats at the same time.
Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/
But seriously what good are these types without out-of-the-box JSON and EF SQL Server support? Looks like we have to wait until Dot Net Core 7 for this.
Change like this takes time. These led the way so that not just the Microsoft teams could use them, but also third-partly libraries could as well.
Hi Tim, at 0:33 the Tab Tab to accept, is that an extension or a feature of the new VS?
That’s a new feature of VS2022.
@@IAmTimCorey Nice, must have it. Time for the release 😃
So is this a C# 10 Feature or just new DataTypes/Classes added in .net 6? Which relation has this to C# 10?
This is a C# 10 feature. C# 10 only works in .NET 6+.
@@IAmTimCorey Yes C#10 only works with .Net 6, but how can this be a new "language feature"? There is nothing new in the language for that, its just new datatypes added in .net 6. There is no new keyword or language feature to learn for using this. I'd say its just a .net 6 feature - and yes you will have to use C# 10 for this, but its not a language feature.
Can we use these in our EF entities?
thanks so much.
You are welcome.
I like these new types; I'm just concerned/worried how they would translate when using them with Entity Framework!? If they do, how well will they do so!?
They are working on that now, but they aren't in place yet.
@@IAmTimCorey Thank you for the response and everything else. Please keep doing what you're doing.
I love this
Great!
This is neat!
Great!
Will this mean that EntityFramework will now parse SQL DATE and TIME into these rather than a getting confused when a DateTime object translates back into a SQL DATE?
Not yet, but they are looking into it.
could you transform a DateOnly + TimeOnly in a Datetime?, i say because theres sometimes for example when you have a picker for dates and other for hours, you save them in this DateOnly and TimeOnly but you need the DateTime for googlecalendar or any other calendar.
Or maybe you want to do some operations with the hours or date and after that get the new datetime.
Yes, you can combine a DateOnly and TimeOnly into a DateTime.
I'd like se how to work with timezones in Blazor: displaying the date in the timezone of the client, editing the date and sending the date back to the server. With normal dates, but also with DateOnly and TimeOnly.
If you are dealing with time zones, you probably want the DateTime object.