Can I use windows 8 to install and use Microsoft Hololens? - visual-studio

I need to work on unity 3D and Hololens to predict and map the movement of a machine.I wanted to ask is it possible to use Hololens and trace the movement of a machine by using windows 8? I would also appreciate if anyone could help me with the total installation procedure of how to install and use Hololens since I am new to it.I found some installation guides but that requires Windows 10 and since I have windows 8, anything related to it such as which packages to install, would be very useful.Thank you everyone for your time.
Best Regards
Safayet

Can I use windows 8 to install and use Microsoft Hololens?
No, you can't.
To build for Hololens you need UWP and UWP needs the requirements below:
Unity 5.2 or later
A Windows 10 Pro, Enterprise, or Education (The Home edition does not support Hyper-V)
Visual Studio 2015 RTM, (the minimum version is 14.0.23107.0). Please
note that earlier versions, for example Visual Studio RC, are not
supported in Unity 5.2.
You’ll also need to install the Windows 10 SDK.
8 GB of RAM or more
The source for this information from Unity's blog. In short, you can't because the SDK requires Windows 10.

Related

Can Visual Studio 2017 be installed and used on Windows 10 on ARM (i.e. Asus NovaGo)?

I am struggling to find information on this. Of course certain features such as docker and hyper-v will not function, but will Visual Studio 2017 be able to be installed and run on a Windows 10 always-connected ARM device? Like, would typical desktop/web development scenarios with .NET/C++/Python work?
Cheers.
Yes, it is possible. I just got a Asus Nova Go and tried it. Compiling and running a basic .net Core app (with an Avalonia UI) worked just fine but there are some limitations and corner cases that hopefully will get fixed.
Visual Studio takes long to launch, and when lauched is not very performant.
I think the Lenovo Yoga C630 is snappier, because of the bigger 8GB RAM and the Snapdragon 850.
If you have any further questions let me know

Can I develop Windows 10 App on a Windows 8.1 device?

I would like to follow the guide (http://microsoftedge.github.io/WebAppsDocs/en-US/win10/CreateHWA.htm) to develop a Windows 10 app, but it says it needs the Windows 10 Insider Preview as the requirements. However, I cannot download it right now as it states that:
We’re very close to the public release of Windows 10 so we’re not onboarding any new PCs to the Windows Insider Program just now.
Can I now have any ways to develop a Windows 10 App? I want to finish making it so that it can be out once Windows 10 is released. Thank you!
You can develop Windows 10 apps with Windows 8.1,too. You need Visual Studio 2015 to and the latest Windows SDK. In the future you will be able to develop from Windows 7, too. (Both has been announced at the build conference in San Francisco.)
There will be some limitations - you can't deploy your Win10 app to your local system, as you are running W8.1 locally. (But you could use a remote or virtual machine).
There will also be some limitations around the XAML designer.
The easiest way is probably to start developing on a remote machine in the cloud. Here's a guide how to set things up: https://github.com/DanielMeixner/DevDreamMachine
As we are getting closer to release of VS2015 and W10, please check out this post, too. There are some limitations around app development between release of VS2015 and release of Windows which might affect you.
http://blogs.windows.com/buildingapps/2015/06/29/release-dates-and-compatibility-visual-studio-2015-and-windows-10-sdk/

Can I bypass hyper-v with an earlier version of visual studio

I installed visual studio express 2013 on my windows 8.1 computer. Everything was fine until I learned that I needed 8.1 pro to have hyper-v to use a phone emulator to run my program. (I think)
Rather than downloading a new operating system, would I be able to use an earlier version of visual studio? If so, which one...
I am very new to phone development and (considering I can't get past the installation stage) would appreciate the simplest explanation out there.
Thanks!
Sadly, no. Hyper-V is a requirement for WinPhone emulation, and it requires Pro, no matter what version of VisualStudio
Note: To use the Windows Phone 8 emulator your PC must have Windows 8
Pro or greater and a processor that supports Second Level Address
Translation (SLAT).
https://www.dreamspark.com/student/Windows-Phone-8-App-Development.aspx
http://msdn.microsoft.com/en-us/library/windows/apps/ff626524(v=vs.105).aspx
However,you can easily upgrade to Pro, see http://windows.microsoft.com/en-us/windows-8/feature-packs You just buy an upgrade key and enter it, you don't have to go through the whole install a new OS process

Windows Phone 7 emulator doesnt work properly and just flickers

Windows Phone 7 emulator doesn't work properly on my laptop.
It just flickers instead of starting my app. Clicking on any of the buttons has no effect. (None of the emulators work, tried 256MB, 512MB, and the ones installed by WP 7.8 SDK Update) WP 7.8 SDK Update didn't solve anything.
I'm using a Samsung NP300E5A-S06 notebook, and it has:
Core i5 3210M 2.5Ghz
Intel HD Graphics 4000 + GeForce GT 620M
6GB of RAM
Here is a video of what's happening on my machine.
I heard this can be caused by the Intel HD Graphics 4000. But we can't force WP Emulator to use the GeForce.
How can I make the WP7 emulator work properly?
If you have any idea or a working solution, please help me!
Thanks in advance!
First, download and install the latest GPU drivers for both GPUs. If it will help, you're lucky: I had something very similar on machine (dual GPU Intel + NVidia as well), and was unable to find a fix.
My advice - upgrade to Windows 8, install visual studio 2012, and WP8 SDK. Fortunately, with the recent version of the SDK you can still build for the previous WP 7.1 platform. And even if xde.exe still won't work on your laptop, you can test and debug the application you're building on new HyperV-based WP8 emulators.
sorry, I cant comment.
Did you try repairing the installation?
Also completely removing and then re-installing?
EDIT:
Also you can try running it on a virtual machine on your laptop (Maybe there is some problem in your Windows installation - after all its Windows ;) )
i think i have had series of problems with that emulator months ago, but now, all is just well. i have some questions for you.
1) Which version of Visual Studio are you using. i believe it should be visual studio 2010
2) have you installed visual studio 2010 service pack 1? if no, try to download it and install
3) which version of .net framework are you using? Visual Studio installs .net3.0 automatically but i guess you have to install the service pack 1 too. you can download it or get it from windows update. in the update settings, choose"check for updates but let me choose which to download and install" then check the two or three check boxes below. then click okay and check for updates. you will then install updates for visual studio 2010 and .net framework.
those should help.

Windows Mobile SDK 6 Confusion

I am upgrading my Windows Mobile 5 project to a Windows Mobile 6 project.
The first step (at least so it seems to me) is to get the Windows Mobile 6 SDK installed.
When I went searching for this I found the following installs that both seemed to fit what I was looking for:
Windows Mobile 6 Professional SDK Refresh.msi
Windows Mobile 6.5 Professional Developer Tookit (USA).msi
So, the question is, do I need these both? and if so, what order do I install them in? and is there any other installers/steps I am missing?
It depends on what you're targeting. There are loads of SDKs, but generally what they bring to the table are emulators and SDK-specific stuff (like additions to the Microsoft.WindowsMobile namespace). Otherwise they really don't do a whole lot. For example you can continue to use just the PPC 2003 SDK to write and deploy apps on WinMo 6.5, you'll just be missing availability of the stuff that was added to be 6.5-specific.
Persoanlly I'd recommend installing the 6.5 Pro (and maybe standard too) SDKs and foregoing the 6.0 SDK unless you need to do emulator testing for something like a 6.0 or 6.1 device.

Resources