Support for lone installs of VS2013

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install VS2013 (Non-Express version)
2. Run vs-android install script for vs2012
3. VS2013 does not recognize "Android" platform

What is the expected output? What do you see instead?
As soon as a project is opened, warnings appear about the Android 
incompatibility. I expect to see no warnings and mainly, to be able to build 
the solution.

What version of the product are you using? On what operating system?
VS2013 - Windows 8.1 - 64-bit

Please provide any additional information below.
I tried to change the install script and the platform targets and all files of 
vs-android from 11.0 to 12.0. Also tried to recompile the vs-android dll, but I 
am not expert in C#, and I was not able to solve the arising issues.

Original issue reported on code.google.com by camil...@gmail.com on 23 Nov 2013 at 8:15

[GoogleCodeExporter]

Original comment by gavin.dj.pugh on 3 Jan 2014 at 6:20

• Changed state: Accepted

[GoogleCodeExporter]

I've just uploaded a new version which has support for VS2013.

Unfortunately they changed the MSBuild script setup significantly. They have 
backward compatibility with the 2012 script setup, which I'm taking advantage 
of. This means though that VS2013 alone installed on a PC won't work. You'd 
need 2012 installed alongside it. I would image VS2012 express would work fine, 
but I haven't tested it.

Support for lone VS2013 installs will have to be something provided by the 
community, which I'd be happy to integrate. I can't see myself spending time on 
it anytime soon.

Original comment by gavin.dj.pugh on 4 Jan 2014 at 8:28

• Changed title: Support for lone installs of VS2013
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I was able to get this working with a few minimal modifications:

1. Copy the Android folder into C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Platforms

2. Set ToolsVersion="12.0" in all *.targets files.

3. I renamed the following files:
       Microsoft.Cpp.Android.default.props -> Platform.Default.props
       Microsoft.Cpp.Android.props -> Platform.Default.props
       Microsoft.Cpp.Android.targets -> Platform.targets

I tested this by removing the old vs-android files from the C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Platforms directory and it seemed to work 
in VS2013.  I haven't fully uninstalled VS2012 though.

Original comment by t...@lindenlab.com on 12 Mar 2014 at 10:21

[GoogleCodeExporter]

@ted@lindenlab.com : Great! Thanks for that!

Next time I do a release, I'll give it a shot on a lone-install setup. Then 
roll it into that version if it's all good.

Thanks!

Original comment by gavin.dj.pugh on 12 Mar 2014 at 10:32

[GoogleCodeExporter]

the two lines below don't sounds right?

Microsoft.Cpp.Android.default.props -> Platform.Default.props
Microsoft.Cpp.Android.props -> Platform.Default.props

Original comment by wael72da...@gmail.com on 26 Mar 2014 at 12:31

[GoogleCodeExporter]

I rewrite a version from v0.961 based on @ted@lindenlab.com mentioned solution, 
plus some more modifications:
1. Rebuile 'vs-android.Build.CPPTasks.Android' from VS2013.
2. Fixed the issue in Build Events not properly executed.

I already tested for lone installs of VS2013(in the new installation of windows 
7 64bit), and it works find.

Original comment by mell...@gmail.com on 30 Mar 2014 at 3:34

Attachments:

• vs-android-src_vs2013.zip

[GoogleCodeExporter]

@mellean Thanks! I'll hopefully get both your fixes in the next version update.

Original comment by gavin.dj.pugh on 3 Apr 2014 at 6:33

[GoogleCodeExporter]

Fixed with v0.962

Original comment by gavin.dj.pugh on 10 Jun 2014 at 5:45

• Changed state: Fixed