i trying create a project with Visual Studio 2019 after a few months but im only see that:
Than i tried to open update vs and i saw this error after finishing update:
How to fix this?
I can't read those errors in that language, but I would suggest two things, both in the VS installer:
Run a repair on your installation.
Make sure you have the relevant workloads installed.
While you're at it, consider upgrading to VS2022 if you can. Given you're on community edition, it's a free upgrade.
Related
Problem picture
Environment:
Windows10 Professional Visual Studio 2017 Unity 2017.4.12f1
I changed the default installation path of Visual Studio 2017 and installed it successfully.
The install path as follows:
D:\win10\Program\visual_studio\2017
However, in the Build setting of Unity, it still can't find my Visual Studio 2017.
How can I solve the problem? Thanks~
Go to Edit > Preferences, and select your Visual Studio to be the preferred external editor. Use Browse if Visual Studio is not listed. More info here.
You need to install windows 10 SDK
https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/
Here's a third answer. I just bumped in to this, and checked that yes VS was the preferred editor, so I went to open up VS to try uninstalling and reinstalling the GameDevWithUnity workflow, but VS popped up a dialog saying I needed to reboot my computer before installation could complete. So it seems like VS was stuck in the middle of an upgrade, which makes it reasonable that Unity couldn't find an appropriate version. I rebooted and everyone is happy.
I would like to work on a project in TypeScript using Visual Studio. I'm working on the project for personal reasons, so I am planning on using the free Visual Studio Community flavor. However, as I went through the installation options, there weren't any options to install TypeScript support.
Here is the list of language support options that I saw as I went through the installation:
VS is a >10GB install, so I would like to make sure I can use it for my projects before I finish installing it.
If I install Visual Studio Community 2015, will I be able to work on TypeScript projects? If so, are there any specific options I need to be sure to select during installation or any post-installation steps I need to follow?
Yes, TypeScript is supported in Community. It is not displayed in that list of components because it is included by default. You do not need to install third party extensions for it to work with VS 2015.
You can but you have to install a 3rd party extension for it https://visualstudiogallery.msdn.microsoft.com/3e5ba71c-abea-4d00-b81b-a62de3ad3d53
This is still in beta so not sure how functional it will be.
On a clean install of community (after uninstalling a trial of 2015 Professional) I got the following when trying to go to the 'Typescript build' tab.
In additional nothing was highlighting in any TS files.
An error occurred trying to load the page. d4683cae-88c4-4b85-863d-ac8014f3ba36
So I just closed Visual Studio, went to the Typescript install page and installed the latest version. That fixed everything. The typescript install for VS2015 on this page includes any extensions needed.
For future updates open the Extensions and Updates control panel and look for Typescript for Microsoft Visual Studio.
I'm trying to create an F# project in Visual Studio 2015 Community. However, before I can do that I have to install the F# tools. Unfortunately, every time I try to install them (or any other tools for that matter) I get this error
and have no idea why. Anybody know how to fix this?
I'm having this question since a month and I'm not able to test it, so i want to ask here if someone have met this situation. Since there is no official release of the new Visual Studio 2015 and it's on RC now ,I'm interested in does someone know if VS 2015 and VS 2013 could work together? Will be the code "infected" if both sides commit something together? Thanks in advance!
In theory yes, in practice no (or at least your results may vary). VS is designed for side by side installations. For consultants it is very common to have multiple versions of VS installed to match the environment of the client.
That being said, RC is pre release software and bugs are to be expected. Nobody can guarantee you won't have problems. VS is a huge and complex codebase. Throw in the number of permutations of possible plugins and extensions as well as environment conditions and there is always a chance of breaking. Just because it didn't blow up on someone else's system doesn't mean you won't have problems.
When I installed VS 2015 CTP6 a few months ago it broke an install of VS 2013 on the same machine. VS 2015 CTP6 installed without error but trying to "login" (Microsoft's new annoying way to infect all software with a user login) hung and became unresponsive. Upon restart devenv.exe complained about corrupted user settings and even before I tried I had a bad feeling that VS 2013 blew up as well. I was right and it took a reinstall to get it working.
Now on the other hand I installed VS 2015 RC side by side on a machine with VS 2010, 2012 and 2013 without any issue. Does that mean you are guaranteed to not have a problem? Of course not. It is pre-release software. If this is a mission critical machine and you don't have the time to potentially spend a few hours reinstalling VS 2013 I would install it in a VM. If it isn't mission critical or you have the time to reinstall if necessary then roll the dice. Honestly you "should" be fine, the RC is pretty stable but you never know.
You should be fine - you'll be using an existing code-base and as long as you don't change the .NET version in the properties, it will compile the same.
However, if you do want to check out the new vNext solutions, you'd have to specifically select the project template in the new project wizard.
These projects are run on the new DNX runtime (which is still evolving and subject to change)
Side by Side. Visual Studio 2015 (even RC) works seamlessly side-by-side with Visual Studio 2013.
See BUILD 2015 News: Visual Studio Code, Visual Studio 2015 RC, Team Foundation Server 2015 RC, Visual Studio 2013 Update 5
or the official guide in the documentation
you might follow the links inside for details about how to configure the target language specific frameworks.
I have just installed VS 2013 RC2 and TypeScript refactoring stopped working. It disappeared from context menu, and pressing Ctrl+R, Ctrl+R gives the following error message:
The key combination (Ctrl+R, Ctrl+R) is bound to command (.Refactor.Rename) which is not currently available.
I have tried restarting VS, didn't help. Any ideas, workarounds?
Edit:
I have submitted a bug to Microsoft. Please upvote it if you have the same issue:
https://connect.microsoft.com/VisualStudio/feedback/details/860463/typescript-refactoring-stopped-working-in-vs-2013-rc2
Microsoft posted the following answer to my question on MS Connect. Seems that while refactor/rename was available in VS Express Edition with TypeScript 0.9, in TypeScript 1.0 it's only available from VS Pro upwards.
Posted by Microsoft on 19/05/2014 at 09:25
Thank you for reporting this issue.
Refactor/rename and NavigateTo are features that are found in the Pro+
versions of TypeScript in Visual Studio 2013. The Pro+ tools are aimed
at helping users work with larger codebases, so there is a focus on
building up tools to help support those codebases in those versions of
Visual Studio. We're working to continue to refine to make the
experience best across both Express and Pro+, with the right features
to help users who want to learn TypeScript and those who want to move
to using TypeScript in larger projects.
For me it happened because of resharper conflict. I uninstalled resharper and restarted visual studio