Distribution

  • Thread starter Thread starter Just D.
  • Start date Start date
J

Just D.

What's the easiest way to create the distribution package like *.MSI or
better Setup.EXE if the application uses MS SQL Server (MSDE is an
alternative way), MDAC, .NET1.1? I know that the VS has something for that
but is it really very convenient?

Just D.
 
As for MSDE:

1. Create your application, an MSDE client/consumer.

2. If your client does NOT run on the same machine as the (MSDE) server, then
see Microsoft "INF: Enabling SQL DMO Clients Without Installing the CLient
Side Utilities."--this is if your client uses SQL-DMO. (Q248241)

3. Use Visual Studios to create a Setup and Deployment project.

4. The deployment project checks for MDAC as a Launch Condition (e.g.,
MDACSEARCH>="2.7"), where the error refers the user to upgrade MDAC (Google
"MDACSEARCH").

(Note: MSDE is completely separate from your client. Microsoft no longer
supports MSDE merge modules. If you don't know what "MSDE merge modules" are,
then good--they are a pain.)

5. You create your .MSI.--.NET 1.1 redistributable is next.

6. You need the .NET bootstrap with the Setup.exe and the Settings.ini file:
[Bootstrap]
Msi=YourApp.msi
FxInstallerPath=dotNetFramework\
ProductName=... etc...

(Tip: Google "FxInstallerPath" for more info.)

7. Your client package is finished.

8. For your server package you need to see "ReadmeMSDE2000A.htm"

9. Do to the potential reboots in your installation, you may not want to
merge your client and server installations.

Good SQL Express replaces MSDE with no "throttle" and double the db size. (But it
is still beta)

Good luck.
 
Back
Top