No "Hyper-V" in Win Features to install after installing VS2013 Preview - hyper-v

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.

Related

Codegear Rad Studio C++Builder 2007 won't open on Windows XP SP2

I've been using Rad Studio for some old projects on another Windows XP (32 bit) based PC. So, I wanted to move my projects new computer. But, after the setup, bds.exe didn't open. Same setup file works on Windows 10 PC (64 bit), but I am not able to open on Windows XP computer.
When I tried to open its closing immediately and giving just-in-time debug option from visual studio 2005. Also, it’s giving some error codes. But, I couldn’t find any solution for this issue.
When I wanted to open firstly following screen comes up.
Then, if I click no it’s closing. If I click yes following screen comes up.
Note: Closing Just-in-time debug doesn’t help to open bds.exe .

visual studio crash when try to start kernel debugger

I have a project on my studies to write kernel driver. First step of this project is to prepere working environment, so I installed WDK, installed and configured Windows 7 x64 on virtualbox machine and created hello world kernel driver solution from the internet. After that I could deploy and debug my driver in windows 7 client machine directly from visual studio. Everything worked fine. After few days there was an update to windows 10 (host) - november update 1511, I installed that and (sic!) removed ,,previous Windows installations" to get disk space. Unfortunatelly when I opened my project again - I couldn't deploy and debug my driver due to visual studio crash. I can't find workaround for 3 days which is really frustrating beacause I have to show it to my professor on monday.
What I have tried to do:
I completly reinstalled visual studio and WDK (in host and client machine) and it still happens.
After compile, when I click ,,Debugging tools for Windows - Kernel Debugger", visual studio is crashing
(screen)
I can't get previous installation back and now I have no time to reinstall entire system.
Can you help me, please? Is there a way to get it working again?
PS. Excuse me for my english
I solved that.
After I upgraded my OS, I had still installed WDK 10.0.10240, it was not updated to the newer version. Even if I reinstalled it with new wdksetup.exe downloaded from microsoft site, there was still this version. Microsoft did not update their download page. I searched in google "WDK 10.0.10586.11" and I found the direct link to the newest WDK 10.0.10586.0 on tweettunnel.com/vanhoivo.
The link is:
http://download.microsoft.com/download/C/E/1/CE19C726-6036-4443-845B-A652B0F48CD7/wdk/wdksetup.exe
After I installed this wdk version, the problem has solved, VisualStudio is not crashing now and I can deploy and debug my driver. However, I think that is a bug in VisualStudio - it should show an error that WDK version is not appropriate
Thanks

Unable to use Windows Phone 10 Emulator

I have Visual Studio 2015 Enterprise installed on my Window 10 development machine. I can create a new Universal Windows Platform app and run it both in the simulator as well as on the local machine.
However, when I select any of the 5 pre-installed Mobile Emulators and start debugging, I see the emulator app (XDE.exe) being launched, but then I immediately get an error dialog with the following message:
The emulator is unable to set some properties on the virtual machine: Couldn't change Display controller settings of the virtual machine: .... The configuration version of the Mobile Emulator 10.0.10240.0 WVGA 4 inch ... virtual machine does not support setting resolution type, horizontal resolution or vertical resolution.
When I open the Hyper-V manager, I can see 3 virtual machines installed. I can even start them and they will eventually show the Windows Phone 10 home screen in the expected resolution and orientation.
This happens when running Visual Studio 2015 either as a regular user or as an administrator.
Make sure your computer has an internet connection, and
If the Tools for Universal Windows Apps Development are still installed:
Go to Programs and Features, select Visual Studio 2015, click Change.
In Visual Studio setup, click Modify.
Deselect the feature Tools for Universal Windows App Development.
Select Tools for Universal Windows App Development again, and click
Update.
If you have already uninstalled the Tools for Universal Windows Apps Development: Reinstall Tools for Universal Windows App Development.
Or, take the following steps to reinstall the JavaScript project system and language service:
Download the installer for your edition of Visual Studio, such as, vs_community.exe.
Open a command window, and run the following command:
vs_community.exe /modify /installselectableitems JavaScript_Hidden
/passive
Change directories to C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE
Run the following commands:
devenv /updateconfiguration
devenv /clearcache

Shell Extension : Not showing in Windows Explorer context

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.

checkout TFS files in windows 7 through SSMS and other "Open" dialogs

When I was working on TFS with Windows XP. I was able to execute TFS Commands through the context menu when I had a open dialog box window open in SSMS and other applications. but once I upgraded to Windows 7. I only can Check-out ,check-in , etc... files through Windows Explorer. I have The TFS Power tools and Side kick installed. Is it because Windows 7 dialogue boxes are coded differently then Windows Explorer?
I am Using:
TFS 2010
SQL Management Studio 2008
If you haven't done so already, get the latest Visual Studio 2010 Power Tools
This is the latest and greatest release of power tools, August 2011.
I too have VM Win7 with Team Explorer and a VM with Win7/VS2010 Ultimate. Both with the latest power tools and do not have any issues through the context menu.
Power Tools does not do an in place upgrade. It requires that the prior version of power tools be uninstalled before installing a newer version.