Featured post

c# - Usage of Server Side Controls in MVC Frame work -

i using asp.net 4.0 , mvc 2.0 web application. project requiremrnt have use server side control in application not possibl in noraml case. ideally want use adrotator control , datalist control. i saw few samples , references in codepleax mvc controllib howwver found less useful. can tell how utilize theese controls in asp.net application along mvc. note: please provide functionalities related adrotator , datalist controls not equivalent functionalities thanks in advace. mvc pages not use normal .net solution makes use of normal .net components impossible. a normal .net page use event driven solution call different methods service side mvc use actions , view completly different way handle things. also, mvc not use viewstate normal .net controlls require. found article discussing mixing of normal .net , mvc.

.net - How do I guarantee node order for an XPath 'OR' query -


i have snippet of xml looks like

<body>    text....    <nodea>....</nodea>    more text    <someothernode>       <nodea>.......</nodea>    </someothernode>    <nodeb>.......</nodeb>      etc..... </body> 

i'm selecting nodea , nodeb nodes inside <body> using xpath query similar //nodea|//nodeb

as understand it, .net supports xpath 1.0 not guarantee node order.

how can guarantee selected nodes returned in document order in or query : that's say:

nodea, nodea, nodeb    

as understand it, .net supports xpath 1.0 not guarantee node order

when xpath 1.0 expression selects nodes evaluated, selected nodes form node-set. a node-set set , this, among many other things, means unordered.

for practical purposes, though, there 1 main ordering chosen enumerate nodes of node set: document order. in practice, xpath 1.0 engines know (and in .net) return selected nodes in document order. in future unlikely change, because vendors try preserve backwards compatibility.

therefore, try using selectnodes() or evaluate() methods , verify nodes in results in document order.

do note: order of following cannot guaranteed , implementation-dependent:

  1. attributes of same element.

  2. nodes belonging different documents (a node-set containing nodes different documents can produced using xslt function document(), of no concern you).


Comments

Popular posts from this blog

c# - Usage of Server Side Controls in MVC Frame work -

cocoa - Nesting arrays into NSDictionary object (Objective-C) -

ios - Very simple iPhone App crashes on UILabel settext -