Parse date in c# the same way as it works in javascript..?

By -

I'm developing an electron application with typescript and another backend application with c#. Now i'm trying to parse data from .xlsx Files in my electron app (javascript), and almost the same kind of data trough an XML API from my c# application in the backend..

Now the thing is, the receiving data has a timestamp formatted like this:

2021-07-22T11:31:43Z

I don't even recognize this format (well i'm not having a P.h.D in date time formats.. who would want that anyways.. -.-)

Now, when i parse this date in javascript by doing this:

moment.locale('de')
const date = moment('2021-07-22T11:31:43Z', 'DD.MM.YYYY HH:mm:ss') // haha i'm not even using the correct format to parse this... moment still works magically
const myDate = date.format() // format without params will return ISO 8601, no fractional seconds
// myDate will be = "2021-07-22T11:31:43+02:00" - pure magic

See that? Javascript is automatically adding the timezone information of my personal computer i'm running the code with (and he adds this magic "+02:00" at the end..)

Now, i try to do the same thing with c#:

var timestampDate = DateTime.Parse("2021-07-22T11:31:43Z");
var myDate = timestampDate.ToUniversalTime().ToString("yyyy'-'MM'-'dd'T'HH':'mm':'ss'.'fff'Z'");
// myDate will be = "2021-07-22T11:31:43.000Z"

Not even close! Well... i'm not mad at c# that he doesn't know what i want - i want the timezone information to be added from my local system (doesn't matter what the original was)...

The only thing that matters is - that both implementations are delivering the same value when the same input is given! How can i achieve this?

The only thing i know is: my JS implementation with moment is much more accurate than the c# one - why? Because if i save the data with this string "2021-07-22T11:31:43+02:00", i'll get the correct displaying value out in my Frontend (trough GraphQL) which is "11:31"..

If i test the same thing again with the data coming from c#, it will display "13:31"... which is totally wrong..

Any help very appreciated :)



from Recent Questions - Stack Overflow https://ift.tt/3BWYQww
https://ift.tt/eA8V8J

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more