I know it's possible to switch to a different "Platform Toolset" in Properties. Since I want to keep VisualStudio 2010 (plugins, etc) but also want to use C++11 features, how can I add a newer compiler version? The windows sdk does not come with a build pipeline anymore. I tried installing VisualStudio Express 2013, but that didn't help. I know I could just use the Express version, but I have several Plugins (EA, CodeXL) that I bought for VisualStudio2010.
Any hints would be appreciated
Related
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! :)
Autodesk mentions here that AutoCAD plugins need to be developed with a particular Visual Studio version, e.g.
AutoCAD 2016 (supports Microsoft Visual Studio 2012 and 2013)
AutoCAD 2015 (supports Microsoft Visual Studio 2012)
...
Why is it like that? I understand that you need to use particular .NET Framework versions according to your AutoCAD versions.
But why the IDE? You can set your target framework version for each project.
Is it because of compiler / debuger issues?
We are planning to upgrade from AutoCAD 2012 to AutoCAD 2016. So we need a new IDE for our plugins and would prefer the latest Visual Studio version (2015)
This strict VS version is for ObjectARX/C++ only.
For .NET you just need the proper framework version to develop or, if you already have a DLL, legacy compatibility should work. But there is an exception, see below:
AutoCAD 2007 - 2012: compile your code with AcDbMgd and AcMgd and your code should work on all these versions (except if you use a feature that is not available on the version you're executing)
AutoCAD 2013 - 2017: this 'new cycle' also need reference to AcCoreMgd, therefore you need a separate compiled DLL
For C++ there is a additional requirement regarding Decorated Names and VS compiles the code using this. Therefore you can adjust the Toolset, but need the specific version installed to compile your code.
I might say that if you're using ActiveX/COM you have some different concerns: the references are different on 32 and 64 bit and between AutoCAD major versions, so it's easier to use late-binding or compile different DLLs for each version/platform.
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.
In our company for software development we are mainly using VisualStudio 2010 (Platform toolset v100).
We ran into a situation where we needed to work with some poorly organized third party SDK that was compiled using VisualStudio 2008 (V90) and this SDK can't function normally while working in the "v100" platform toolset.
What I mean by "poorly organized" is.. imagine for example an SDK export functions that has something like a "std::string" in it.
The solution was to create a "wrapper" dll that we compiled using VS2010, but with a "Platform Toolset v90" option. But for "Platform Toolset v90" to work, we needed to install a VisualStudio 2008.
My question is: Is there any legal way to use v90 platform toolset in VS2010 without buying VisualStudio 2008? Maybe there is some kind of v90 "toolset package" or something that we could use?
Thanks.
As user1240436 stated in his comment, it should also be possible to install the Microsoft Platform SDK. I think v6.0 and higher contain the VC 9.0 and its environment.
As far as I know, it should be possible to use the Visual C++ 2008 Express Edition
It just has to be installed on the compiling machine, everything else could be done via VS2010. (This way you could also build multi project solutions etc)
Where does Visual Studio identify its version. E.g. As Express, Standard, Professional, etc?
For example, the Express version does not support extensibility through add-ons. How do add-on authors prevent against their product being integrated with the Express version?
If you're talking about a VSIX plug-in, then see e.g.
http://blogs.msdn.com/b/visualstudio/archive/2010/01/19/using-the-vsix-manifest-editor.aspx
The VSIX manifest declares the editions it can be installed into.
How do add-on authors prevent against their product being integrated with the Express version?
They don't need to. Microsoft have disabled the functionality that looks for plugins. So even if it gets installed the Express version doesn't go looking.
There may well be hacks you can do to get the Express versions to load plugins, but if that's the case people will probably try to hack your plugin too.