After installing VB6 successfully on my Windows 8.1 64bit pc, whenever i am trying to open my .vbp project file it gives me an error can't find DAO350.dll file. Googled for every possible solution but couldn't find one.
Please help me.
[UPDATE]
[UPDATE1]: It looks something like this
The DA0350.dll must be registered.
Try this:
On the Visual Basic 6.0 CD (or whatever your installation source is), locate the Dao350.dll file, and then copy it to the directory c:\program files\common files\microsoft shared\DAO. (The Dao350.dll file is located in the \os\system folder on the Visual Basic 6.0 CD.)
To register this file, click Start, click Run, and then type or paste the following line:
Regsvr32 "c:\program files (x86)\common files\microsoft shared\DAO\Dao350.dll"
Update:
The VB6TMPL.TLB is probably not installed for your current user.
Try to run Visual Basic as administrator and/or try this: http://support.microsoft.com/kb/262976/en-us
To solve about "Can't find file DAO350.DLL"
Download DAO350.DLL file from https://www.dll-files.com/dao350.dll.html
Extract file DLL, then copy file DAO350.DLL to C:\Program Files (x86)\Microsoft Visual Studio\VB98 or any other place you install VB 6
Try open your VB 6
Work for me.
From the command prompt, execute the following commands:
cd C:\Program Files (x86)\Common Files\Microsoft Shared\DAO
regsvr32 dao350.dll
This should do it.
On the Visual Basic 6.0 CD (or whatever your installation source is), locate the Dao350.dll file, and then copy it to the directory C:\Program Files\Microsoft Visual Studio\VB98.
After applying this fix. The Visual Basic 6 can now run successfully on your Computer.
NOTE: The Dao350.dll file is located in the \os\system folder on the Visual Basic 6.0 CD.
Related
I installed Visual Studio Code a few days ago, and now I can't find the executable on my machine. Where is it?
I have checked Programs and Features. I have also checked my PATH. For some reason it isn't in either.
Update 10.11.2018
If you do a complete re-install, including uninstalling prior versions of code installed on your machine the new version will be installed at
C:\Users\{UserName}\AppData\Local\Programs\Microsoft VS Code
Update 06.07.2018
Since Version 1.25 VS Code supports portable mode.
Instructions on how to use this are documented here.
You will need the ZIP file download version - not the installer.
After unzipping the contents of the archive, create a data folder inside the folder, where code.exe is located. All settings will now be saved there and can be brought along with you.
|- VSCode-win32-x64-1.25.0-insider
| |- Code.exe (or code executable)
| |- data
| |- ...
On macOS, the folder must be named code-portable-data and has to be a sibling of the app itself. Not inside the app.
|- Visual Studio Code.app
|- code-portable-data
The reasoning behind this can be read here: What is VSCode User Setup for Windows?
Update
If you are using the x64 version, the path is:
C:\Program Files\Microsoft VS Code\
C:\Program Files\Microsoft VS Code\Code.exe
Original answer
At this point and time (Version 1.19.2) Vs code no longer resides in your AppData folder, but under
C:\Program Files (x86)\Microsoft VS Code\
C:\Program Files (x86)\Microsoft VS Code\Code.exe
There are two types of installer available for VSCode.
Go to link to find type of installer you want.
If you are using/going for User Installer, the version will be installed at:
C:\Users\{UserName}\AppData\Local\Programs\Microsoft VS Code
If you are using/going for 64bit System installer, the version will be installed at:
C:\Program Files\Microsoft VS Code\
If you are using/going for 32bit System installer, the version will be installed at:
C:\Program Files (x86)\Microsoft VS Code\
I used the new VSCode User Setup installer on Windows 10, and found the executable here:
C:\Users\my-username\AppData\Local\Programs\Microsoft VS Code\
Okay. I found it in the docs.
C:\Users\my.user\AppData\Local\Code\app-0.1.0
The way I find most intuitive and easy to remember is:
Search for Visual Studio Code in the Windows 10 search bar -> right-click -> Open File Location
For me this goes directly to:
C:\Users\{YOUR_NAME}\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Visual Studio Code
Right-click on the shortcut -> Properties -> Start in:
"C:\Users\{YOUR_NAME}\AppData\Local\Programs\Microsoft VS Code"
If you prefer username-agnostic path strings:
folder: %HOMEPATH%\AppData\Local\Programs\Microsoft VS Code\
executable: %HOMEPATH%\AppData\Local\Programs\Microsoft VS Code\bin\code
If you also want to use those path strings inside C#/C++ code:
folder: "\"%HOMEPATH%\\AppData\\Local\\Programs\\Microsoft VS Code\\\""
executable: "\"%HOMEPATH%\\AppData\\Local\\Programs\\Microsoft VS Code\\bin\\code\""
If for some reason none of the other answers work, try this:
Go into your vscode settings
Find any setting that has 'Edit in settings.json' (for example - Color Customizations)
Press ctrl+shift+s
Go one folder up
Copy + paste the file location (on the top for windows) into into another file explorer
Profit
The difference is:
System Installer will install VSC in C:\Program Files\Microsoft VS Code\
User Installer will install VSC in %HOMEPATH%\AppData\Local\Programs\Microsoft VS Code\
Search for the files with respect the version installed.
Why default your program would be installed here..
C:\Program Files\Microsoft VS Code\
If you have chosen different directory while installing it you can get it by:
1. Go to the icon location
2. Right click open properties
3. Check target
I found it at
C:\Users\%username%\source\repos\Notes\%VSCode-folder%\bin\Debug\
Where %username% is the user and %VSCode-folder% is the VSCode project
The command 'xsd' in the Visual Studio (2010) command window is not fiding my file.
Tried full path 'c:\...\etc...', tried path from project folder, tried any sub path of the full path, tried only the file name (as shown on any example in the web of the usage of the tool).
The file is inside the project inside a subfolder, like "project\schema\mySchema.xsd".
Command used
>Tools.Shell xsd <path\>myfile.xsd /classes
returns:
The operation could not be completed. System could not find specified file.
What work around can I make, how should I properly use the tool? (Am I using it wrongly?)
To find XSD.exe these days, go to:
C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.7.2
Tools\xsd.exe
Step by step:
Go to C:\Program Files (x86)\Microsoft SDKs\Windows\
Click latest version (e.g. v10.0A)
Click Bin
Select latest .NET Version e.g. NETFX 4.7.2 Tools
There is xsd.exe
When you launch the shortcut that opens the Visual Studio Command Prompt you execute a batch file that set some important string inside the PATH environment variable. These strings contain the folder names where the XSD tool is located.
The shortcuts are located in this folder on my dev PC with Visual Studio 2013
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\Shortcuts
The shortcut that opens the Command Prompt for Visual Studio x86 Native Tools is something like this
%comspec% /k ""C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\vcvarsall.bat"" x86
So, unless your installation is damaged you should be able to find the correct command in the relative directory of your Visual Studio 2010 install.
I have a stupid question to ask. I have just started learning F#, and I am trying to compile some basics examples (such as HelloWorld.fs).
I created a simple F# file whose path is: C:\FSharp\HelloWorld.fs.
In order to compile it, I used the full path of the F# compiler as follows:
C:\FSharp>"C:\Program Files\Microsoft F#\v4.0\fsc.exe" HelloWorld.fs
It worked perfectly.
However, I do not want to keep writing the full path of the complier: C:\Program Files\Microsoft F#\v4.0\fsc.exe. I tried to add it to Windows path,but I keep getting the error fsc is not recognized as internal or external command.
How can I create a shortcut word for F# compiler so that I don't have to use the full path everytime I need to compile a program?
For those arriving here in 2019 having received F# as a component of Visual Studio 2017. The location of the F# compiler is as follows:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\FSharp\fsc.exe
Take careful note of the Version Type (Community in this case) and adjust yours accordingly.
You don't really need to create a shortcut for this, you just need to add the folder containing fsc.exe to your PATH variable.
When you open the command prompt, run this:
set PATH=%PATH%;"C:\Program Files\Microsoft F#\v4.0\"
or, if you're using a 64-bit version of Windows:
set PATH=%PATH%;"C:\Program Files (x86)\Microsoft F#\v4.0\"
The most recent version of fsc.exe can be found in these locations :
"C:\Program Files (x86)\Microsoft SDKs\F#\3.1\Framework\v4.0" // as of Aug 2014
"C:\Program Files (x86)\Microsoft SDKs\F#\3.0\Framework\v4.0" // 2013
I tried setting it to my path, but unfortunately it did not work. Tried logging off/restarting etc. I believe it is because of security measures in place on my work computer.
For other people having similar issues, I found that setting the alias not only worked but was more preferable over other methods.
set-alias fsi "C:\Program Files (x86)\Microsoft SDKs\F#\3.1\Framework\v4.0\fsi.exe"
set-alias fsc "C:\Program Files (x86)\Microsoft SDKs\F#\3.1\Framework\v4.0\fsc.exe"
Now the commands don't have the annoying .exe file extension.
Helpful in getting setup was this article on creating persistent aliasing for powershell.
http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/
I can confirm that adding the directory to your PATH variable should do the trick (works on my machine!) Note that you may need to restart any opened command line (or, just to make sure, the system) until the change is taken into account if you change the PATH variable in system properties.
You could also create a bat file with something like:
echo off
"C:\Program Files (x86)\Microsoft F#\v4.0\fsc.exe" %*
And then make sure the bat file is somewhere in your PATH. But the bat file can have a different name (say fsharpc.bat), in case there is some name clash between the standard name fsc and something else on your system...
I have troubles with .vsix installation.
If I launch the .vsix from the explorer, instead of suggesting me to install the package, I get the same ouput as Vsixintaller.exe /? (it displays the command line usage).
I also tried to run the following command line :
VSIXInstaller.exe /skuname:Pro "fullpathto\NuGet.Tools.vsix"
Same output (command line usage is displayed).
What can be wrong ?
I'm suspecting a wrong registry registration, but I couldn't find the source of the problem.
Here is what I have in my registry :
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\VisualStudio.Launcher.vsix] #="Microsoft Visual
Studio Extension"
[HKEY_CLASSES_ROOT\VisualStudio.Launcher.vsix\DefaultIcon]
#="C:\Program Files (x86)\Common Files\Microsoft
Shared\MSEnv\VSFileHandler.dll,-221"
[HKEY_CLASSES_ROOT\VisualStudio.Launcher.vsix\Shell]
[HKEY_CLASSES_ROOT\VisualStudio.Launcher.vsix\Shell\Open]
[HKEY_CLASSES_ROOT\VisualStudio.Launcher.vsix\Shell\Open\Command]
#="\"C:\Program Files (x86)\Common Files\Microsoft
Shared\MSEnv\VSLauncher.exe\" \"%1\""
[HKEY_CLASSES_ROOT.vsix] "Content Type"="application/vsix"
#="VisualStudio.Launcher.vsix"
[HKEY_CLASSES_ROOT.vsix\OpenWithProgids]
"VisualStudio.Launcher.vsix"=""
Any idea ?
PS: my computer is running W2K8 R2 x64, and I use VS 2010 Pro.
I cannot use Visual Studio integrated extension manager because of a proxy server not working with the gallery (don't know why)
Oh ... finally found the issue.
VSix Installer does not seems to be able to install from a network share.
With local copies of vsix, it worked. Strange.
I'm using EditBin to increase the stack size of an application I'm writing. I have this in the post-build event command line for Visual Studio:
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\editbin.exe" /STACK:268435456 "$(TargetPath)"
When I build my project, I get this error:
Error 470 The command ""C:\Program
Files (x86)\Microsoft Visual Studio
10.0\VC\bin\editbin.exe" /STACK:268435456 "[Target Executable]"" exited
with code -1073741515.
I have both of the following in my PATH environment variable:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin
The command also works when I run it manually with cmd.exe. Does anyone know what the problem is here?
I had the same issue, how I resolved it:
Ran msbuild.exe <my.sln> /t:<mytargetproject> from a VS2010 command prompt, where <my.sln> is your solution name and <mytargetproject> is the project you are trying to build. For e.g. msbuild.exe helloworld.sln /t:mainproj.
When you do this or at least when I ran this, a dialog box popped up and said "foo.dll" cannot be found, I added the path of that dll to my "PATH" environment variable and the problem was solved! See ChrisF's comment to the question, as it says, the error is that some dll/component is missing.
From the dll name it complained about, I believe this is not contained to VS2010 libs/dlls, for me it was a third-party dll (which I am using and supposed to be available during the build) it was complaining about.
The best solution is to run the vcvarsall.bat located in the root of the visual studio install folder(C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC). That sets up the search folders for all MSVC compiler related tools.
I got this to work for now by copying mspdb100.dll into the same directory as editbin.exe, but this is not an optimal solution because every developer on my team will need to do the same thing.