Will their be a new release of the compact framework with VS2010 and .net 4.0 and if so what new features will it include?
WPF?
linq to SQL?
etc
Visual Studio 2010 only supports developing for windows phone 7. This is a silver light based framework, it does not support win forms or native code.
VS2010 can not be used to develop for Windows Mobile 6.5 or lower.
You can however install VS2008 along side VS2010.
From what I heard from guys in redmond, there will be a mobile silverlight platform for both windows mobile and nokia (symbian, I think).
The "silverlight mobile" platform should be built on top of the compact framework, so it will NOT be a port of the desktop version.
There seems to be an information embargo on Windows Mobile right now, but I think things will be much clearer once Windows Mobile 7 is out.
I'm not sure about 4.0 for compact devices (although it seems likely),
and I don't know about WPF either, but I can tell you they are going to provide Silverlight for mobile devices giving you access to a subset of WPF.
Haven't found any other references yet...
You can go here and vote to have Microsoft add Compact Framework Support for Visual Studio 2010.
UPDATE: MS has more or less abandoned existing feature requests in Connect. Please go to the new User Voice site to vote for this feature.
There's an unofficial release of CF 3.7 kicking around the intertubes:
http://www.google.com/search?q=compact+framework+3.7&rls=com.microsoft:en-us&ie=UTF-8&oe=UTF-8&startIndex=&startPage=1
It appears that someone ripped it off a ROM image and dropped it in a torrent.
Related
What IDE (and version) and it components should I use to build that app? For now I write in C# so that will be cool if it is possible
This is what i use for wm:
VS 2008 pro, Microsoft .NET Core SDK 2.1 (x64), Windows Mobile 5.0 Pocket PC SDK. Im not sure about Davide Piras' answer above. I have never heard that anyone managed to install WM 6 project profiles in any VS above 2008 version. Beside v2008, i also have VS2012 installed and it doesnt register any MW project from Mobile SDK 5.0.
in the past i used Visual Studio .NET 2005 with the .NET compact Framework, that allows you to build apps for windows mobile 6.
mind that there is no above, Windows Phone ( 8 or 10 ) is a completely different beast than Windows Mobile 6 and app development for Windows Phone is still done in .NET but I don't think you have code or binary compatibility between Windows Mobile and Windows Phone.
I have about 20 app demos, mostly for Windows Mobile but some for Windows CE. They were all created in Visual Studio 2008 for Mobile 6.1, Mobile 6.5, and CE 5.0. They are a mix of C# and VB.NET. I've been asked to update them.
I've done a fair bit of research, and I understand you can't do the standard Visual Studio project conversion, but is there anyway to salvage these projects? Ideally, I need to get them running on the current version of Windows Mobile/CE and compiling in the current Visual Studio. Is there any hope for them?
The latest version of Windows Mobile/CE is WEC 2013, and is supported in VS2012 and later. Note that for .NET CF development you will need an Application Builder SDK from the device vendor.
Whether you will be able to port the applications really depends on what they do.
For instance, one of the main differences between CE 5.0 (and its mobile derivatives that you mention) and WEC 2013 is that in WEC 2013 user mode code can no longer access hardware directly, so if the applications rely on direct hardware access you will need to find or implement device drivers to do this. On a related note, P/Invoke is always a potential cause for concern when porting.
You'll also need to determine if the target device includes all the OS features that are required by the applications. Remember Windows CE / WEC are componentized OS's, and the device vendor might have excluded features from the OS image that the applications need in order to function.
We have some applications running on data reader devices with windows CE 6.0.
These apps was created with genexus generating C# / .Net Compact Framework 3.5
Genexus will not support this anymore and I´m looking for alternatives to rewrite these apps.
First, off course, i thought about Microsoft, but i would have to use visual studio 2008 (too old, my devices are also, but...).
Than i thought about SharpDevelop, but Compact Framework was dropped in version 4.
Does anyone know an alternative to develop C# for Windows CE 6.0?
Visual Studio 2008 (or 2005) is your only option and that's simply never going to change. Microsoft abandoned the Compact Framework starting in about 2010 and completely in about 2015. Windows CE itself has effectively been abandoned as well. There's simply no market for anyone else to even try to make an IDE for development for systems that have zero future.
I have created a game using C# and Microsoft XNA 4.0. It works on fine on Windows 8 and 8.1, but my friend tried downloading it for a computer running Windows 10 and found that it wouldn't open. It wouldn't even appear in Task Manager when opening it was attempted. The computer in question has the Microsoft XNA Framework Redistributable 4.0 installed on it, so it should be working. Is Windows 10 simply not compatible with XNA?
XNA is no longer supported on newer versions of windows, it was discontinued and isn't supported on platforms newer than Windows 7. Luckily there is an open source implementation of XNA which is essentially the exact same thing and that is currently supported on all windows versions. It's called "MonoGame", here's the link to their website:
http://www.monogame.net/
I know this is a older post but just for those looking for an option like I was today (this post is still a top hit in google) its a bit of work to get setup, but XNA will in fact run on windows 10 just fine, and there is a way to actually use Visual Studio 2017 with XNA just fine as well:
http://flatredball.com/visual-studio-2017-xna-setup/
so if you have code for XNA or like the XNA framework (Like I do, I prefer the pure c# way not c# to some other bloated bridge like Unity) for 2D games then this will be your savior.
Enjoy :)
Some updates:
On March 14, 2016, ID#Xbox announced that MonoGame is coming to Xbox One:
* https://mobile.twitter.com/ID_Xbox/status/709402975051980800
In the FB group Xbox One Indie Devs, Tom Spilman from the MonoGame team had some information to add, more info coming soon.
* https://www.facebook.com/groups/XboxOneIndieDevs/permalink/852775944827686/
Stay tuned to the Twitter account and FB group mentioned above, for new info when available.
Hope that helps!
XNA does work on Windows 10 and even Windows 11. In 2021 I released a game using XNA Framework and it works but the user will have to install XNA Redistributable 4.0 for the game to run on their system so that's not ideal.
But then I ported my game to FNA Framework which is an open-source, identical, reimplementation of XNA. My codebase required almost no changes to work under FNA so I highy recommend it to you.
FNA requires no additional library installation. The DLLs need to be in the same directory with your executable and it will work.
You can see my game here if you are curious about the subject: https://cyon4d.itch.io/cozy-days
To add on what x2kpb said, your best bet at this point is to look at MonoGame for certain platforms, and FNA for others.
XNA, in its pure form, will not work as a new Windows 10 application. The platform to bring win32 (XNA) games to Win10 is called Project Centennial
Both Xbox One and Windows 10 will support MonoGame, per this video at last year's BUILD conference.
I have windows 8.1 64 bit with visual studio 2013. But I want to develop C# application which will run on all Windows operating system xp,vista,7,8,8.1 32bit&64bit.
Is it possible to develop universal C# application for 32&64 bit xp,vista,7,8,8.1 OS.???
As pointed out in the comments, you can use .NET 4.0 to do this, and compile with Any CPU. Don't use 4.5 or later, as it's not supported on Windows XP.
You can even back-target your app all the way to the 2.0 runtime if you have a very simple application and you want to have the widest availability without having to install a later version of the .NET Framework on old machines. You give up a lot when you do this, though. I recommend just targeting 4.0 and being done with it.