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?
Related
I am running on application in Visual Studio 2008 in new laptop (windows 2010). in my old system (windows 2008) was running fine. Even my other team member able to run it. I am getting below error
I tried to run same application in VS 2013 its runs fine.
from other post I already install StyleCop . still the same. Anything I can do to get it work? any advice !!
to get that work I created new working folder from VSS and get latest code from VSS and then run the code from new working folder after that all fine.
Migrating a legacy Visual Basic application from Windows 2000 to Windows 2008 R2, I get the error
Component 'MSCOMCTL.OCX' or one of its dependencies not correctly
registered: a file is missing or invalid
Installing VisualBasic6-KB896559-v1-ENU.exe didn't help
For some reason MSCOMCTL.OCX didn't get copied / registered to the correct folder when installing the downloaded runtime VisualBasic6-KB896559-v1-ENU.exe from the KB896559 at https://www.microsoft.com/en-US/download/details.aspx?id=10019.
These manual steps fixed it:
Use 7-Zip to unpack VisualBasic6-KB896559-v1-ENU.exe (NB: executing this file won't install anything!)
Copy the contents to %systemroot%\SysWow64
From command line (run cmd as administrator), execute
%systemroot%\SysWoW64\regsvr32.exe %systemroot%\SysWOW64\mscomctl.ocx
Try running your archaic Visual Basic app again!
Problem: I can't open the installed program on other computers.
I created a program on visual studio 2010 with database created on sql server 2008 express. When i created the setup and install it on MY OWN PC, it runs properly together with its database. When i try to install it on other computers, it successfully installed but i cant open. When in double click the shortcut, even the .exe, it is not responding. The application is not opening/running.
Any ideas?
Your application is probably trying to connect to a database that doesn't exist. You'll need to install SQL Express on the computer where you installed the software.
I am trying to install VS 2010 in my PC but when I clicked on setup file it shows an error like:
unalble to find/load htmllite.dll
But htmllite.dll already exists within the file.
The same thing is happening again when I'm trying to install SQL Server 2008
unalble to find/load setup.rll
But I already have setup.rll file.
After you mount the image, do not run directly, but copy all the files into a folder on your computer , and after that run setup.exe. I had the same issue with microsoft visual studio 2010 on my laptop with windows 8. Good luck!
I have Visual Studio 2008 Database Edition, and everything worked great until the first time I tried to load a .dbproj file. These database project files work for the other developers I work with, but when I try to open it, I just get an error message "Object reference ot set to an instance of an object."
It's probably the same problem this guy is having, although he didn't do a good job of describing it and has no solution.
Every other kind of project file loads and builds and runs normally. dbproj files all generate this cryptic error. I just tried a fresh removal and reinstall of Visual Studio 2008 DE to no avail. Could this have something to do with my SQL 2005 installation? (This also works normally through SQL Server Management Studio.)
**
UPDATE
**
Probably even more importantly, this same error occurs when I try to make a new dbproj file. Every other type of project can be created no problem.
You need to tell Visual Studio the correct instance of SQL Server to use for validation.
Tools>Options>DatabaseTools
Change the settings in "Data Connections" and "Design-time Validation Database" to reflect the correct instance.
After many failed re-configurations and re-installations, a member of my team discovered the problem!
Under Tools > Options > Database Tools > Design-time Validation Database, there is an option to set your SQL Server Instance Name. Visual Studio automatically picks this when it's installed.
The key is that Visual Studio doesn't necessarily pick the right one. I happen to have 3 SQL server instances on my machine. SQLEXPRESS (a 2005 instance that Visual Studio installed alongside itself), SQLEXPRESS2005, a 2005 instance I installed, and SQLEXPRESS2008, which I also installed.
Visual Studio had configured itself to connect to the SQLEXPRESS2008 instance, even though it only supports SQL2005 dbproj files by default. By opening this dialogue, and updating the server instance name, the error no longer appeared and I was able to open dbproj files: