When it finished installing it worked OK, then I closed it, and when I re-opened , it wanted me to Modify, Repair or Uninstall (couldn't bypass it). I chose Repair, but when I close and re-open it again, it does the same and I can't seem to launch Visual Studio. The only way to use the program is through the solution I found here ( C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv (open devenv) and directly open devenv application it won't give you any error about modify repair uninstall) I should mention that I have 2 Microsoft visual studio files 12.0 and 14.0
However, is there a faster way to open it? when I click on the icon in desktop it does not work.
Thanks
I think your shortcut is corrupted.
The standard Target location of Visual studio is: "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\ "
with target devenv.exe.
Please check the shortcut target.
this is the correct one:
"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe"
(don't forget to include the quotation marks)
Related
When I run Visual Studio as Administrator, visual Studio cannot find some files. Everything will compile and run though. When I run normally, it can find all the files without any issues. Does anyone know why this is happening?
Here is what the properties of the exe looks like
Target = "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe"
I have added Visual studio to my startup folder in windows, now I want that when it launches it should load a particular solution by default. So that I don't have to check from the recent projects and select them.
So when my windows starts it launches visual studio and loads this solution and I am ready to code.
You can add a shortcut to your .sln solution file to the startup folder instead of a shortcut to VS. It will load VS with this solution.
If you already have devenv.exe added in startup, the next step is to add the argument with the path to the solution.
Right click the shortcut to devenv.exe under your startup folder.
Click properties.
Update the target field from
"C:\Program Files (x86)\Microsoft Visual Studio
11.0\Common7\IDE\devenv.exe"
to something like this
"C:\Program Files (x86)\Microsoft Visual Studio
11.0\Common7\IDE\devenv.exe" "C:\Your path\HelloWorld.sln"
You can see additional information about Devenv Command Line Switches here.
I am pretty sure I installed VS 2012 Express on my new laptop a month ago. I even posted on Facebook about how I didn't like the default themes because the window borders were too light in color.
Now, I can't seem to find the VS 2012 Express installation. Where should I look?
I've looked for devenv.exe or any exe under C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common\IDE and in C:\Program Files\Microsoft Visual Studio 11.0\Common\IDE.
Okay, I found it. The exe name is VWDExpress.exe and it is located at C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common\IDE
If you are using the Ultimate version go to
C:\Program Files\Microsoft Visual Studio 11.0\Common7\IDE
and look for "devenv" with visualStudio Icon .
I had the same problem. I found it in
Local Disk > Program Files 86 > Common7 > IDE > WDExpress
It wasn't an .exe when I found it, it was an application that I launched.
After uninstalling ReSharper 6.1 from VS 2010, ReSharper Display Items still show up in the Fonts and Colors settings. How do I remove these? Thanks!
If something's gone wrong with the (un)installer, try these steps:
Uninstall all R# versions.
Delete any leftover R# files from under "C:\Program Files (x86)\Microsoft Visual Studio <version>\Common7\IDE\Extensions\JetBrains"
Delete any leftover R# files from under "%LOCALAPPDATA%\Microsoft\VisualStudio\<version>\Extensions\JetBrains" (highliy unlikely to be there).
For VS11, touch the "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\extensions.configurationchanged" file.
Run devenv.com /Setup.
For the Fonts'n'colors problem, try also cleaning up the HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\<version>\FontAndColors\Cache Registry key.
Whenever I try to create a new project in VS 2010 I get the error:
New project/item dialog could not be initialized due to error:
Exception of type 'Microsoft.VisualStudio.Dialogs.DialogInitializationException' was thrown.
And when try to open existing project visual studio 2010 restarts.
I had the same problem on my computer. After a long time searching I solved it by the following steps:
Close all instances of Visual Studio
Go to "C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE" (or whatever is your VS installation directory)
Run command devenv.exe /resetuserdata and wait until finished
Run Visual Studio
I can't find the former case. As you met an exception
Microsoft.VisualStudio.Dialogs.DialogInitializationException
I am suggesting you try the way below:
Run devenv /resetuserdata.
Delete the file:
%LOCALAPPDATA%\Microsoft\VisualStudio\11.0\ComponentModelCache
and restart Visual Studio.
Close all VS instances and try the solution mentioned here:
Launch Developer Command Prompt for VS 2017 as Administrator
Go to VS 2017 installation folder, for example: pushd C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise
gacutil -if Common7\IDE\PublicAssemblies\Microsoft.VisualStudio.Shell.Interop.8.0.dll
Open your control panel
Change
Regional -> Formats tab -> Format: English(United States)
https://connect.microsoft.com/VisualStudio/feedback/details/727578/vs-do-not-work-with-finnish-number-format-on-w8-64-bit
It works for me :)
This problem can cause when you install an older version of Visual Studio nearby the current version. For example VS 2017 is installed on your system and you do force install of VS 2008.
I faced this problem many years ago by installing VS 2008 after VS 2010;
and today again I had this problem. Because I installed SolidWorks 2015 after VS 2017. SolidWorks had a Visual Studio 2008 inside its package that interferes my installation.
Just uninstalled VS 2008 and I'm done.
I found this to still be an issue in Visual Studio Community 2017, Microsoft released a work around that fixed my problem:
The work-around for this issue would be:
-Launch “Developer Command Prompt for VS 2017” as Administrator
-Go to VS 2017 installation folder, for example: pushd C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise
-gacutil -if Common7\IDE\PublicAssemblies\Microsoft.VisualStudio.Shell.Interop.8.0.dll