I want to run emulator in visual studio 2015 . but i cant able to enable it in my windows 10 home edition , because there is no option in (windows on or off feature) . my laptop support slat.. And i also enable visualization technology from bios setting.
Hyper-V is not available in Windows 10 Home. You have to either upgrade to Windows 10 Pro 64bit or use a 3rd party option like VMWare or Virtual Box.
Yes this works on Windows 10 professional, however on my system (Lenovo idea pad yoga Intel i5, my TaskBar, InternetExplorer , Edge , restart and FireFox all became unstable until I switched Hyper V off again.
Related
I have a fresh Windows 10 installation on my MacBook Pro (Late 2016) along with the newest Bootcamp drivers. Everything is working and shiny up until now.
When I install Visual Studio 2017 Enterprise it works up to a point where the reboot takes place. This takes really long, but windows is starting again, for about 7 minutes windows boots while showing the loading indicator. When I'm finally prompted for Login, the MacBooks keyboard and trackpad doesn't work anymore, as we'll as I don't have a wifi connection or audio (having the x sign in taskbar).
I tried the whole painfull process three times now while ending up with the same problem. Windows is broken, which means I can't reinstall the bootcamp drivers (crashes system), no system restore points can be restored (failing), I can't reset windows (breaks the boot process and results in a blank screen). I guess this is somehow related to an intercompatibility between bootcamp and Visual Studio 2017.
I'm not sure if this is related to any specific components of VisualStudio which I install. I'll try a minimal install next...
It was the same for me, Windows 10 was loading 5-8 minutes and no keyboard and touchpad support. After 3-5 re-installs(windows and VS2017), found that issue caused by Hyper-V virtualization. It is disabled by default, but as soon as you installed VS 2017 with at least one component which require Hyper-V, you will never be able to login to you windows on macbook pro.
Just DO NOT install any emulators:
Google Android emulator,
Intel hardware accelerated execution manager(HAXM),
Visual Studio emulator for Android,
Windows 10 Mobile Emulator
And Windows will work fine.
I would like to know if a Windows Phone Silverlight 8.1 app will work without any flaw on a Windows 10 phone. If I need to fix some bugs for Windows 10 phone, can I use VS2013 and a Windows 8.1 machine to fix the issues in Silverlight 8.1 solution?
In general: Yes to both. Windows Phone Silverlight apps will run on Windows 10 Mobile, and you can continue to use Visual Studio 2013 to write and edit Windows Phone Silverlight 8.1 apps.
See Get ready for the Unified Dev Center dashboard preview and upcoming Store changes for store changes you'll need to be aware of and may need to adjust for.
Previously I was using Visual Studio 2012 (including Update 2) with Windows Phone SDK 8.0 in Windows 8. Everything was fine and emulator connected to internet as expected without any additional settings.
But later in same machine I installed Windows 8.1 and set up same environment with Visual Studio 2012 (including Update 2 and 3) with Windows Phone SDK 8.0. Only additional thing was Visual Studio 2012 Update 3 as it is required in Windows 8.1
Now my Windows Phone 8 doesn't connect to internet. It doesn't give any error messages and just doesn't load any web page in mobile internet explorer. I'm using mobile broadband dongle to connect to internet.
There are several discussion regarding internet issue in wp8 emulator but non of them talk about this specific issue comes with Windows 8.1
Is there anyone who had same problem and solved it?
Most probably the bridged connections created by Hyper-V got removed/changed. If suitable I would suggest you remove the WP 8.0 SDK and then install it again and see if it solved the issue.
Optionally you can try to fiddle with the 'Virtual newtork...' adapters in Hyper-V to fix this, but I'm not help there as I didn't manage to solve it that way.
Cheers,
Manuel
It seems only the VS 2013 Remote tools for ARM works on Windows 8.1.
Does this mean that Visual Studio 2012 is obsolete now for WinRT development?
Update on 25 Nov 2013:
Just saw Moche's answer and was about to post the update. Yes VSE2012 on Win8.0 can now remote debug on Surface2 / Win8.1 using VS2012 Update 4 which was released over the weekend.
Also it is required to download the Remote Tools for Arm that are part of the Update 4:
http://www.microsoft.com/en-au/download/details.aspx?id=39305
Click the 'details drill down' to get the 'Remote Tools' Download
To get remote debugging running, you need to right-click on the project file in Solution Explorer and select debugging under the Configuration tab - then you will notice a field with 'machine name'... complete the machine name of the Surface 2 and select Authentication 'Yes' - Ensure both the Visual Studio Computer and Surface 2 are on the Same Workgroup in Control Panel, System, Advanced System Settings, Computer Name Tab. These brief instruction assume you will be using Windows Private lan authentication. If you want to use your live account for authentication simply google how to Remote Debug Visual Studio 2012 with Windows Live Authentication..
When you run the remote tools installation for the first time on the Surface 2 tablet, you will be prompted by a wizard which sets up the necessary exceptions for the Windows firewall on the tablet.
Actually I succeeded to do the debugging on 8.1 using VS2012. I've installed the latest update 4 of the Debugging Tools. Then I went in Windows Explorer to Program Files->MS Visual Studio 11->Common 7->IDE->Remote Debugger>arm and ran msvsmon from there. That's it - I was able to connect to it from my Windows 8 machine running VS 2012.
Yes, it's indeed obsolete.
For windows 8.1 RT development, set up a separate 8.1 machine with VS 2013.
Update
As of Visual Studio 2012 Update 4, remote debugging to 8.1 seems to be available.
The Answer above that 'Its obsolete' pertaining to VS 2012 and debugging on Win 8.1 is (entirely) not correct - the correct phrase would be that Debugging on Win 8.1 client from a Visual Studio 2012 machine is not supported at time of Win 8.1 preview - Hopefully VS 2012 update will soon allow it to connect to Visual Studio 2013 remote debugger tools to allow Windows 8 development to continue between Windows 8 and Windows 8.1..
As Per:
http://weblogs.asp.net/lduveau/archive/2013/07/10/visual-studio-2012-2013-and-windows-8-1-apps-clarifications.aspx
Quoting:
Visual Studio 2012 (running on either Windows 8 or Windows 8.1) continues to support creating and working with Windows Store apps for Windows 8. It does not support creating or working with Windows Store apps for Windows 8.1. Apps targeting Windows 8 continue to work on Windows 8.1, they just can’t take advantage of all of the new Windows 8.1 functionality and performance improvements.
When I read the Answer above I got my knickers in a real twist and then I thankfully found this (and now have hope my shiny Surface 2 isn't a desk weight for developing) -->
quoting off:
http://social.msdn.microsoft.com/Forums/en-US/3e5bd281-4dde-418b-a9fe-078815523fe1/win-81-surface-remote-debugger
For debugging applications on Windows 8.1 Preview RT devices you need to use VS2013 Professional, Premium, or Ultimate Preview with the Remote Tools for VS2013 Preview.
We are aware that VS2012 is not compatible with Windows 8.1 Preview, and we are working to address this with the next update to VS2012.
Thanks,
Dave Lubash
Visual Studio Team
#Carl L - After further digging.. It seems both our answers are sort of right.. To support Win 8.1 currently, you need Win 8.1 and Visual Studio 2013 installed - I tried Installing Visual Studio 2013 Express on my Windows 8 PC and NO DICE..
I guess the only clarification I am adding is that developers can continue using Windows 8 with Visual Studio 2012 to create apps that run on Windows 8 (only) and will also be available in the Apps Store and run compatibly on Windows 8.1 (but not use all the latest 8.1 optimized features). I am only taking this based on MS forum posts.. The information from Microsoft doesn't properly address this point in its documentation at:
http://www.microsoft.com/visualstudio/eng/products/compatibility-2013
Its also worth pointing out that Visual Studio 2013 Express (free version) is not able to produce Windows 8 Apps - ONLY Windows 8.1 apps (so that part of your answer is correct currently). So in a sense it is unsafe to say Visual Studio 2012 is obsolete as it is currently required to support creation of Windows 8.0 apps.. Unless you don't mind ditching App updates for your existing user-base who may not have yet made the jump to 8.1 (not a sound development model and I am very surprised MS is making fragmentation on its own new platforms for developers currently).
At the moment I am a bit miffed that I am forced to upgrade to Windows 8.1 and VS 2013 in order to debug on my Surface 2 (RT) tablet and in that case would not be able to debug Windows 8.0 apps on my Surface 2 (RT) using VS 2012 until MS hopefully updates VS 2012 and/or the VS 2012 remote debugger tools.
Hope that clarifies a bit - seems you were mostly right which is a real shame if Microsoft is serious about attracting developers to its newest OS and having its free development tools rival that of Android OS and iOS..
I would like to know if it is possible to create win 8.1 apps with WinJs 2.0 (where the hub, search, back button, etc is included) on a machine with Windows 8 or do i have to install the preview of Win 8.1?
You need the preview of Windows 8.1 along with the version of Visual Studio for it.
You need to install preview on Win 8.1 as WinJS 2.0, relies of features introduced in IE 11 (mutation observers etc).