How do I get back to the install screen (see image) for Visual Studio 2022 on a MacBook Pro? I'm sure this has been asked and answered, but I can't figure it out to save my life...
Download the installer from the Visual Studio for Mac download page.
Once the download is complete, click the VisualStudioForMacInstaller_<build_number>.dmg to mount the installer, then run it by double-clicking the arrow logo
You may be presented with a warning about the application being downloaded from the Internet. Select Open.
An alert will appear asking you to acknowledge the privacy and license terms. Follow the links to read them, then select Continue if you agree
the link about this method other to install again for Macbook Pro : https://learn.microsoft.com/en-us/visualstudio/mac/installation?view=vsmac-2022
Related
I have Visual Studio 2022 Preview installed and would like to replace it with the release version that went live yesterday.
When I started VS and checked for updates, it let me upgrade from the previous release candidate to Preview 1.0, but not the actual release version.
Is it possible at all to replace the preview with a release version, or do I have to install them side by side (and delete the preview)?
This is the version I have now:
Microsoft Visual Studio Professional 2022 (64-bit) - Preview
Version 17.1.0 Preview 1.0
You don't have to reinstall anything. Just switch the update channel in Visual Studio Installer (More -> Update settings):
You have to reinstall. Preview is basically an Insider build. It will continue to update as pre-release even after 2022 releases.
No need to reinstall or to uninstall. Just download the installer of the channel you want and start it. Once the installer finished updating the installer check again the solution from #antarct and it should show you the option to change.
I was able to switch the Update channel, but the context menu still says "Microsoft Visual Studio 2022 Preview" and the application still lives in "C:\Program Files\Microsoft Visual Studio\2022\Preview".
I can't live with that rubbish. These may be minor, but in what other areas was the upgrade done so poorly?
I'll be uninstalling and reinstalling as soon as I can find the time to waste on something I shouldn't need to do.
You don't need to reinstall. From my experience, you just need to run the installer NOT from inside visual studio, but from the start menu.
I had switched to preview from release channel for my installation. When I first saw an update notification in visual studio, I opened the installer via the notification and only preview channel was there in the channel list. Then I decided to try the installer from the start menu before hopelessly re-installing as suggested here, the usual full channel list appeared. Then I went back to visual studio and opened the installer from there again, and the channel list was refreshed in there, too. It seems like a metadata refresh problem. Or, maybe the channel data was updated while I was tinkering with it, IDK.
Looks like I am being held hostage by the Atomineer Pro Documentation add-in for Visual Studio! The trail period is over, I have no use for it! But now everytime I do something in Visual Studio I get an error message and get sent to their web site!
I have looked all over to find out how to uninstall it and have not found away to uninstall it!
WARNING TO EVERYONE - This Atomineer Pro is not easy to uninstall!! Just from the problems of uninstalling it, I would highly recomend no one ever installs it!
I ran into this too running on Windows 10 and VS 2013. Ended up installing and running IObit Uninstaller, which clean up the registry, but Atomineer was still loading in Visual Studio. My second pass was to search my C: drive for "Atomineer" which got several hits including some in a VS AddIns folder (I think). I just deleted everything and that did the trick.
Visual Studio 2015 onwards (Standard VS Extension)
In Visual Studio, go to Tools > Extensions and Updates, select Atomineer from the list, and click the Uninstall button.
Visual Studio 2005-2013 (Standard VS Add-in)
Use Control Panel > Programs and Features to uninstall it just like any other app, or
Run the Atomineer installer and select "uninstall", or
In the unlikely case that neither of the above work, you can manually search your drive and delete any "AtomineerUtils.Addin" files you find.
In any case if you have any problems, email Atomineer support and we'll be happy to help.
On a Windows 8 machine with VS Express 2010, VS 2012, I've installed Visual Studio 2013 Ultimate Preview.
In the end of the installation, an error message appears, giving me this link to activate Hyper-V.
So i entered BIOS, I found a similar option for enabling Virtualization, and set it to Enable.
After finishing restart, I downloaded coreinfo.exe, opened the console as Admin, and checked for asterisk in the row where it said I should check. So there was, which means my computer supports SLAT.
When I go to Control Panel -> Programs -> Windows Features on/off, there is no Hyper-V there as is shown in the link that there will be, and I should select it and press OK to install/activate it.
Will this be fixed by reinstalling Visual Studio 2013 Ultimate Preview now?
Make sure you are running Windows 8 Pro 64-bit as the Hyper-V feature is a Pro Edition feature.
I have Windows 7 Professional x64. I have Visual Studio 2010 Premium and Visual Studio 2012 Premium installed on my machine.
I installed TFS Power Tools Decemeber 2011. I restarted my computer after successful installation. I then checked out a folder from TFS 2010 but the TFS menu items in Windows Explorer context menu do not appear when i right click on the folder.
I even reinstalled it by uinstalling it, restarting the pc and installing it again then restarting it again but same issue.
I have followed the instructions outlined in here:
TFS Power Tools: Shell Extension : Context Menu Quirky and TFS Icons on Files/Folders missing
But same issue same issue occurs. Would anyone know what else i can do to get the TFS menu items to appear in the context menu please?
Thanks in advance,
I am not sure if this would help or you are willing to use a new version but I had the exact same environment and issue with you.
What I had done is that I uninstalled the old TFS Power Tools ( listed with a "Microsoft Team Foundation Server" prefix and/or "Microsoft Visual Studio Team Foundation Server" in Control-Panel/Programs-and-Features ) and install a newer version which is RTM. You can download them at http://www.microsoft.com/en-nz/download/details.aspx?id=35775 and install the following in the same order listed below
Team Foundation Server 2012 RTM Power Tools.msi
Visual Studio Team Foundation Server 2012 Update 1 Power Tools.msi
Visual Studio Team Foundation Server 2012 Update 2 Power Tools.msi
Close Visual Studio before you start then restart after installing, you should see your context menu afterwards together with the green arrow that indicates it is in TFS
Here is a screenshot of it
Also please take note that after installation this would not happen instantaneously as advised on this post: TFS Power Tools: Shell Extension : Context Menu Quirky and TFS Icons on Files/Folders missing
It sometimes takes a while for the TfsComProviderSvr.exe to check if
the local folder is a workspace and register the shell extension.
So this depends on many variables, your TFS server speed, your machine speed and your network speed. In my case I left it overnight to fully show everything.
Windows has a limit on home many overlay icons it can support. This started happening to me after i installed google drive, one drive, and dropbox and the TFSOverlay got pushed down to the bottom in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer \ShellIconOverlayIdentifiers
You can fix it by either
Uninstalling some of the overlay apps. (Eg: remove Google drive
or Dropbox)
Rename the TFS folders in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer \ShellIconOverlayIdentifiers to start with numbers so they take priority (Eg: "1TfsOverlayAdd" , "2TfsOverlayEdit" etc.).
Also there is usually a delay for the green icons to appear in the folder explorer, so be patient.
I was having the same problem and just I executed this file:
C:\Program Files (x86)\Microsoft Team Foundation Server 2012 Power
Tools\TfsComProviderSvr.exe
After a few minutes the menu appeared.
This problem also occurs when you are running Visual Studio under different credentials (i.e. an account with Administrator privileges) than the logged on user. Logging on as that same user displays the ShellExtension correctly. But that's just not an option here...
I have not yet found a solution. It would be a nice feature to be able to set some options for TfsComProviderSvr.exe, so that one can let it watch workspace folders for a different 'Team Member' than the logged on user...
I've tried running Explorer.exe with other credentials, but that does not spawn a new TfsComProviderSvr.exe. Starting it by hand with the different credentials also does not seem to work. An instance of TfsComProviderSvr.exe is always (re)spawned for the currently logged on user.
Forgive me for sharing the obvious, but I had a similar issue, and in my case it appears that the default selected installed features were different than I expected.
I reran the installer using "Modify" instead of "Repair" and confirmed that the Windows Shell Extension feature was selected for installation:
I'm running a similar environment (VS 2010 Shell with VS 2013 Professional). Perhaps that impacts the defaults.
Here is the Power Tools Installer that I used.
I had a similar issue, I ripped off old the version, gave me some issues as you have to stop the TFS process and the explorer process but you can always restart explorer again once the old version has been uninstalled.
Then I restated my machine.
Installed latest version: http://visualstudiogallery.msdn.microsoft.com/b1ef7eb2-e084-4cb8-9bc7-06c3bad9148f ( version 11.0.60506.0 )
Restarted my pc again
Navigated to a source control folder and all TFS icons and shell extensions now started to appear.
Bottom line, the latest version worked for me, did not have to fiddle with reg'values at all.
Here's how I fixed mine. I had installed Visual Studio 2015 and installed TFS Power Tools for VS 2015. I also installed Visual Studio 2017. I generally use VS 2017 and had attached to TFS there. I hadn't attached VS 2015 to TFS and the power tools menu would not show up in explorer. I finally realized that when they say you have to have the same version of Visual Studio installed that you ALSO have to have that visual studio Team Explorer connected to TFS. You don't have to use it beyond that, but it must be connected using the dialog, like you see here.
I have a Windows 7 64-bit computer with Visual Studio 2008 and Visual Studio 2010 Professional installed (C# only).
Now I want FxCop. I read first we should install Microsoft Windows SDK for Windows 7 and .NET Framework 4, so I wanted to do so, but it gives me error and says installation failed, go find more details in some HTML page in a folder path that it does not even exist:
Installation of the “Microsoft Windows SDK for Windows 7″ product has reported the following error: Please refer to Samples\Setup\HTML\ConfigDetails.htm document for further information.
So two questions:
I do not care about the rest of the stuff. I just want FxCop! Do I really need to install this SDK too?
What do you think is the problem when its installation fails?
I had a very similar problem. You don't need to install the SDK to do it. However, you still need to download it which is unfortunate as it is a pretty large download after all. Why it isn't a separate download is beyond me...
Anyway, I extracted the install files I needed by following the information in XXX.
In brief, you need to do this (edited from the link above):
Download the ISO version instead, extract it with 7Zip and locate
Setup\WinSDKNetFxTools\cab1.cab. Open it with Windows and copy out the
file
"WinSDK_FxCopSetup.exe_all_enu_1B2F0812_3E8B_426F_95DE_4655AE4DA6C6".
Rename this to "WinSDK_FxCopSetup.exe" and it should now install.
You can also browse the ISO image with suitable tools rather than unextracting the whole thing.
Given the date of this post, you might have already found the solution, but it may help others who come acros this issue.
From the page above there is a comment linking to another explanation that is better detailed: Liberate FxCop 10.0.