Ah, one per dataset makes sense for very diverse datasets, but I looked at the first three, they seem pretty similar, so one general one might to do the trick. Or, perhaps two; One that helps examine the column headings and the dashed-line heading to dynamically create another one that's specific to that layout?
I think the question actually should be "it is possible to set xsl dynamically for xml document??"...
"Throughout human history, we have been dependent on machines to survive. Fate, it seems, is not without a sense of irony. " - Morpheus "Real men use mspaint for writing code and notepad for designing graphics." - Anna-Jayne Metcalfe
Sorry, I guess that would make a difference wouldn't it?? private void button2_Click(object sender, EventArgs e) { string str = Application.StartupPath + "\\KeeperOut.xml"; XmlTextWriter writer = new XmlTextWriter(str, Encoding.UTF8); dom.WriteContentTo(writer); writer.Flush(); writer.Close(); } Thanks Mike
You can do anything you want but you pay for everything you do!
Stefan, Thanks for the information. CData it is, because the information may contain <> and other chars that may offend the parser.
Stefan Troschuetz wrote:
Mike Hankey wrote: As an aside this is my 100 post Congratulation
I don't feel any different am I supposed to???:):)
Everybody gotta be somebody
Instead of asking this question all over the CP forums and hoping that someone will do your work, you should start doing it yourself. If you encounter concrete problems while doing this, we'll be pleased to help you as best as we can, but nobody will spend his free time to do your work.
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rick Cook
www.troschuetz.de
There are two types of XML Parser Standards 1) DOM Parser - produces an in memory tree structure of XmlNode objects 2) SAX Parser - fires events during parsing
led mike
This magic is called XMLHttpRequest. Google for it, you'll see a plethora of tutorials. Best regards, - Dmitry.
------------------------- Don't worry, be happy :o)
What I meant that I had tried set preserveWhiteSpace to VARIANT_TRUE. This does indeed get rid of the WhiteSpace but I still have CR-LF's i.e. I have: 0D 0A 09 09 Because the xml file saved to disk has been C14N'ed then when loaded into my IXMLDOMDocument2 object for transmission the signle LF's i.e. 0A have been converted back into CR-LF's i.e. OD OA pairs. What I want to know is how can I load the XML file into my IXMLDOMDocument2 object without it changing it in any way?
wrote:
i dont see what the other user has posted on my reply
Probably he post some XML. The browser tries to interpret the XML tags like he does with HTML tags but since they have no meaning to the browser (in almost any case) the tags and its content are ignored. Asked the user that replied to you to either replace the "<" characters with "<" or check the "Ignore HTML tags in this message" beneath the smilies. If you do not want to wait till he does either of them, you should be able to read the answer by looking at the source code of the page.
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rick Cook
www.troschuetz.de
Subramaniam s.V. wrote:
It says the below error.
Who is it?
Subramaniam s.V. wrote:
Port 'PreBpelService83Port' can not be imported. PortType 'PreBpelService83' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'process' was ignored
Are you sure you're trying to import XML Schema documents? The error complains about not being able to import WSDL elements.
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rick Cook
www.troschuetz.de
jomoK wrote:
I had not found that link when I googled.
Yeah, it's sometimes quite hard to find the right search terms that let google find the answer one is looking for :)
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rick Cook
www.troschuetz.de
WiseHacker wrote:
StringDictionary implements the IDictonary interface and the serializer aborts saying classes implementing that interface are not supported yet.
So I guess you have to do it on your own. Should not be to hard using the XmlTextWriter and XmlTextReader classes. Simply iterate over the dictionary and use the appropriate WriteXX or ReadXX methods to store or retrieve each dictionary entry. The resulting XML could look like that:
<dictionary>
<entry>
<key>key1</key>
<value>value1</value>
</entry>
<entry>
<key>key2</key>
<value>value2</value>
</entry>
...
</dictionary>
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rick Cook
www.troschuetz.de
Stefan, Thank you very much for the info. W3 looks like a very good resource site! Thanks, Mike
If you can't find time to do it right the first time how are you going to find time to do it again?
The problem is the XPath expression passed to the SelectSingleNode method. The double slash at the beginning causes the selection of all nodes in the document from the current node that match the selection no matter where they are, so you're always selecting the first of the AmortizationLineType elements of all AmortizationLine elements. Try using the following XPath expression amortNode.SelectSingleNode("./AmortizationLineType") instead.
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rick Cook
www.troschuetz.de
Got a fix from Microsoft in the end. Horah! FIX: A deserialized object may contain null objects when you deserialize an object from XML in the .NET Framework 2.0 http://support.microsoft.com/kb/918298
