The docs state that developing for the Azure Sphere device requires
A PC running Windows 10 Anniversary Update or later
and
Visual Studio 2017 Enterprise, Professional, or Community, version 15.7 or later
Is there a way to develop for the device on macOS?
Currently there is no VS code support for Mac OS. You will need to use Window 10 Anniversary update or later.
You can open a feature request for the Azure Sphere team to enable Mac OS support here.
Related
I am trying to get started on application development for my Motorola MC32N0 device running Windows Embedded Compact 7.0.
This tutorial explains that I need a Board Support Package (BSP), however I am unable to find this on the Zebra website. Is a BSP available for the Motorola MC32N0, and where can I find it?
Another question, during the installation of Platform Builder 7.0 I used a trial license key. Now if I deploy the build output to my device, will it replace the OS that is already installed, or will it just deploy the application?
I am new to Windows CE, but have a background in web development and WinForms.
For C/C++ application development, Visual Studio 2008 and the Motorola SDK will suffice.
BSP's on the other hand are for developers working on low-level code such as the kernel OAL and device drivers. Platform Builder 7.0 is a plug-in to Visual Studio 2008 that enables building and debugging BSP code, and is not required for application development either.
If you only intend to develop C# applications, you may not even need the Motorola SDK, but could target just a generic Windows CE device in Visual Studio.
According to system requirements I can install SDK only on Windows 8 machine (I need support Windows Phone 8 platform too).
I want to create build server for WP applications, so can I use Windows Server for that?
I install WP SDK on my Windows Server 2012 without any problems.
Did you have any troubles?
PS. But as I know not all CPU are compatible.
This might be a stupid question, but I couldn't find the answer anywhere. Does the Microsoft Surface SDK 2.0 only work with Microsoft Surface products, or can I use it with other touchscreens? I really just like the way the SurfaceTextBox control works (popping up a onscreen keyboard when clicked) and was wondering if I could use it in a program I'm making (which uses a Elo touchscreen monitor, not multi-touch).
Edit
Thanks for the responses. I downloaded and installed the SDK 2.0 and tried to run the sample apps that are included. They don't seem to respond to my finger touches but do work if I the included simulator. I'm running this on windows 7. Any reason why it doesn't seem to work on my touch screen?
Yes, you can use it with any touchscreen. It works on WinRT/Windows 8 as well as Windows 7. I have used it for surface, tablet (both WinRT as Win7 tablets) and touch-enabled desktop applications and it works absolutely fine.
The installer requires you to install Visual Studio 2010, but if you import the DLL's manually in the toolbox, you can also use it in both Visual Studio 2012 and 2013 preview. This is an answer on a different question, answered by one of my colleagues on how to use the Surface SDK 2.0 with Visual Studio 2012
It's a great toolkit to support touch-enabled WPF applications and can also be use as a replacement for the WinRT Metro UI, in case you cannot use that toolkit (e.g. when you interface with USB, or need desktop services).
Update:
Since you update your question to how to get the Elo Touchscreen to work with native Windows 7 touch, I suggest you download and install the latest drivers. Your touchscreen will only work with WPF touch / Surface SDK if native Windows touches are supported. Installing the latest drivers should do the job. Don't forget that you might have to enable and configure touch input in the Control Panel (Pen and Touch).
I noticed that in some cases touches are not working when you use a SurfaceWindow. Use a normal WPF Window and all the SurfaceControls should work. Thus if you want to use the sample applications on Windows 8 you need to replace SurfaceWindow with Window and remove the unavailable EventHandlers.
From Microsoft's web page:
http://msdn.microsoft.com/en-us/library/ff727815.aspx
The Microsoft Surface 2.0 SDK provides the managed APIs and the tools you need to develop Surface applications. Applications that are built using the Surface SDK can run on devices made for Surface 2.0, and on Windows 7 computers.
See also:
http://social.msdn.microsoft.com/Forums/en-US/b61c2eda-410e-4c65-9a60-b9e0a8ea11b2/windows-surface-sdk-setup-and-development-on-the-tablet-windows-rt
Surface SDK 2.0 is not dedicated to Windows RT for a Surface Tablet. it
is innitially dedicated on PIxelSense SUR40 unit or if you are bulding
windows 8 application with Pro version.
There has been a lot of confusion since the arrival of the Surface
tablet. The product name Surface before what the name of the Microsoft
Table touch table and the Samsung SUR40 device.
And that SDK was only working on those device. Then MS has release a
version (Surface SDK 2.0) which can be use also fro traditionnal Touch
PC application starting from Win 7.
Finally:
http://www.infoq.com/news/2011/07/Surface-2
With Microsoft Surface SDK 2.0 one can write applications for both
Surface and Windows Touch devices.
Surface 2.0 is not compatible with Surface 1.0 devices, and so far the
only compatible device is Samsung SUR40 [as of July 2011]...
These details have been public for a while, but Microsoft has just
made available Surface SDK 2.0. One of its key features is the ability
to target Windows Touch devices, that is Windows 7 computers with
touch input, so this SDK serves a much larger spectrum of devices. If
there are very few Surface devices out-there, there are lots of
Windows Touch ones, and their number is poised to grow.
Windows Touch applications are very similar to Surface ones, except
that the later supports full HD resolution and a multitude of touch
related inputs, such as finger and blob recognition, tagged objects,
tilted display, rotated display, etc.
At windows 8 you just need do that:
Run Microsoft Surface Input Simulater
Go to Device Manager
In Human Interface Devices, right click over Touchscreen compatible with HID and click activate.
Just that. ;)
I know that the SDK is not finished, yet a few lucky developers have got their hands on it already, so here's my question: when you installing Windows Phone 8 SDK, did it install the SDK in Visual Studio 2010 also, or just on the 2012 edition (including 2012 Express)?
After posting my question, two different developers that had access to the SDK contacted me directly stating that there is no integration of the Windows Phone 8 SDK in Visual Studio 2010, just on the 2012 version.
No, You need Visual Studio 2012, Windows 8 Pro or Enterprise x64 + processor supporting SLAT for running Hyper-V.
You can now download the WP8 SDK here:
http://www.microsoft.com/en-us/download/details.aspx?id=35471
There's no emulator for Windows 8, so in order to develop metro apps I must install the release candidate on a device and run Visual Studio there, right? That's what this page seems to suggest, but I just wanted to double check.
Yes, Windows8 is required.
However, VM can be used. For example, I'm running Win8RP/64 and VS2012RC in Oracle VirtualBox on Win7/64.
NOTE: For developing Metro Style App, you should NOT install VirtualBox Extension Pack.
Yes, you need Windows 8 to develop Windows 8 Metro style apps.
Metro Style apps rely on a new set of APIs which are implemented only in Windows 8 through the the Windows Runtime (WinRT).
There is no emulator for Windows 7 and not even for Windows 8... Windows 8 has a simulator which in practice is just a Remote Desktop session to the same machine. It is not an emulator.
While Windows 8 is not in its final version, what I recommend is to install Windows 8 in a VHD (virtual hard disk) and boot your PC directly to the VHD. It is faster than running virtual machines (because only the disk is virtual, all the rest is real hardware) and you can keep your Windows 7 intact.
This is what I've been using since Developer Preview. I have a dual-boot configuration being one for the Windows 7 that is booting from the regular disk partition, and one Windows 8 that is booting directly from the VHD on disk.
Metro UI style is just a design approach and some guidelines. You are free to implement such interface using Visual Studio 2010 as well as 2008. Using C# and WPF everything is possible. But, indeed, new Visual Studio has a set of Metro style components (WPF) with which your development process will be much more quicker.
The only thing you can't use at OS other than Windows 8 - is WinRT subsystem.
Almost all of the development tools needed to build Metro style applications can be run on OS's other than Windows 8 (Visual Studio and the package creation tools require Windows 8). So it should be possible to set up a build environment using msbuild.exe (or even make/nmake) that will compile and link metro-style applications on an OS other than Windows 8.
However some parts of development MUST be done on Windows 8 - the tools for some of the steps of development will only run on Windows 8.