I'm trying to set up some new developers to make apps for the Okuma control using the Okuma API and SDK. What environment should they use? I tried installing Visual Studio Express 2012 but it keeps giving an error looking for files during install. Also, what language should they use so they can work with the Okuma API?
The Okuma API is written using .NET 4.0 so you really have several options.
Normally I'd say Visual Studio express 2012 for desktop is best but I've seen problems putting it on Windows XP.
If you're using windows XP and aren't ready to invest in a full version of Visual Studio yet, I'd recommend Visual C# Express 2010. If you're more familiar with VB and don't want to switch, do the VB express verison.
All these (and the professional version) are available from
www.microsoft.com/visualstudio/eng#downloads
VS 2019 community edition is currently working fine for me doing this. I just have to choose which .net framework in the project settings. That was not listed in the prior answer in case anyone comes across this in the future.
Related
My question is What is difference between Visual Studio Express Edition for Desktop and
Visual Studio Community version?
I want use VS to create Desktop apps, currently I have ultimate version of VS2013, but I think mentioned versions are lighter and faster and FULL FREE for me because I don't use most of developing features like Team server or Testing tools or IntelliTrace, .... I want know the mentioned versions have full Windows API Support (Header files definition) like Ultimate/Enterprise versions?
Don't forget my first question: VS Express for Desktop vs Community, because both are FREE.
Community edition is the full fledged software, but you can't use it on enterprise (>5 users)
On the other hand, Express editions can be used in enterprise environments, but does not let you use plugins.
So in the end, as far as I can tell the choice is between plugins and enterprise. If it's just a product you are developing yourself, or an open source software, Community edition would be your best bet. On the other hand, if you want to try out the latest version at your work for free, then Express edition is for you.
Here is from the "source" :)
Differences between Visual Studio Community Edition and Express Editions
Here is a quote from that MSDN blog:
There are two main differences between Visual Studio Community Edition
and the Express Editions
1) Visual Studio Express Editions do not allow users to use extensions
(aka. plugins). There are over 5000 great plugins for Visual Studio
in Visual Studio Gallery. Plugins such as Developer Assistant can
boost developers’ productivity. Unfortunately, they are not available
to Visual Studio Express users. With Visual Studio Community
Edition, you can access and use All of them!
2) Visual Studio Express Editions are targeting specific platforms:
Express for Web allows you to develop Web apps; Express for Windows
allows you to develop Windows apps; Express for Windows Desktop allows
you to develop desktop apps. But with Visual Studio Community
Edition, you can develop projects targeting cross-platforms.
Community is like a full version of Visual Studio Professional, only they don't allow you to develop for commercial purposes (through the licence agreement). With the exception for developing apps that you sell in the Windows Store.
Why you would want Community (dito for VS Professional):
You can develop a mix of different projects in the same solution on the same IDE. With Express you develop asp.net and other web apps (Express for Web) in different IDE's than you would developing a Windows Forms applicaiton (Express for Win Forms).
You get full access to plugins that enhance the IDE, like code optimisation tools.
Other than Professional, Community is integrated with a lot of online collaboration sites. Like integration to GIT repos and Windows Azure hosting.
Express is like the old school express versions, if you used to use the old school express versions, you probably want to stick to it. It allows for commercial development, but they restrict the features of the IDE. And they make it harder to use by splitting the IDE to only handle Web Applications (like ASP.Net) in one IDE and a different IDE for handling Windows Forms. (In the past they also split the Win Forms IDEs to only handle one coding language like C# or VB).
Here is the official comparison
I think IntelliTrace is the most important part missing in the community edition. Cloning the repo some similar things are missing. but I don't think those are any real problems.
I am trying to create test case in C# for the WDF drivers of Smartcard devices. but i could not find the Windows driver > Windows Driver Test template under installed Visual C#. I am using the Visual Studio 2013 for Windows Desktop. i could not even find the Windows Driver Test in online template. Any other package i need to install?
You might be running into problems because of the version of Visual Studio that you're running: VS 2013 for Windows Desktop is essentially an "Express" edition of VS put together to provide developers with a basic IDE for building Windows desktop apps for free. The Express SKU's of VS were, however, limited in their functionality and do not support add-ons and additional SDK's, project templates and/or tooling such as WDK. For that you'll likely need a Pro edition of VS.
Note: Microsoft has recently released Visual Studio Community Edition which is a full release of VS Pro, including add-ons and extensibility, but free for non-commercial use and/or dev teams of up to 5 people. If you meet these licensing requirements, then you may have more luck using VS Community Release than VS for Windows Desktop.
For past express editions, I've been able to find a "compare editions" page that shows what features are available in express, professional, ultimate, etc. Something like this.
However, every comparison table I've seen so far omits the express editions. Surely Microsoft must have a list of things you get by upgrading to Visual Studio Professional from an Express Edition--after all, it's a free product, and they would like you to upgrade to a paid product! So, where have they hidden this feature comparison table, or "reasons to upgrade to Professional" list?
As far as I know there is no single table with a summary.
It depends on which version of express your talking about. Express is split up into a lot of different SKUs based on the type of product you're building; Web, Phone etc. Which is probably why there isn't an entry on this table for Express. 2013 was a point release to 2012 and there is a comparison of Express Web 2012 to Pro on MSDN.
The biggest single difference is that you cannot run plugins in Express. This means no Resharper, Test Driven .NET etc. This also applies to some plugins that you might consider to be written my Microsoft because they were not part of the official Microsoft release, for example plugins written my various other groups. This is a long-standing gripe for users of Express and looks like it is still the case for 2013, How to install Nunit plugin in Visual Studio 2013 Express?.
I was very surprised when I downloaded Visual Studio 2013 Express Edition for web development on my new Windows 8.1 machine, and it was starkly different from what I believe is the identical product that I have been using for a while on a Windows 7 machine.
For example, when creating a very small demo app using Web API (from the asp.net website), the "New ASP.Net Project" wizard did not offer Web API. And the new project did not include the App_Start folder, which would include code for things like routing.
I tried to use NuGet to add the essential features, but no luck. That tutorial only took a few minutes on Windows 7, but was a miserable failure and an hour I will never get back on Windows 8. I don't really understand Microsoft's strategy here.
From what I observed Visual Studio Express 2013 doesn't come with a 64-bit compiler.
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC>vcvarsall.bat x64
The specified configuration type is missing. The tools for the
configuration might not be installed.
And since the Win 8 SDK doesn't provide compilers anymore either, it appears like you must pay for Visual Studio 2013 Pro or you won't be compiling 64-bit binaries.
"The Windows SDK no longer ships with a complete command-line build
environment"
https://dev.windows.com/en-us/downloads/windows-8-sdk
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.
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 :)