|
Hi
I think must be doing something silly here, but cannot see it. My problem is reading in data from an XML Document into a DataSet in C#.
I have declared a Data Set and a Data Table and used the XMLReader in the Data Set to read in the XML Document - ds.XMLReader("A.xml"). However, I am unable to point the dataset to the datatable.
The dataset does read in the XML without error, and I can write it out again to a new XML Document.
Can someone show me how to point a dataset to a datatable?
Thanks
|
|
|
|
|
I assume you mean ReadXml(), not XmlReader()...
Not quite sure what you're asking here, but if you're trying to get a reference to the table you loaded, that's easy enough:
DataTable dt = ds.Tables[0];
DataTable dt = ds.Tables["MyTableName"];
|
|
|
|
|
Hi
Yes, sorry, it should be readxml.
I did try referencing the table either by index or by name, but all it said was that the table is not there or does not exist. This is what I wrote orginally:
DataSet ds = new DataSet("mySet");
DataTable dt = new DataTable("myTable");
ds.Tables.Add(dt);
ds.ReadXml("myXml");
When I read in the xml into the dataset and then wrote it out to a new xml document it does it - no error, but I can get the data to a table, where I can then work with each value.
I would have thought just a couple of lines of code was all that was needed with DataSets?
|
|
|
|
|
Don't create the table... The dataset will do that for you. Set a breakpoint right after the ReadXml, hop into the watch window, and see what's in the Tables collection... You might just be looking for the wrong table name, because it names it based on the XML file...
This is all assuming the XML file is a valid dataset dump, of course.
|
|
|
|
|
Hi,
for example
String fileName;
fileName = "users_2.xml";
Dataset myDs = new Dataset();
try
{
FileStream fin ;
fin = new FileStream(Server.MapPath("./files/"+fileName), FileMode.Open,
FileAccess.Read, FileShare.ReadWrite);
myDs.ReadXml(fin);
fin.Close();
}
catch (Exception ex)
{
Response.Write(ex.Message);
}
modified 27-May-14 5:34am.
|
|
|
|
|
I want to encrypt my source code how can this be accomplished.
|
|
|
|
|
khalil.kamel wrote: I want to encrypt my source code how can this be accomplished.
Why would you do so?
In between, there are many encrypting tools available on internet.
Manas Bhardwaj
Please remember to rate helpful or unhelpful answers, it lets us and people reading the forums know if our answers are any good.
|
|
|
|
|
I want it to be encrypted on the client side. I do not want the user to see my source for security purposes
|
|
|
|
|
Why would they be able to see your source code ? Do you mean via reflection ? You're going to have to spend some serious money to buy a tool to precompile your .NET app so you don't use MSIL.
Christian Graus
Driven to the arms of OSX by Vista.
Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
|
|
|
|
|
Then don't give it to them.
|
|
|
|
|
LOL - I assume he's talking about reflection.
Christian Graus
Driven to the arms of OSX by Vista.
Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
|
|
|
|
|
The standard answer:
You can't stop someone from decompiling your code while still letting them execute it. You can "obfuscate" it (Which just changes the variable/method/class names to random junk) to make it difficult to understand, and you can encrypt any strings you store in it (While obfuscating the decryption key), but nothing is foolproof.
If someone is determined to read your code and is willing to put in the time and effort, they can do it.
|
|
|
|
|
Ok Guys it seems that i used some wrong terminology , once i was working on a web application when my PM did something suddenly when i right click on view page source there was nothing related to the page source. This is what i want to implement in my new application. Hope i explained it.
|
|
|
|
|
You're getting a lot of responses here. It seems to me that you have no idea what you're doing.
1 - right clicking on a web page lets you view the HTML, not the source code.
2 - the code your PM did to stop right clicks, is useless, anyone can defeat it
3 - there's nothing similar in a non web app, because it doesn't use HTML
4 - anyone can read your source code ( unlike a web app ), using reflection
5 - you can use free obsfucators, but free or commercial, they won't stop anyone determined
6 - you can spend a lot of money on tools that remove your source code,
7 - odds are high that it's not worth the effort.
Christian Graus
Driven to the arms of OSX by Vista.
Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
|
|
|
|
|
khalil.kamel wrote: for security purposes
Security by Obscurity[^] does not provide real protection.
Furthermore, if you are talking about your executable, what do you think encryption it will do? How could you expect the CPU to run code that it does not know? Unless it decrypts it first, but the user has the same knowledge as the CPU, which now apparently includes all information necessary to decrypt it, so you gain nothing.
[edit]Ok I starting posting before that last post of yours. The same principle applies. How does the browser know what to render if it doesn't have the source?
|
|
|
|
|
What am talking about is i do not want the client when he clicks view page source to view the javascript functions the control ids and so on...
|
|
|
|
|
So was I, in the part after the edit. How do you expect the browser to execute encrypted JavaScript, without decrypting it first? You couldn't decrypt it first, because that would mean giving away the decryption code on a silver platter.
|
|
|
|
|
Well I swear i know what are you saying and i do not know what did that person did but i really want to know how did he did it. Does any body has any suggestion?
|
|
|
|
|
From your description in the other post, all your coworker did was remove the "View Source" option from the menu, probably using a javascript function.
This is not secure. It's just aesthetic. It only makes it a little more difficult to view the source, NOT impossible.
|
|
|
|
|
|
|
I have a suggestion of how to make it "slightly harder" to quickly see all JavaScript: put the real code in a base64-encoded string, decode that and write that to the page in a normal function that people can see.
It won't stop a hacker, but it may stop the bored school kids who have nothing better to do than messing around with people's sites.
Don't rely on it.
|
|
|
|
|
You can override the context menu to "hide" the view page source option, but it won't remove it from the browser menu. There is no way to completely remove the ability to view the page source because it must be sent down in a way that the web browser can interpret and display it.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
ok but how these things can be accomplished
|
|
|
|
|
Well, not with C#, that's for a start. Shouldn't you take this over to the web development forum? You'll possibly want to ask about doing it in jquery while you're over there, or disabling the right click.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
