I think most people simply overlook (and taking for granted) things that big companies brought forth, and set low standards for creations by 16 year old basement dwelling kids. XMLHttpRequest came from MS and still people say the company never innovates.
Great tip, thanks...
But still not working...
<asp:Label ID="Label1" runat="server" Text='<%= "Hello " + "World!"%>'></asp:Label>
<span id="Label1"><%= "Hello " + "World!"%></span>
Text property expects a string, and if the tag is not <%# %>, it will consider that a literal string; <%= Hello + World %> in this case. If you want evaluation on the front page, you'd need <%# %>, but that will require you to raise DataBind event.
One nice thing about <%# %> is you can put them anywhere... such as
<asp:Repeater ... DataSource="<%# SomeObject.SomeCollection %>" ...>
So you can actually assign data to controls without doing it in code behind. I prefer this method because it lets me see where I'm getting the data from.
Sabot wrote:People have argued for centuries about Jesus and religions, so we aren't going to crack the issues here on C9 are we?
But I have a belief about what will solve the issues once and for all.
Sorry, my friend, time will not change much. Religion will only evolve with changing human thinking. It's inescapable. First we have Terracentric thinking, then when we all know it's heliocentric, somehow we managed to adapt religions to work with that new discovery. And then when we proved that Earth was more than 5,000 years old, religion still works. Then evolution etc etc... It's really a waste of time when it's clearly an outflowing channel of human's dissatisfaction of its own fragility and insignificance in the universe. Healthier to admit that kind of fragility and insignificance than to force to think otherwise. Didn't you guys get taught that you should be who you are and be proud of who you are in pre-school? It's the biggest athiest organized conspiracy, ya'know.
I remebered I used the legendary 'notepad' to modify and save the Xml file, so I don't think there such an encoding problem.
That's exactly why.
I think that's why too. Remember that XML headers define the encoding (usually UTF-8), so the parser will switch to different decoding schemes regardless of what the file originally is. Notepad can save in UTF-8 format, but on my English machine it saves as ASCII by default. See what your Notepad saved it as.
Office can say "XML file appears to be corrupted" but a standard user will not know what that is all about. ("I'm opening a Word file! What XML file!?!")
Is it a good idea to split tables? Let's say I have a table of photos, a table of galleries, a table to relate photos to galleries (M-to-N), a table of articles, and a table to relate photos to articles (M-to-N). Should I combine these two relation tables into one and distinguish each relation with a type, or split it into two by type? If I split them, the growth of table size will only be moderate, say O(1.5N), knowing that a photo may only be featured in 1.5 galleries on average (maybe lower). If I combine them, it may make searches lengthier because it will record all relationships, including ones that I have no mentioned, making the growth likely be O(m x n) or maybe O(n^2). So one makes coding harder and overall performance better, the other makes coding easy but performance may be unscaleable. Further, it's very likely that finding photos in a gallery occurs more frequently than finding all relations in a gallery. What should I do?