how visual studio looks like for me at the moment
This question was previously asked and I did click the "Open Visual Studio Installer" link. When installing, I also check marked the ".NET Desktop develepment move and clicked "Modify" but still no luck. Does anyone have a solution to this or have run into the same problem?
The version I'm using is Microsoft Visual Studio 2017 Community version on a Windows 7 Enterprise OS.
If you look in \Common7\IDE\ProjectTemplates or \Common7\IDE\ItemTemplates, do you see any templates installed there?
Try re-registering your templates by issuing this command from the VS Command prompt:
devenv.exe /InstallVSTemplates
Related
I have completed an application I have made in Visual Studio 14.0, but when I tried to publish the program, I get an error as Visual Studio cannot find 'SignTool.exe'. I have searched my Hard drive a few times for this but it is nowhere on my PC. Can anyone help me find it or download it?
I had the same issue but installing the Windows 8.1 SDK as per Catquatwa's answer did not work for me (signtool.exe was still missing from C:\Program Files (x86)\Microsoft SDKs\Windows\vX\Bin).
I stumbled across this solution: http://www.benedykt.net/2015/08/12/missing-signtool-exe-w-visual-studio-2015/
Basically, for VS 2015, this would be:
Open Programs and Features
Select "Microsoft Visual Studio 2015" and click "Change"
Press "Modify" to progress to Features options
Select "Windows and Web Development", then tick "ClickOnce Publishing Tools" for installation
Then "Next" and then "Update"
I have a windows 7 and installing the ClickOnce Tools was not enough.
The signtool.exe appeared after also installing the sdk:
If you do not care about sign your program when you publish, just right click your project then choose Properties --> Signing --> un-check Sign the ClickOnce manifest . I had the same issue when building my program on another machine which did not have ClickOne.
The SignTool is available as part of the Windows SDK (which comes with Visual Studio Community 2015). Make sure to select the "ClickOnce Publishing Tools" from the feature list during the installation of Visual Studio 2015 to get the SignTool.
Once Visual Studio is installed you can run the signtool command from the Visual Studio Command Prompt. By default (on Windows 10) the SignTool will be installed at C:\Program Files (x86)\Windows Kits\10\bin\x86\signtool.exe.
ClickOnce Publishing Tools Installation:
SignTool Location:
1.Just Disable signing from the properties of your project it will solve issue :)
2.The other method is to purchase the certificate for your product from Digicert or Comodo or any other you want. You can get some free certificates for One pc use.
No Worries! I have found the solution! I just installed https://msdn.microsoft.com/en-us/windows/desktop/bg162891.aspx
and it all worked fine :)
Windows Software Development Kit (SDK) for Windows 8.1
http://go.microsoft.com/fwlink/p/?LinkId=323507
Right click on Project, select properties and Un-Check the sign on option in teh project save and re-built.
This has fixed issue for me.
Here is a solution for Visual Studio 2017. The installer looks a littlebit different from the VS 2015 version and the name of the installation packages are different.
I have a Visual Studio 2013 extension that has a reference to Microsoft.VisualStudio.TeamFoundation.VersionControl.dll, from which the following type can be obtained:
Microsoft.VisualStudio.TeamFoundation.VersionControl.VersionControlEx
Today I uninstalled all previous installations of Visual Studio and then installed Visual Studio 2017 Enterprise with the options ".NET desktop development" and "Visual Studio extension development".
I opened the project with Visual Studio 2017 and had to replace some of the references (EnvDTE, envdte80, Microsoft.VisualStudio.Shell.15, etc) and also installed the nuget package Microsoft.TeamFoundation.VersionControl.All.
Unfortunately the namespace Microsoft.VisualStudio.TeamFoundation and therefore VersionControlEx are not recognized.
I have searched the file on my machine with FileLocator Lite and it does not exist.
Any idea how has this changed in Visual Studio 2017?
I basically to access the PendingChanges window.
Thanks in advance.
By doing a search, I was able to find the file in there:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer
I also found copies associated with other versions of Visual Studio. Given the path of the file, it appears to be included along with Team Explorer.
I suspect the reason you were not able to find the file on your machine is that you had uninstalled your prior versions of Visual Studio and Visual Studio 2017 did not release with Team Explorer.
If you update your version of Visual Studio or you run the standalone installer, I expect that you will be able to find the file.
I installed Visual Studio 2015, and tried to create a windows form, just as I used to do it in the VS2010. I could not find a Windows form for C#.
How can I create one? Do I need to install another version or do I need a plugin or something?
Screenshot: http://prntscr.com/8rwzyl
Informations about my Visual Studio: http://prntscr.com/8rx0a1
It seems you are opening new project in Blend. You have to use Visual Studio (not Blend).
Blend and Visual Studio are installed together with Visual Studio Community Edition 2015 . You probably run a wrong shortcut (which starts Blend).
The Checked Answer is correct however there is no explanation of how to solve this. I just came to the same problem, but figured it out. When searching in your file directory C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE
Then you can search .exe and it will come up with Blend and devenv. Or just scroll till you find devenv. devenv is the clickable application for visual studio community. :)
I just installed Visual Studio 2015 and now want to start a new MonoGame project (C#, Windows DX).
I got MonoGame installed, as well as XNA.
The problem is that the templates are not showing up in the New Project dialogue.
On Visual Studio 2013, they showed up here, they are also nowhere to be found aynwhere else in the Project tree.
So I searched for the templates, they exist in the location where they should be:
C:\Users\<user>\Documents\Visual Studio 2015\Templates\ProjectTemplates\Visual C#\MonoGame
I tried running the devenv.exe /installvstemplates from the Visual Studio admin console, as well as devenv.exe /setup, for good measure.
After doing both several times, mixed with a few Visual Studio 2015 and Windows restarts, the project templates are still not showing up.
I also tried to clear the cache by deleting C:\Users\<user>\AppData\Roaming\Microsoft\VisualStudio and C:\Users\<user>\AppData\Local\Microsoft\VisualStudio\14.0, to no avail.
The MonoGame installer was customized to work with Visual Studio 2015, so I assume it should work somehow.
So, can anyone help me getting those project templates set up?
I found out why it wasn't working:
Apparently, the MonoGame installer puts the Templates in the wrong folder for Visual Studio 2015.
The correct folder for VS2015 is
C:\Users\user\Documents\Visual Studio 14\Templates\ProjectTemplates\Visual C#
The MonoGame installer installs to C:\Users\user\Documents\Visual Studio 2015\Templates\ProjectTemplates\Visual C#
So, when the folder MonoGame inside that folder gets moved to the first one, and the devenv.exe /installvstemplates command gets executed, the templates show up.
In case you work as standard user and run MonoGame setup as admin, MonoGane templates was installed only in Administrator account.
So I just make copy into my user \ProjectTemplates\Visual C#.
MonoGame Setup installation:
C:\Users\**Admin**\Documents\Visual Studio 2015\Templates\ProjectTemplates\Visual C#
Correct folder is under my user account:
C:\Users\**user**\Documents\Visual Studio 2015\Templates\ProjectTemplates\Visual C#
Then as answered above just run devenv.exe /installvstemplates from Developer Command Prompt for VS2015.
how do i get Unity3D for debugging the code, and Visual Studio 2013 which i have now to only script the code. Example: Like Flash Professional for debugging and FlashDevelop for scripting only.
My question is, how do i get the Unity3D link with Visual Studio 2013. I already searching around the internet, and had found that Unity3D only works with VisualStudio 2010.
I wrote a blog article on this awhile back on my blog HERE for Visual Studio.
However I will paste it here too:
How to use Visual Studio 2013
Recently Microsoft bought and re-released the popular Unity3D plugin UnityVS. The now renamed Visual Studio Tools for Unity plugin smooths the connection between Unity and Visual Studio and even allows one to perform debugging too! Download it here.
In Unity Editor go to Edit->Preferences->External Tools and In External Script Editor choose Browse from the drop down box.
Browse to and select C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe.
The External Script Editor should automatically show your selected editor as Visual Studio 2013.
That’s it! It should just work from that point on.
As an important update, I would like to notice, that former UnityVS (after Microsoft's acquisition of SyntaxTree) is now available for free as a rebranded Visual Studio 2013 Tools for Unity.
The versions for VS 2012 and VS 2010 are also available.
The integration of Unity3d and Visual Studio got simpler with latest Unity (version 5) and Visual Studio Tools. This is the current procedure.
To use Visual Studio as editor and debugger with Unity you must:
Install the Visual Studio Tools For Unity. For this download the package at http://unityvs.com (careful to get the version for the Visual Studio you are using) and import it (as is standard in Unity for packages) by going into Assets -> Import Package -> Custom Package and browse to the tools installation folder and pick the package.
Once installed in Unity you will get an additional menu Visual Studio Tools, go there and select "generate project files". Visual Studio will already be the default editor for your scripts.
This done, if you say put a breakpoint in Visual Studio, click on "Attach to Unity" in Visual Studio, and then run your Unity project, the process will stop at breakpoints in Visual Studio and allow variable inspection etc.
you can use unityvs VS plugin (but I'm not sure about current 2013 support, it's works with vs2012) http://unityvs.com/ - on windows it's works very well, but remote OSX debugging feature is not ready yet
I'd like to add to the fine answer given by Pietro Polsinelli, that for me, there was an extra step in his Step 1. And that is that, after installing Visual Studio Tools For Unity, I had to, in Unity, go to Assets->Import Package->Visual Studio 201X Tools and then click around on the menu bar until "Visual Studio Tools" showed up as an option. After that, I could Generate Project Files and Open in Visual Studio.
This enabled me to Attach to Unity in Visual Studio and debug.
None of these solutions worked for me. Renaming monodevelop just changed the default program to notepad++, and the next default program after that was simply notepad.
However, there is a known bug with Visual Studio 2013 (not sure if it was present in previous versions, or if it is present in the non-professional version) where if you try to open a C# file in visual studio, where Visual Studio is opened as administrator and Unity isn't, VS crashes.
I had to either run both programs (VS and Unity) as administrator, or not open VS as administrator (as per the solution found here: http://connect.microsoft.com/VisualStudio/feedback/details/597863/cannot-open-visual-studio-files-from-windows-explorer).
With Visual Studio You Can Use UnityVS Plugin But if You Use Monodevelop You Can Go To Run->Attach To Process.. And Connect The Debugger to Unity Editor It Work Perfectly.
To link Unity with Visual Studio, do the following:
Do this on Unity.
Go to file --> preferences --> external tools --> external script editor --> Choose visual studio.
If Visual Studio is not showing, you Re gonna have to browse Visual Studio by hand.
Then you open any script in the Unity Project window and Visual Studio should open the file.
I hope this is helpful.
Note that I am using Unity 2020.2 and Visual Studio 2019