of the Firebird .NET providers
firebird-net-provider@lists.sourceforge.net
Sent: Tuesday, January 16, 2007 12:09:38 PM
Subject: Re: [Firebird-net-provider] Distributing app with embedded Firebird
2.0 for dummies
For the FirebirdSql.Data.FirebirdClient.dll you could take a look at
IL Merge to include
For the FirebirdSql.Data.FirebirdClient.dll you could take a look at
IL Merge to include the assembly inside your .exe file.
The other files seem to be native DLLs so IL Merge won't help you
here. I think you could store those DLLs as resources of the .EXE and
save them to disk once the program
- Original Message
From: Jiri Cincura [EMAIL PROTECTED]
To: For users and developers of the Firebird .NET providers
firebird-net-provider@lists.sourceforge.net
Sent: Saturday, January 13, 2007 4:04:50 AM
Subject: Re: [Firebird-net-provider] Distributing app with embedded Firebird
2.0 for dummies
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Vlad Orlovsky
Sent: Sunday, January 14, 2007 3:10 AM
To: For users and developers of the Firebird .NET providers
Subject: Re: [Firebird-net-provider] Distributing app with embedded Firebird
2.0 for dummies
Thank you for your feedback everyone
Hello:
Is there a way I can put all these into MyProgram.exe and load/unload
them from there? I'd prefer not to use MyProgram.exe as a storage
medium(once the program is running copy all the DLLs out of it into
the current dir) I would like to make the program very easy to
distribute.
Installers aren't always helpful in locked down environments.
It is often very handy for sys admins to have an XCopy deployable type
application, as it makes copying to client machines logging in much
simpler then running installers, when the users don't have the rights
to, etc.
We had
Scott Price wrote:
It is often very handy for sys admins to have an XCopy deployable type
application, as it makes copying to client machines logging in much
simpler then running installers, when the users don't have the rights
to, etc.
This is probably OT, but this isn't true. XCopy is
Vlad Orlovsky wrote:
What I'd like is to distribute to my end users only MyProgram.exe Most
end-users are not technical people, so even having an installer may be
overwhelming.
I have two ideas how to do this.
First is distr. app. as a self extracting package. This could be acceptable
for
Scott Price wrote:
It is often very handy for sys admins to have an XCopy deployable type
application, as it makes copying to client machines logging in much
simpler then running installers, when the users don't have the rights
to, etc.
This is probably OT, but this isn't true. XCopy is
Alan McDonald wrote:
you've obviously never tried to distribute an application in an environment
like Novell Zenworks. The msi is only relucantly received by sys admins.
Yea, Novell something another. ;)
BTW you're using Novell?
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ |
Alan McDonald wrote:
you've obviously never tried to distribute an application in an
environment
like Novell Zenworks. The msi is only relucantly received by sys admins.
Yea, Novell something another. ;)
BTW you're using Novell?
--
Jiri {x2} Cincura
I'm distributing to a Novell SOE.
Jiri Cincura wrote:
Scott Price wrote:
It is often very handy for sys admins to have an XCopy deployable type
application, as it makes copying to client machines logging in much
simpler then running installers, when the users don't have the rights
to, etc.
This is probably OT, but
12 matches
Mail list logo
