Anybody did compile Farseer Physics Engine 3.0 with XNA 4 ?
Read the release page:
This release does not support XNA 4.0. XNA 4.0 introduced some breaking changes that means you will have to change some files in order for the release to compile. The current version (FPE 3.1) in the source control does support XNA 4.0.
You can download the latest source from http://farseerphysics.codeplex.com/SourceControl/list/changesets - although it may not be as nicely packaged as the release. It also may not be as stable.
Of course - I imagine that you probably can use Farseer 3.0 on XNA 4.0, because as far as I know there are no breaking changes in the maths-related classes between XNA 3.1 and XNA 4.0. You just won't be able to compile the demos (unless you fiddle with them).
Andrew is correct. Everything is upgraded in the latest source, however only the rendering part of the samples and testbed need to be modified for the release version to work in 4.0. The engine itself has to dependencies on any specific version of Xna and even includes a Vanilla version for use without Xna.
Related
Did anyone succeed in building libgit2sharp using .NET 2.0?
I need to make the library work under VS 2005 and have many 3.5 features to re-write.
Does anyone know of a better way to work under VS 2005 with the library or is there .net 2.0 library version available anywhere?
Is there .net 2.0 library version available anywhere?
There is no official LibGit2Sharp version working against .Net 2.0. Only .Net 3.5 or Mono 2.10 are currently supported.
Does anyone know of a better way to work under VS 2005?
Current version embeds a lightweight compatibility layer to ease a future migration towards .Net 4.0.
Provided you're committed to make it to work against .Net 2.0, I'd suggest you to adapt a similar kind a isolation layer, and (as much as possible, trying to) avoid altering the code of the library. This will ease the backporting of any future LibGit2Sharp update in your project.
I am working on an application in VS 2010 and using Asp.net framework 4.0 which i just migrated from Framework 3.5. The reason i had to migrate it to 4.0 is, i have a third party toolkit dll which is built in Framework 4.0, so in order to include it i had to change target framework of this project to 4.0. As, this project is being referred from other projects ans so on.., i end up converting whole application to framework 4.0. Every thing worked okay but as the application is using spring.net also, after successfully building the application, i found broken controls on almost all the pages. i am getting java script errors (about undefined control)for usercontrol PopupDatePickerControl we are using in the application. i downloaded and included latest version of Spring.net. i have no idea what is causing this problem. Please help if any one has experience working with this combination of framework 4.0 and spring.net? OR there is any way out to wrap up Framework 4.0 into 3.5. so i don't have to do this Migration.
Thanks!
Sounds like a shot in the dark on so many levels. It's probably not the combination of 4.0 and Spring.NET, unless you aren't referencing the correct Spring.NET dlls. Can you post parts of your IoC configuration and a rough outline of your app's architecture?
Also, what is the other third party toolkit you mentioned?
Is there a way to open XNA 4.0 projects in XNA 3.0 without installing XNA 4.0.
If you're asking if you can load a project created with VS2010/XNA 4 in VS2008/GS3, then the answer is no.
There are enough differences in not only the XNA assemblies, but how the content pipeline is structured that you really need VS2010 installed. Is there any particular reason you don't want to install v4?
If you're planning to port to XNA 4.0, you can use this XNA 3.1 to 4.0 cheat sheet to help you update your rendering code.
The answer is no. Because there are a lot of changes between them. The content pipeline, drawing states, vertex buffer and format, shader using and windows phone support.
There is a built-in "importer" of sorts if you're going from XNA3.1 to VS2010/XNA4.0 (which i've tried with mixed results), but there isn't a way to go backwards. There are too many libraries and dependencies in 4.0 that simply aren't present in 3.1 or before.
Update the project to XNA 4.0.
Check this page, contains a lot of useful information. Especially the section:
"Are you trying to convert XNA 3.1 projects to XNA 4.0?"
http://nelxon.com/resources/xdsk2.php
You Can't Convert Higher Versions to Lower Versions since some libraries and assemblies don't exist in the lower versions but you can do the opposite,
in other words, you can't convert XNA 4.0 to XNA 3.1 (or you can't open XNA 4.0 in C# 2008) but you can convert XNA 3.1 into XNA 4.0, but still you have to check for the some changes though.
I hope I helped.
I assume you are asking if you can open an XNA 4.0 project in XNA Game Studio 3.0.
You cannot to that. XNA Game Studio 4.0 can only be used with Visual Studio 2010, and XNA Game Studio 3.0 can only be used with Visual Studio 2008.
There might exist unofficial hacks that will allow you to do this. But if you use these hacks, the Content Pipeline integration with VS will not work.
If it is possible, how would you go about doing it?
Yes, it is possible so use XNA 3.1 on the ZuneHD, you just have to have XNA 3.1 installed and then the 3.1 Zune Extenstions.
You can read about those on the XNA Team Blog where they made the announcement originally.
http://blogs.msdn.com/b/xna/archive/2009/09/15/xna-game-studio-3-1-zune-extensions.aspx
For saving data, it works the same as it does on the Xbox 360 so any tutorial sample for that would work the same for the Zune (as long as you're looking at XNA 3.1 samples/tutorials)
I am a few weeks from hopefully launching my site (Yes, I know like I may be tempting fate, even merely asking this question).
I am developing using SF 1.2.9 (using Propel ORM), but I am increasingly being tempted to upgrade to 1.4, least of all, I feel it will be less of an effort to migrate a life system from 1.4 to 2.0 later on, than from 1.2 to 1.4. Also, IIRC, active support for 1.2 is being phased out next year, whereas 1.4 is to be supported till 2012 (IIRC).
So, shall I bite the bullet and upgrade, or shall I take the (on the face of it - safer) option and stay put with 1.2.9?
If you want to use some of the new features, you should upgrade of course. As the symfony development is test driven, I assume the new versions are stable and reliable.
But: Do not upgrade to 1.4 but to version 1.3. The later has an extra compatibility layer to ensure that projects based on 1.2 still work. There are some internal changes in 1.4 that forces you to really refactor some parts of your project to keep it working. With 1.3 you can make this changes step by step.
The only differences between 1.3 and 1.4 is this compatibility layer. For specific instructions, read this upgrade guide.
As for support, 1.3 is supported until the end of next year which gives you plenty of time to upgrade to 1.4 step by step.
And in general I belief also that upgrading from 1.4 to 2.0 will be easier than from 1.2.
Edit:
You can find the changes here and the deprecated stuff here.
I don't know if 'internal changes' was the right word. There is some stuff you have to consider if you change to 1.4 but the deprecated stuff in 1.4 still works in 1.3.
I will try to upgrade one of my projects to 1.3 this weekend and I can give you feedback somehow if you want to.
Are their any compelling reasons for the upgrade? Does version 1.4 have more bug fixes, or additonal features that your appliation must have? Are their any breaking changes between 1.2.9 and 1.4? Is there any refactoring to do after you've upgraded to 1.4 from 1.2.9?
I'm looking at this from a .net framework perspective;
.net 1.1 to 2.0 - there were many changes here. many of them were breaking changes, but the benefits of the upgrade were great.
.net 2.0 to 3.0 or 3.5 - a lot of upgrades were introduced here, but not very many if any breaking changes since the last two upgrades were based on the same basic framework. You can live with the 2.0 version without upgrading to any of the other two.
So if the Symfony upgrade is similiar, I would wait for a little while. You've got your application built, tested and ready to go. See what it takes for the upgrade and then see about integrating the new features in during the next iteration of your development.
Good luck with your site, and hope this helps some.