Hello,
I created a setup file from my application. I did this because I want to put my application on other PCs without installing Visual Basic. I basically want to just run the applicatoin on other PCs. What I did to create the setup file was within VB I clicked "Build" then "Publish."
I then wanted to test the setup file on my PC, so I removed everything given to me by the VB installation CD!
So, I uninstalled VB using the installation CD. But, I also had to go to the control panel to remove some of the programs that the installation CD gave me. I did this because the uninstall via the CD left things on my system that the installation CD gave me.
When I was done, the control panel, remove programs listing had nothing with SQL on it.
I then clicked on setup to install my program on my desktop. I was given the following error:
An error occurred attempting to install Equipment_Database_Program.
The following error occurred attempting to install 'C:\Documents and Settings\lusardicm\Desktop\setup database interface\Equipment_Database_Program.application':
"The system cannot find the file specified. "See the setup log file located at 'C:\DOCUME~1\LUSARD~1\LOCALS~1\Temp\VSDD1.tmp\install.log' for more information.
I did a search on my C drive to look for the file install.log, but I found nothing.
I went to the control panel, remove programs and saw that I now had:
Microsoft .NET Framework 2.0
But, I had nothing else new. There is nothing having SQL in the listing.
I know that my application has to have "Microsoft SQL Server 2005 Express Edition x86" to run because I created the application. But, that item was not in the control panel, remove programs listing at all.
When I goto Start, All Programs on my desktop, I see a program entry for:
Microsoft SQL Server 2005
SQL Server Configuration Manager
SQL Server Error and Usage Reporting
SQL Server Surface Area Configuration
Maybe that's why the setup file did not give me the "Microsoft SQL Server 2005 Express Edition x86.
I am using Windows XP.
What do I do to get the setup file to work properly, so that I can run my application called Equipment_Database_Program
Do I have to rebuild my operating system.
Also, when I use the VB installation CD to do a custom installation, it doesn't offer to install "Microsoft SQL Server 2005 Express Edition x86." When I began working with VB 2005, (about 3 months ago) I was able to install it using the same CD that I am now using.
Thank you,

Setup Produced By "Build, Publish" Gives Error After I Uninstalled VB With CD And 'Removed' All Installation CD Programs
Stephanie Chen
As you said you changed the code in you project I assume your using a password file in you application.
You need to add this file into you project.
Add -> Existing Item and then point it to this file.
Once this has occured it will appear in the list of project files. Then you right click the file in Solution explorer and ensure that it Copy to output folder setting is set to copy always or copy if newer.
The publish the deployment and this file should be included in you deployment. run the deployment and look in the folder that contains the deployment - not in you development folder. The file should then exist.
bobo224
Hi, Christopher,
As Spotty implies above, uninstalling your programming environment, API framework (.NET), and SQL Express is a pretty draconian measure, particularly as there may be other programs on your machine relying on (for example) .NET, as well as the fact that it takes a lot of time -- what if you find that you need to make a change to your setup file Install everything, fix, build setup, uninstall everything, test it, if fails, reinstall everything, try to fix it again... that's just super-slow and prone to problems (accidentally forgetting to uninstall of reinstall everything, etc.). It's just not something we can recommend nor would feel comfortable advising on.
The preferred way to do this sort of testing is for your work environment to have a test machine available which doesn't have anything pre-installed on it, and try to install your application on that machine. I don't know if there's another machine available to you, but really there is no substitute for that sort of testing if you need to fully test a setup. (I personally try out my setups for my "for fun" projects by first of all installing them on my own machine without removing anything (so that I can verify it works when the pre-reqs are there) and then testing it on a cheapo second machine with none of the pre-reqs on it to verify that angle of it.
--Matt--*
AlucardHellSing
Asifkhan75025
Sugan
Firstly I'd check to see if this file exists on your system. I would assume that this is a file that is part of you project.
I'd then check the password file and its property in project explorer is set to copy to output directory is set to copy if newer.
This should result in it copying to the application install directory.
I would then check that you were not putting in a path that was specific to the development machine - ie. c:\xyz\password.txt or something like that which is an absolute path. This is going to be installed into the directory with the application in - not to any specific absolute location.
SnowJim
Select All files *.*
and simply select the file.
This is only going to show you filters of some well known file types but you can add absolutely any file type to your project.
Ogulcank
clickonce is the technology behind you so called Build / Publish.
If you cant watch the video - which seems very strange as its for work/educational purpose which I would have thought was an excellent justification. Then you'll need to read the documentation about the product.
I'm not trying to force you to do anything - merely answer your question and guide you in the right direction to educate yourself on the technology you are using.
http://msdn.microsoft.com/netframework/windowsforms/learning/features/clickonce/
Atul Palkhe
ksona
Whoisit
ZopoStyle
tri4pro
OK, I'm not sure why you are removing everything from your machine to start with but what you need for a click once deployment is to ensure that the SQL Express database is actually part of your project (and that the file properties for these files in solution explorer are marked as copy to output folder are marked as copy always or copy if newer) and that in the Publish requirements My Project -> Prerequisites that both the .NET Framework and the SQL Express are checked.
That should be it.
By uninstalling VB, framework etc. you are simply confusing matters.
I'm going to also suggest that you watch the following Dot Net Rocks TV show on click once - its very good and actually shows the setting up of a click once application, so you can listen and watch what you need to do. It covers a lot but is fairly simple to follow
http://dnrtv.com/default.aspx showID=8
re infecta
You are getting this error after you finish the setup and run the program If so then the file "password" is not being found -- it is not being deployed or is being deployed incorrectly. Things to check:
(1) Is it actually being installed to where you think it is Since you are not specifying a path, it's going to look for the file in the application's directory.
(2) Is the password file being installed at all I presume it's part of your solution -- when you select the password file in the solution explorer, what are it's properties in the property grid (is it being copied to the output directory as it ought, is it marked as content, etc.)
(3) What is the exception that's being thrown Change your Catch to Catch ex As Exception and have your message box print out some of the more interesting details in that exception (like ex.Message).
--Matt--*
slickred
Got to agree with Matthew.
Even if its trying the installation on a home machine (if this is work) or another work machine or a friends machine. Basically trying it on another machine outside of your development box.
You really have so many factors that could effect the installation that you cannot possibly tests absolutely every scenario.
As some examples of these tests.
Clearly you wouldnt want to adopt your approach to testing in all these scenarios and your one development box wouldnt be able to satisfy all them.
So basically the best approach is to find another machine or two to test the setup on.
The approach you doing at the moment is time consuming, limiting and run the risk of screwing up your development environment or missing things in your testing by the environment not being as clean as you might think after uninstalling stuff.