Motorola EMDK for Visual Studio 2013? - motorola-emdk

So, now that Visual Studio 2013 supports the Compact Edition AppBuilder.. Does anyone know where to find the right EMDK or how to create a new solution for a Motorols/Symbol MC9090 ?

The Motorola/Symbol EMDK for .NET only is only supported up to VS 2005/2008 since Windows Mobile SDKs only have support up to VS 2008.
This is the most recent EMDK release, check the release notes for installation requirements: EMDK for .NET
Update: Fixed link to new support site.

We still use Visual Studio 2008 for our EMDK development, however, I believe Microsoft has added .NET 3.9 support for Visual Studio 2015.
While the EMDK doesn't support Visual Studio 2015, the references would still work you just wouldn't have the toolbox objects. Not sure how big an issue that would be for you but we've never used them!
So if you started a new project, you should be able to select the EMDK dlls required for your project if you have the EMDK installed on your machine. You will need to select the correct processor architecture for your device (I'm guessing armv4i as most Motorola kit seems to be this)
You also may need to work with .NET 3.9 exclusively which might give you a headache getting that onto the MC9090. You'll not only need to install but you'll need to make it stick for a cold boot. This will either need a platform build or some very creative splicing of the .NET 3.9 CAB file and some SymScript! :)

Related

Install WinCE 5.0 Platform Builder SDK - build code with Visual Studio 2012 or higher

I have a Windows CE 5.0-based Platform Builder image. It is intended to be installed on Visual Studio 2005. My team would like to upgrade our build tools to utilize Visual Studio 2012, but Visual Studio 2012 does not support this platform image.
To be clear; I am not asking whether or not Visual Studio 2012 (or higher) supports Platform Builder SDKs targeting Windows CE 5.0. That question has already been answered (more or less), and the answer is clearly "No."
Instead, what I'd like to do is install the Platform Builder SDK, and manually modify the Visual Studio 2012 environment to allow compilation of my Windows CE code. Features like remote debugging and deployment are acceptable losses to my team; we have our own pathway for deployment and debugging on our embedded device. What I'm really hoping to gain is simply the ability to build WinCE 5.0 code in VS2012, which was intended for VS2005. I am attempting to reduce the number of Visual Studio installations, and get access to the superior intellisense faculties of newer versions of Visual Studio.
Does anyone know if this is possible? How would I go about doing that?
There does not appear to be a way to do this, in such a fashion as to no longer require Visual Studio 2005.
You can, however, use registry hacks to force Visual Studio 2012 to build a WinCE 5.0 project by utilizing the compiler binaries from Visual Studio 2005, during compilation. This would allow you to develop code in VS2012, but would also require that VS2005 be installed for a successful build.
Here is an article explaining the steps to set this up.
VS2012 doesn't have any of the Windows CE compilers. The last one that shipped with compilers compatible with CE 5.0 was VS 2008, so that's the "latest" version you'll be able to use to build. (VS2012 is capable of building for Windows CE, but only for WEC 2013, and only after installing a WEC 2013 SDK, which includes the requisite compiler pieces).
In short, there's no way you can get VS2012 by itself to compile a CE 7.0 or earlier app.
There is a plug-in for VS 2013 that will allow you to use that IDE for managed code (I've never used it, so I can't say how well it works), but it still requires VS 2008 to be installed to get the compilers.

New Laptop - Any reason to install Visual Studio 2012 AND 2013?

I've just been given a new work laptop and have an MSDN subscription. My old laptop had VS 2008, 2010 and 2012. I'd rather not install all of these again if I can avoid it. My main question here is whether there any reason to install VS 2012 if I have access to VS 2013? I believe Projects & Solutions are compatible, what other reasons might there be for installing VS 2012 (and for that matter VS 2010) again? If I have an MVC 3 app created with VS2010, will it be possible to open and work with that in VS2013 without having to "upgrade" the project type?
It really depends on what kind of projects you are working on. Each new releases of VS in fact remove certain features.
http://msdn.microsoft.com/en-us/library/vstudio/hh266747.aspx
ASP.NET MVC 3 is not supported by VS2013.
Lex' answer is pretty good. I'd also like to add that if you are using C++/CLI, upgrading to Visual Studio 2013 will force you to target .NET 4.5, which might not at all be desirable if your users only have .NET 4.0 etc.
You can still target the older frameworks, by letting VS2013 use the older "Platform Toolset" from e.g. VS2010 or VS2012, but this will force you to have either one of these installed. I am using this exact scenario (VS2010 + VS2013) and it works quite well. (I have only VS2010 and 2013, not 2012 in that specific virtual machine.)
Update: Here is a MSDN page which backs up my statement about C++/CLI, just for the reference.

Does the Honeywell D6X00 WinCE5.0 SDK work with Visual Studio 2010?

I'm planning to develop an application targetting the Honeywell Dolphin 6100 running Win CE 5.0. The documentation for the platform SDK and device SDK say that VS2005 is required to use them.
I don't have a copy of VS2005 and since it's not sold or supported by MS any more, I'd much rather buy VS2010. Does anyone know if the Honeywell D6X00 SDKs are compatible with VS2010?
Thanks for your help!
Matt
You can get access to VS2005 or VS2008 by purchasing VS2010 Pro with a MSDN subscription. You can then download old versions of VS and other stuff from the MSDN site. This is the path I have taken as there is lots of info on the web about how VS2010 does not support Win CE 5.0. If you plan to only write straight C++, you can use embedded visual c++ 4.0 which you can download for free from MS. If you have a lot of UI code, you may want to get VS2005.
Good luck.
Visual Studio 2010 removed support for developing Windows Mobile devices (instead replacing that with support for Windows Phone) - you would need to get hold of Visual Studio 2008 (or 2005, as you mention), which should still be available.

What Visual Studio for .NET 1.0 web development?

I have a old web application developed in .NET 1.0. How can I do some minor changes in it? What Visual Studio do I need and how do I obtain it? Or can I develop in some other tool?
Thanks in advance!
It was called VisualStudio.NET, followed by Visual Studio 2003 (also known as version 7.1).
I don't think this is available anymore, unless you have a pro MSDN subscription or above.
Visual Studio 2005/2008/2010 cannot be used for this, nor can mono-develop, but you might be able to use the version of SharpDevelop that supports 1.1.
You'd need Visual Studio 2002, it targeted .NET 1.0. That edition didn't last long, Visual Studio 2003 and .NET 1.1 quickly followed. Your project should have good odds opening and running properly on that edition. Odds get lower once you move to VS 2005/8 and .NET 2.0+
If you don't have VS2002 then you can obtain a license through an MSDN Library subscription. An auction site like Ebay is a cheaper alternative.
It was originally called Visual Studio.NET but later on also got referred to as Visual Studio 2002.
I looked it up and apparently you can still download it if you have an MSDN subscription.
You can use VS 2005, VS 2003, or VS 2002. I think the 2002 edition was called VS.NET.
From http://weblogs.asp.net/scottgu/archive/2007/06/20/vs-2008-multi-targeting-support.aspx
What about .NET 1.0 and 1.1?
Unfortunately the VS 2008 multi-targeting support only works with .NET 2.0, .NET 3.0 and .NET 3.5 - and not against older versions of the framework. The reason for this is that there were significant CLR engine changes between .NET 1.x and 2.x that make debugging very difficult to support. In the end the costing of the work to support that was so large and impacted so many parts of Visual Studio that we weren't able to add 1.1 support in this release.
VS 2008 does run side-by-side, though, with VS 2005, VS 2003, and VS 2002. So it is definitely possible to continue targeting .NET 1.1 projects using VS 2003 on the same machine as VS 2008.
Take a back up of your project.
Try to down load visual studio express 2008 version and open the project. you will have an option to convert. Once converted download the latest visual studio express and then convert into the latest version.
BTW Visual stuido express is FREE
Note:
Some of the methods may not be supported or droped. you need to recode them or replace them.

If I have Both Visual Studio 2008 and 2010, do have I have to keep both

I recently downloaded VS 2010 trial, the new version is more easy to use.
I have VS 2008 installed, If i decide to use VS 2010 in the future, do I still have to keep VS 2008? Is there any compatibility issue with it?
You would need to keep VS2008 installed if you target Windows CE (via Compact Framework, native smart device projects, etc.)
http://msdn.microsoft.com/en-us/library/sa69he4t.aspx
Also if you want to write native applications that run on versions of Windows before XP SP3 and Server 2003 SP2, this is no longer possible with VC++ 2010. The same applies to managed code written for the .NET Framework 4.0, but you can still use Framework 3.5 with VS2010 for projects with managed code only.
And Intellisense for C++/CLI code is gone (MS promises to remedy that in the future, whether a service pack or the next version I cannot say).
If you open a VS 2008 solution or a project in VS 2010 it will be converted to VS 2010 and you will not be able to open it in VS 2008.
If that is not a problem then you don´t have to keep VS 2008, unless you are using a addin or some other third party application with VS 2008 that is not compatible with VS 2010.
Edit:
Look at Ben Voigt´s answer for information for which version have support for different platforms.
VS2010 allows you to specify the target framework that you'd like to develop on. There should be no reason to keep VS2008 installed unless you've become accustom to some handy plugins :)

Resources