Hey guys i wanna setup cocos2d version 3.0 for windows. Currently I am using visual studio 2010 and cocos2d 2.2.2 for building apps. As cocos2d version 3.0 released so i want to upgrade cocos2d 2.2.2 to cocos2d 3.0. Is cocos2d 3.0 stable version released? and how can i integrate it with visual studio 2010.
Yes, Cocos2d-x v3 is officially released: http://cocos2d-x.org/news/216
Here are Windows instructions: http://cocos2d-x.org/wiki/How_to_run_cpp-tests_on_Windows
Related
I have a .NET Framework 4.6.1 project. I'm following instructions on this .NET Upgrade Assistant Page to upgrade to .NET 6.0. After I completed the upgrade, I looked at the project file. The Upgrade tool upgraded the v4.6.1 to netstandard2.0.
Shouldn't the project be upgraded to .NET 6.0 and not netstandard2.0? Is it not possible to upgrade to .NET 6.0 from .NET Framework 4.6.1.
<TargetFrameworkVersion>v4.6.1</TargetFrameworkVersion>
to
<TargetFramework>netstandard2.0</TargetFramework>
You can find some solution on this link:
Migrate from .net standard to .net 6 using the upgrade tool
Already answered.
But based on my understanding. If you update a class library then the assist tool will change your project to netstandard.
After that I think you are able to change it via the csproj to .net6.
Hi I was testing yesterday the new version of Visual Studio 16.0.0 Preview 4.0 and I noticed the UWP development SDK 10240 is not included there:
Does someone know if this is just because it's a preview and it's finally gonna be included in the RC versions? Couln't find it in the current installer but it is in the previews versions.
Thanks.
I Can not compile using Android version 7.
I want to get a plan for Android 7 in the 2015 Visual Studio.
I have installed sdk completely, installed Java Development Kit 1.8.0.92
But none of the above versions of Android 6 will be displayed for selection
Please give me a solution in this regard, thanks all
The solution is on upgrading xamarin android
With the update, all versions of the api were finally made available
Thanks to the advice of all loved ones
I am working with a project which uses .Net Frame V1.1 runs on VisualStudio 2003,
Now, I want to run my project in VisualStudio 2010?
Can I still target .NET Framework 1.1 in VisualStudio 2010?
Visual Studio 2010 only supports the 2.0, 3.0, 3.5, and 4.0 frameworks as targets. It does not support 1.1.
Is there any reason why you can't upgrade it to .NET 2.0. Did you know that .NET 1.1 is no longer officially supported on Server 2008 R2 and so I wouldn't expect it to be officially supported on any newer operating system.
I have read of some hacks to build .NET 1.1 projects for VS2005 and VS2008 - see below. Realize that if you set this up, then everyone else who works on the project will have to go through the same setup.
http://www.hanselman.com/blog/BuildingNET11ProjectsUsingVisualStudio2005.aspx
http://devlicio.us/blogs/ziemowit_skowronski/archive/2008/08/22/working-with-net-1-1-in-visual-studio-2008-and-team-server.aspx
No, .NET Framework 1.1 is not supported by Visual Studio 2010.
First of all, The Winform application is based on .Net Framework 1.1. I have 1.1 SDK installed but 1.1 is not listed in the Target Framework(VS 2010 Beta 2) so I cannot choose the same, the minimal available is 2.0. Am I supposed to install an add-on or something for building 1.1 apps in VS 2010 beta2. Further more, I am using a Clickonce deployment publish method. I am not sure if 1.1 supports ClickOnce deployment. Please advise on both these fronts. Thanks a Lot
.NET 1.x is not supported by VS2010 (or any future versions). You'll have to use VS2002 or VS2003 for that.
ClickOnce is only supported for .NET 2.0 or later.
.Net 1.1 isn't supported on VS 2010. I don't even thing it was supported on VS 2005 or 2008. I've always had a VS 2003 install in a VM for 1.1 maintenance stuff.
Here you can find a way to create your project in .net 1.1 with VS 2008. And I think this is last version of the VS you can use to create your projects in .net 1.1
If you have an application that uses e.g. an app pool using .Net 1.1, compiling for .Net 2.0 simply isn't an option.
You should just build your code with .NET 2.0, assuming there's some reason why you can't build it with .NET 3.5.