c# time format weirdness -

-

i have following string thetimeformat custom time format:

  "{0:h:mm tt}"

i have following datetime thetime:

  {1/14/2011 2:19:00 am}

i have following statement

  thistime = thetime.tostring(thetimeformat);

why thistime equal "{0:2:19 am}" . should 2:19 , i'm not seeing why. not in gridview, use following statement , works charm:

((boundfield)(mygrid.columns[0])).dataformatstring = theuserpreferences.usertimeformat; theuserpreferences.usertimeformat same format string.

any suggestions?

when put time format datetime's tostring method, don't need placeholder; is, have this:

thetimeformat = "h:mm tt";

and

thistime = thetime.tostring(thetimeformat)

would give desired output.

edit:

per extended question in comment, allow put format in requires placeholder (and store aforementioned version of thetimeformat in db):

string formatwithplaceholder = "{0:" + thetimeformat + "}";

i briefly played around string.format instead of concatentation, having braces in format giving issues. nonetheless, works, don't particularly concatenation.


Comments

Post a Comment

Popular posts from this blog

c# - Is it possible to remove an existing registration from Autofac container builder? -

-
something along lines: builder.registertype<mytype>().as<itype>(); builder.registertype<mytype2>().as<itype>(); builder.deregistertype<mytype>().as<itype>() var container = builder.build(); var types = container.resolve<ienumerable<itype>>(); assert.istrue(types.count == 1); assert.istrue(types[0].gettype == typeof(mytype2)); scenario: go through bunch of assemblies , go register types want make sure have 1 implementation of given type. need before create container. track on own nice if autofac me bit. this cannot done directly using containerbuilder , unless start on new one. mind you, having first built container should able construct new container filtering away unwanted types , reusing registrations first container. this: ... var container = builder.build(); builder = new containerbuilder(); var components = container.componentregistry.registrations .where(cr => cr.activator.limittype != typ...
Read more

c++ - Warning : overflow in implicit constant conversion -

-
in following program, line 5 give overflow warning expected, surprisingly line 4 doesn't give warning in gcc: http://www.ideone.com/u0bxn int main() { int = 256; char c1 = i; //line 4 char c2 = 256; //line 5 return 0; } i thinking both lines should give overflow warning. or there i'm missing? the topic led me experiment this: typedef type checking? there said following(which deleted answer, because when run it, didn't show had expected): //however, you'll warning case: typedef int t1; typedef char t2; t1 x = 256; t2 y = x; //possible overflow warning! (but doesn't give warning :() -wall doesn't include many options. -wconversion 1 of them , warns behavior you're interested in. see http://gcc.gnu.org/onlinedocs/gcc/warning-options.html
Read more