Multiple executable files in one setup using vb.net 2005 windows application - vb.net

Kindly help me in creating one setup for multiple .exe files....
1)I have 36 .exe file & which needs to be executed in one setup, the project created in VS 2005 using vb.net & is a windows application
2) We need to restore a database during installation process.
3) We also need to set ODBC connection settings during the installation process
Thanks

Related

How to deploy vb.net project with SQL Server CE as database

I created a vb.net project and I used SQL Server Compact Edition as my database. Now I want to create an installer for it, for installing on different PCs.
Does it require to install Visual Studio on the client PC? How should I create installer which will include that database file?
Sorry for my bad English.
Please help.
Thank you in advance.
This msdn link shows how to do it:
https://msdn.microsoft.com/en-us/library/aa983326.aspx
There are 2 parts to it:
Deploy the database file. This can be done by setting the file to copy local always and updating your connection string to point to this.
Deploy the sqlserverce dll's. Follow the instructions in the msdn link which will copy the 7 dll's locally. This means you don't have to install sqlserverce on the individual pcs.

vb net 2008 setup project, msaccess db points to different folder

I have this problem after installing my project. The ms access database I included in the "application files" in setup project is not being used by the project itself. The program works fine until ANY query is executed.
The connectionstring I used points to the included ms access db file which is "DataSource=|DataDirectory|\MyDB.mdb"
After any query executes, this MyDB is ignored, instead it CREATES a new database file with same name in this location
C:\Users\myPC\AppData\Local\VirtualStore\Program Files\myproject\
My installation path is
C:\Program Files\myproject
I tried installing in 3 different machines:
Win7 (this one used for development, VS2008 installed) - problem occured
Win 8.1(VS2008 installed) - problem occured
WinXp (VS2008 NOT installed) - works fine
Does vs 2008 being installed have anything to do with my problem?

Filepath for database in application

I have a SQL database on the server and I want to import it to Visual Studio. I executed the script and a copy of the database was created in VS. Now what I want is to include the Database in to the project folder and I want to know the path of the Database relative to the application.
Also what should I do so that the installation file includes the database as well.
I am working in .NET WPF

Getting a .dep file to work on Windows server 2008 R2

I am working on a dashboard related project using the MS BI stack integrated with SharePoint. I have a configured POC server running on Windows Server 2008 R2, SQL 2012 and SharePoint 2010. I am trying to run one of the MS tutorials that I have already completed on the MS virtual labs in a completely 2008 environment but doing so within my SQL 2012 / SharePoint 2010 environment and this requires I use the .dep file to set the tutorial up. When I first tried to run it I got the windows doesn't know which program to run it with but since the server is in a sandboxed area without net access it cannot search the web for the correct program. In the tutorial it mentioned the file ran via the command prompt so I tried opening it with that and unfortunately nothing happened, but I forgot to untick the always associate box so basically I now have two issues.
First is getting the .dep file back to having no default associated program to run with or finding out what actually is the correct one and the second is to actually get the required files I need to run the .dep file and set-up the environment for the tutorial. Unfortunately MS does not have a nicely detailed list on this.
I have tried using GPMC.MMC to remove the file association but as it is connected to our active directory the default features do not match up with what the technet article states on doing this and I don't want to cause errors on our active directory. Any advice on how to get this working would be appreciated.
You can try downloading the offline training kit.
This training kit should contain a folder with the name "assets". Into this folder you can find an installation of the software "DependencyChecker.msi". Just do this installation. The installation associates the .dep files with the "Dependency Checker Tool"
Secondarily, you can google around to find "How to install the Microsoft Dependency Checker Tool".
In the next link Microsoft talks about the tool.
http://msdn.microsoft.com/en-us/identitytrainingcourse_silverligthandidentity2010.aspx

Visual Basic .Net Application Deployment

I have designed an Application tracking details and I have deployed it. The records are updating the way I need. I want the same application to be used in other three different systems which do not have MS Visual Studio. How can I do it ? Is it enough that I create a similar table in the path I have designed in the other systems and run the Application ?
The probably easiest way to deploy your project would be:
Copy & Paste the whole output from your bin folder to the other machine and make sure the .net framework you used for your application is installed on this machine.
You can also create a Setup and Deployment Project
Open the Solution of your application
File -> Add -> New Project...
Other Project Types -> Setup and Deployment -> Visual Studio Installer -> Setup Project
In the File System Tab right-click on "Application Folder" -> Add -> Project Output and Select "Primary output" from your application project.
(More details about adding files to your setup project: How to: Add Items to a Deployment Project)
If you want to use a copy of the access database on each machine
As you're using an access database. You can mark the include you're access database to your project and set Build Action (in the Property Page) to Content.
Now in the same manner as before rightclick on "Application Folder" and add project output. Only this time select "Content Files" instead of "Primary Output"
Build the setup project and distribute the setup.exe or the .msi file.
If you want to access the same database from each machine
I would advise to store the application on a server which runs independent of your machine so that others can access the database also when your machine is not running.
Change your connectionstring, so that users from other machines are able to connect have a look at this site if you need help with connectionstrings.
As you won't be able to connect to the database with the absolute filepath from other machines, create a fileshare where everyone who should be able to connect has permissions to read/write.
Build the setup project and distribute the setup.exe or the .msi file.
Hope this helps so far.
Why should there be VB language on the target computer? Once compiled(published) you are out of the language environment and the program is in the machine language. In order to publish you have to go to "Build" and "Publish" after opening the program in the language environment. Publish it to a flash drive instead of the C drive. You can do that by selecting the "Browse" option. Once done you can take the flash drive around and install it on most computers that have the .Net files installed. In my experience most windows opss have them.
Just create an Installer after you have written and debugged your program. Install it plus your database on the server computer. If you intend to share the database and its a file-server database such as Ms Access, you will have to make sure that the folder is a shared folder.
Go to all the other computers on the network and repeat your installation. Make a Mapped drive on each computer and configure your database string to point to the mapped drive. If your database a server one like SQL Server, you will need to configure your database access string to point to the Server like so:
\Syl-PC\SQLEXpress.MydatabaseName
I assume that you are familiar with the complete syntax for connecting to databases from Visual Basic using a database provider such as Ole db or the SQL Server Provider.