What is the least impactful way (to the end user) to deploy ac#/database application?

[sherifffruitfly]

Hi all,

I'm making an app that reads some text files on the user's computer,
puts them into a little database, and then least the user view/search
thru them. I've just realized that the sqlexpress db I created thru
server explorer is only gonna be on my dev box, and not the user's
(heh). So I need to write code that'll create a similar db on the
user's computer.

From the end user's standpoint, what's the easiest way to do this? As
much as possible, I'd like this to be completely transparent to the
user.

Thanks for any ideas!

[=?Utf-8?B?QWRhbUg=?=]

RE: What is the least impactful way (to the end user) to deploy a c#/d

How about xml as teh storage and xpath as the lookup.

or

how about not creating the database but just the structures. then on the
client machine you can treat everything as a disconnected tables etc and use
the builtin ado stuff for storage and lookup?


"sherifffruitfl y" wrote:

Hi all,
>
I'm making an app that reads some text files on the user's computer,
puts them into a little database, and then least the user view/search
thru them. I've just realized that the sqlexpress db I created thru
server explorer is only gonna be on my dev box, and not the user's
(heh). So I need to write code that'll create a similar db on the
user's computer.
>
From the end user's standpoint, what's the easiest way to do this? As
much as possible, I'd like this to be completely transparent to the
user.
>
Thanks for any ideas!
>

[sherifffruitfly]

Re: What is the least impactful way (to the end user) to deploy ac#/d

On Mar 13, 6:03 pm, AdamH <Ad...@discussi ons.microsoft.c omwrote:

How about xml as teh storage and xpath as the lookup.
>
or
>
how about not creating the database but just the structures. then on the
client machine you can treat everything as a disconnected tables etc and use
the builtin ado stuff for storage and lookup?

Nah. There are a lot of fields, and at least 100s of 1000s of records
(and growing).

I was really looking for ideas on how to do what I said, not ideas on
how to do something else; but thanks nevertheless.

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

Re: What is the least impactful way (to the end user) to deploy ac#/database application?

sherifffruitfly wrote:

I'm making an app that reads some text files on the user's computer,
puts them into a little database, and then least the user view/search
thru them. I've just realized that the sqlexpress db I created thru
server explorer is only gonna be on my dev box, and not the user's
(heh). So I need to write code that'll create a similar db on the
user's computer.
>
From the end user's standpoint, what's the easiest way to do this? As
much as possible, I'd like this to be completely transparent to the
user.

I think you should go for an embedded database. SQLServer Compact,
Firebird or something similar.

Arne

[Bill Woodruff]

re Adam H in response to Re: What is the least impactful way (to the end user) to deploy a c#/d

Adam H. wrote in response to OP :

"how about not creating the database but just the structures. then on the
client machine you can treat everything as a disconnected tables etc and use
the builtin ado stuff for storage and lookup?"

Hi, this is very interesting : is there an example of this technique you
happen to know of in any CodeProject article, on-line resource ?

best, Bill

"sherifffruitfl y" wrote:

Hi all,
>
I'm making an app that reads some text files on the user's computer,
puts them into a little database, and then least the user view/search
thru them. I've just realized that the sqlexpress db I created thru
server explorer is only gonna be on my dev box, and not the user's
(heh). So I need to write code that'll create a similar db on the
user's computer.
>
From the end user's standpoint, what's the easiest way to do this? As
much as possible, I'd like this to be completely transparent to the
user.
>
Thanks for any ideas!
>