Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Visual Basic > VB 6 Visual Basic 6 > VB.NET
|
VB.NET General VB.NET discussions for issues that don't fall into other VB.NET forums.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the VB.NET section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old June 13th, 2003, 09:21 AM
Authorized User
 
Join Date: Jun 2003
Posts: 18
Thanks: 0
Thanked 0 Times in 0 Posts
Default Packaging an VB.NET Database Application

I have an VB.NET simple application that I wrote. It only consists of 3 forms and an application configuration file. It hooks into an SQL Server 2000 local database.

What I want to do is package this application. How do I do that? And when I package this application will it incorporate the database within the package?

Thanks
 
Old June 13th, 2003, 05:16 PM
Authorized User
 
Join Date: Jun 2003
Posts: 33
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I would guess that you would package a .EXE and you would somehow tell that .EXE where the SQL Server was (probably by providing a connection string in the xml configuration file).

Quote:
quote:Originally posted by fantom222
 I have an VB.NET simple application that I wrote. It only consists of 3 forms and an application configuration file. It hooks into an SQL Server 2000 local database.

What I want to do is package this application. How do I do that? And when I package this application will it incorporate the database within the package?

Thanks
 
Old June 16th, 2003, 02:44 PM
Authorized User
 
Join Date: Jun 2003
Posts: 18
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Well I know what you mean Phillip

But that would work if they already have SQL server. What I want to do is package the database within my application. Do you know a way to do this.

Thanks






Quote:
quote:Originally posted by Phillip
 I would guess that you would package a .EXE and you would somehow tell that .EXE where the SQL Server was (probably by providing a connection string in the xml configuration file).

Quote:
quote:Originally posted by fantom222
 I have an VB.NET simple application that I wrote. It only consists of 3 forms and an application configuration file. It hooks into an SQL Server 2000 local database.

What I want to do is package this application. How do I do that? And when I package this application will it incorporate the database within the package?

Thanks
 
Old June 17th, 2003, 03:15 AM
Authorized User
 
Join Date: Jun 2003
Posts: 63
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi

Just a thought....
You could ship MSDE with your app, if it is targeted at the 1 - 5 users, they could then attatch your database to MSDE after installing MSDE on there server or a dedicated machine, if not then your end user would need the full SQL Server version.



Duncan
 
Old June 17th, 2003, 10:24 AM
Authorized User
 
Join Date: Jun 2003
Posts: 18
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Duncan

You are right I could ship MSDE with my app. I am actually using MSDE on my desktop. I have a database on it and a bunch of stored procedures. I just can't find any information on how to package the everything that I have running now.

1.) vb.net application consisting of 3 vb forms and a app.config file connected to a MSDE (sql server desktop database) I have about 10 stored procedures and 3 tables.


This all runs find using vs.net but now I just have to find a way to package it. I have been looking at articals but I have not run across anything that tells you how to incorporate the database within your install package.


Thanks
 
Old June 18th, 2003, 04:07 AM
Authorized User
 
Join Date: Jun 2003
Posts: 63
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi fantom222

You are very unlikely to be able to package MDSE with your app, you might be able to though, using something like Wise or Installshield, which gives you a bit more flexibilty and in some cases like Wise provide a scripting lanaguage which allows you even more flexibility in creating install packages though these do come at a price.

If the user had MSDE or sql server installed your database could be installed whilst your app was being installed, this is easliy done using a call to OSQL, with a few details from the user (IE user name, password and location of server).

The other option is to have a folder which contains MSDE, a folder containing your database either as a script that the user runs or as database that the user attach's to and a folder with your installation in and a set of concise instructions, though this is not the prettiest of solutions.

Other than that have you checked out if you can create installation scripts/code in VB.Net, I know the VB6 install package was customizable to a point.



Duncan
 
Old June 18th, 2003, 08:32 AM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 1,101
Thanks: 0
Thanked 2 Times in 2 Posts
Default

I'd question if MS even allows you (by license) to distribute MSDE or SQL that way. If you MUST ship a working database file out with your software- I'd look at access- since a .mdf is easily packaged into a setup.

If this is a multiuser system- then you are likely to have a separate install for both the server and client- and the server install would require SQL server to be installed first. This would be typical of many programs using SQL Server as the backed.

Your install package would then create the database in the SQL Server.

Hal Levy
Daddyshome, LLC
NOT a Wiley/Wrox Employee
 
Old June 18th, 2003, 09:07 AM
Registered User
 
Join Date: Jun 2003
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via MSN to dmadam
Default

It is within the liscensing agreement to package applications to run on the MSDE. There is a liscensing component required if the intent is to utilize SQL Server.

Assuming that MSDE / SQL Server is already installed, you could generate the scripts to create your Database and have your application execute the script or create & execute a stored procedure that does. You could easily package the script file as a part of your installation package into the installation directory.

This would require that your User have a Username & Password to the previously installed db.

David Adams
 
Old October 25th, 2004, 09:53 PM
Registered User
 
Join Date: Oct 2004
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via AIM to hswami Send a message via MSN to hswami Send a message via Yahoo to hswami
Default

You could use SQL Packager from Red-Gate Software (www.red-gate.com). SQL Packager which can produce a C# project or a .NET executable for building a database distribution package from your local database installation (tables, stored procedures, tables, triggers, etc.).

I myself purchased their SQL Bundle Developer Edition which allows using the SQL-Packager functionality as a set of APIs callable from .NET code to allow automating building of database packages.

Hope this helps. Unfortunately, there are no "free" or "cheap" solutions out there.
 
Old September 2nd, 2007, 03:44 AM
Registered User
 
Join Date: Sep 2007
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via Yahoo to sairamtirluka56
Default

 HI FRIENDS IF ANY ONE HAVING IDEA OF VB.NET DATABASE APPLICATION PACKAGING PLS MAIL ME THE DETAILS OF THAT APPLICATION

sairam





Similar Threads
Thread Thread Starter Forum Replies Last Post
packaging & deploying vb application sameera Pro VB 6 3 March 13th, 2008 12:01 PM
PACKAGING AN ACCESS APPLICATION sola Access 0 February 22nd, 2006 06:00 AM
PACKAGING OF ACCESS APPLICATION sola Access 4 February 6th, 2006 01:03 PM
Internet Compnent (VB) & Packaging attreyakapil VB Components 0 October 29th, 2004 08:15 AM
Packaging an VB.NET Database Application fantom222 VB How-To 2 June 30th, 2003 12:55 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.