![[ERR!]](https://www.gravatar.com/avatar/a269f4d289c78311604da08588915489?d=identicon&s=40)
275 Views
DateTime.Now's new implementation in v4.0 is more memory-consuming than in previous releases. Even though the Int32 boxings issue was resolved, a new issue had emerged.
0 comments
Join in on a hand-picked round up of the best .NET articles every day.
Curated by our Moderators and Voted up by our Community. Free.
DateTime.Now in v4.0 Causes Dynamic Memory Allocations