I wrote a vb2005 express app that open an oledb connection to an access db trough a connectionstring defined in the sub main()
Module
ModMainPublic dbcon As New System.Data.OleDb.OleDbConnection Sub Main()
Dim Main As FrmMain Dim connstr As String Try
New FrmMainMain =
connstr =
"Provider=Microsoft.Jet.OLEDB.4.0;User ID=Admin;Data Source=db\delta.mdb;Mode=Share Deny None"dbcon.ConnectionString = connstr
dbcon.Open()
.......
when i publish my application, it creates a setup which include the db in the correct folder, but when I install the setup, it places files in strange named folders in my "local settings" folder. It causes the application not to find the db at runtime.
It's my first vb2005 app, can anyone help me
Thanks

one click deploy and file positions
Luke Hoban
"ClickOnce"
That is the funniest thing I've read in months.
Kah Geh
I think what they mean is that they would like the option of the user choosing the install path rather than the installer silently installing to where it thinks it should go.
I know there are many IT departments which insist on installing applications to a path such as D:\Program Files\ instead of the default C:\Program Files\ so that if/when the windows installation is damaged, then the application files don't go down with the sinking ship
(one of the reasons I personally move the My Documents folder).
I will also second the motion of using a free installer. There is a learning curve, but the end result can be extremely rewarding: plus you have full control over where you sprinkle files on the users computer
.
Roman Wienicke
On the publish tab in your project properties page you can set the Instalation URL to the path you want the app installed to but there is no option for the end user to change it . Clickonce is the penalty you pay for using the free edition if you ask me . I use a free 3rd party installer myself and use the files in the release folder after I build the project . With that though it won't do things like install the framework for the end user .
boonpin
No, there is no support for Setup and Deployment projects in Express editions. ClickOnce deployment is very nice, though, once you get used to the concept: it Just Works across a wide variety of systems, and discourages use of techniques that would cause problems in certain deployment scenarios.
Of course, if you absolutely require a well-known installation path (a sign of bad app design, in my opinion), there are always third-party installers, some very low-cost or even free. Upgrading to the VB.NET Standard edition is of course also an excellent option...
'//mdb
igkmahesh
Well, maybe, but even so, there are people who like to keep their apps and related files on a second disk drive and leave Windows on C.
Thanks though for the reply ... at least I know where I stand
Martin
Leonid Fro
You'll probably want to have a look at the Accessing Local and Remote Data in ClickOnce Applications topic on MSDN2. In short, ClickOnce creates a unique data directory for each app on the target machine, and you can find out what it is at runtime using the ApplicationDeployment.CurrentDeployment.DataDirectory property.
'//mdb
Yashman
CccF
"I know there are many IT departments which insist on installing applications to a path such as D:\Program Files\ instead of the default C:\Program Files\ so that if/when the windows installation is damaged, then the application files don't go down with the sinking ship
(one of the reasons I personally move the My Documents folder)."
Hi SJ!!
It seems to me there are problems with this IF the application has any registry entries because when you replace the OS, the registry is replaced also. It would work for applications that have no registry involvement.
Curtis Zeiszler
So is it not possible to use a Windows installer deployment in VB Express I'd quite like to be able to specify the installation path, but with One Click it's not possible.
Martin T