I was gonna give it up to you?
> -Original Message-
> From: Unmoderated discussion of advanced .NET topics.
> [mailto:[EMAIL PROTECTED] On Behalf Of Scott
> Sent: Saturday, December 25, 2004 12:23 AM
> To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
> Subject: Re: [ADVANCED-DOTNET] Persis
I haven't read WSE2.0 for .NET, but I could certainly understand why it
would say that Web Services interfaces should be Platform independent.
This is a main goal of Web Services which leads to increased
interoperability between systems using different technologies.
However, a particular implement
> Scott writes
You say that most consumers don't have .Net installed. This seems like a
temporary problem, since Microsoft has put a large investment in .Net
Scott,
Microsoft recomends that you write WebServices interfaces to be Platform
independant and to
Thanks for the help. I'll definitely do some research on Firebird.
Serialization is an option, but from my experience with Java, it's
something that should generally be avoided. In addition, I may have to
perform queries which I imagine serialization won't support.
There are a couple of reasons
When you say "data persistence" do you mean "a database with multiple tables",
or do you mean something as simple as "one or more instances of a particular
.NET object"? It is often easy to store instances of .NET objects in a file,
using the serialization facilities that come with .NET.
If yo
> I'm new to the .NET framework and I'm trying to write a
> consumer application that requires data persistence. It
> should be lightweight, so it shouldn't require a separate
> database installation. It should also not require a
> commercial license (i.e. it should be free). Does anyone
>
I'm new to the .NET framework and I'm trying to write a consumer
application that requires data persistence. It should be lightweight, so
it shouldn't require a separate database installation. It should also not
require a commercial license (i.e. it should be free). Does anyone have
any suggesti
