GridView, XML, and .NET 2005 Application

[dm1608]

Hello, I'm in the processing of learning .NET 2005 and an trying to rewrite
a simple command line application that I wrote a couple years ago. I have
the following requirements:

1) Read an XML file that I create with a list of .EXE and .DLL files.

2) Scan a directory based on the path stored within the XML file and extract
the production version information

3) Add the Path, Filename and version information to a GridView control.


Now I have item #3 working today which displays output to screen using
console.write.

Question 1:

How can I add headers to a datagrid and update with my own information based
on me scanning a directory?

Question 2:

My application today reads the file path information, etc., from SQL Server
and then scans the directory for the version information. I would like to
instead use an XML file to contain this information instead of SQL Server.
This way I can use ClickOnce easily deploy my application without having a
SQL Server requirement. Most of my updates will be done to the XML file
only, so I would simply like to republish my ClickOnce to have user
redownload new XML file.

What is the best way for me to create an XML file of my data that can be
maintained? I have columsn such as:

1) Filename

2) Path of file

3) Description

4) Shortname of file

Each row within the XML will be unique. I need a way that I can easily
update/create this file. I currently have about 200 rows in SQL that I need
to get into my XML file. I really do not want to retype all the
information, but I can if I have to.

Any help or direction with this would be appreciated.

 

[Kevin Spencer]

You can save a DataSet as XML.

And something else you might want to think about. If the data displayed is
static, not requiring any user interaction, you might want to think about
optimizing your app by using an XSL transform to create the data in HTML in
the page, rather than a DataGrid. You can create an XSL style sheet, and use
an Xml WebControl to display it in any format you choose (as HTML).

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
If you push something hard enough,
it will fall over.
- Fudd's First Law of Opposition

 

[dm1608]

Thanks for the reply, Keven.

I'm trying to do away with using SQL Server. If I use the SaveToXML option
of ADO.NET, is the XML file the is created something that can easily be
maintained going forward? I guess I cannot control the output or format of
the XML file, so that is why I'm thinking it may not be what I want.

Opinions?

 

[Michael Rys [MSFT]]

I don't think it s a good idea to replace the database with an XML file. You
will loose all the benefits of concurrency control, backup/restore,
maintenance etc that the database provides you with.

You can store your XML in the database though either shredded (if it is
relational in nature) or natively...

Best regards
Michael