Would Windows CE 5.0 binaries be compatible on Windows Embedded Compact 7 and 8?
I've searched the Internet for a long time with no answers that are thorough or definite enough concerning the backward compatibility of these OSs.
Also I've tried to find the ceappcompat app mentioned here; it looked like it was supposed to be in the Platform Builder tools found in the installation of Windows Embedded Compact 7 x86, but it wasn't there.
By way of experiment, I have found that Compact 7 is, in principle, backward compatible with respect to native applications. I was able to run x86 applications built against Windows CE 5.0 Standard SDK on a Compact 7 OS. However, Compact 2013 is a different story. As explained in the answer to a similar question on MSDN forum, existing Windows CE applications must be recompiled in order to run on Compact 2013. Reportedly, the breaking change in the new OS is the price paid for the ability to use the same Visual Studio 2012 tool chain for both desktop and Embedded Compact Windows targets.
Related
Without specifying RuntimeIdentifiers in my csproj I got win7-x64 on both win7 and win10 machines. Both builds works (based on full framework).
I cannot find docs about - how to choose right RID and what is the difference between same-architecture-and-platform RIDs?
The.NET Core defaults to win7 for
.NET Framework projects. In most cases, win10 and win7 runtime identifiers produce identical output, especially for .NET Framework projects.
The difference only matters if you depend on a NuGet packages that has Windows 10 specific APIs, which very few do, if any. Choose the runtime identifier that matches the minimum platform you support. E.g. if you don't intend to support Windows 7, 8, or 8.1, use win10.
Or use both if you want to support multiple platforms. RuntimeIdentifiers accepts a semicolon separated list.
When you deliberately want your apps to be only used by Windows 10 users.
That can be pleasant if your apps do use Windows 10 specific features, which is not obvious for console and web apps, but might be typical when Microsoft introduces other project types such as GUI apps.
What I can think of at this moment is Windows 10 only things such as HTTP/2 support.
I am working on a project developed in ADA on windows xp using GPS-GNAT 2006 and must port it to windows 7 however when trying to upgrade to a newer version of GPS-GNAT (2008+) the ada code throws exceptions, but on the 2006 version it runs but GPS-GNAT 2006 has issues with hitting breakpoints, opening the IDE, the open project button, etc. My question is are there known compatibility issues with Win7 and GPS-GNAT 2006? And what should be the best course of action to get this old code running on windows 7?
Thanks
You are mixing two things here: the GNAT compiler itself (for which you might be stuck with an older version indeed), and the GPS IDE, which you can upgrade independently of GNAT. As others have suggested, please upgrade to GPL 2015 for GPS, and keep the old compiler.
I am wondering if it is better to develop .Net 2010 web application on XP as compare to Vista? I have developed many .Net applications on XP without any problem and personaly like XP over vista. Now i have started a new job and we are all mainly using Vista Ultimate 32 bit.
Are there any known issues with vista for VS2010 development?
Application will be published on Window Server 2003 or 2008 so my main concern is developing and running application localy.
Also, is Visual Source Safe 6.0 Compatiable with Vista?
You'll have some difficulty since XP is only 32 bit (unless you've got the 64-bit edition which is a little flakey re: drivers).
Also, certain features like XNA Game Studio, Windows Phone 7 development, DirectX 11, etc... just aren't supported on an XP development environment.
You may also hit issues with regards to integrating with the Azure cloud platform as it has some dependencies that don't work fully on XP.
That said, if you're only going for a simple Winforms/Console app/ASP.Net site, you probably won't ever notice the difference
Oh and .Net 4.5 isn't supported on XP
As an aside, please DO NOT USE visual source safe - it's truly awful. It doesn't guarantee consistency, has no concept of branching and merging, doesn't allow multiple users to work on the same files and is generally unreliable (not to mention the fact that it relies on every client playing nicely and a single malicious user can drop the entire data store since it's really just a windows share with some files, not an actual server). See this article: Visual SourceSafe Version Control: Unsafe at any Speed? for more details.
You should use TFS or an open source alternative (I've also played with SVN and used AnkhSVN to integrate into VS - Not perfect but pretty good). If you want to use TFS but don't have the servers/experience to set up a server yourself, There's a (currently free) beta being run by microsoft at tfspreview.com which integrates right into VS 2010 SP1 and later and provides all the same functionality as well as a whole slew of other features like bug/workitem tracking, analytics, etc...
I am about to upgrade my pc, and operating system at the same time. I was wondering what version of Windows 7 to get pre-installed, given that I want to do some ASP.NET development using Visual Studio.
Specifically :
Will all versions of Windows 7 run an IIS server & be suitable for ASP.NET development ?
Are all good for running SQL Server etc ?
Will Windows 7 have any probs running old versions of Visual Studio (Ie. 2003 & 2005 versions).
Are there any other things I need to consider ?
I'm probably going for the 32 bit version of Windows 7.
Thanks in advance,
Bazza
I would suggest you get the 64-bit version: there's really no reason to be running a 32-bit operating system in this day and age (unless you have some esoteric hardware that doesn't have 64-bit drivers, but that's exeedingly rare: especially on Windows 7).
I think IIS 7.5 is included in Home Premium, but I think the Professional SKU is probably the best bang-for-buck version. You don't actually need IIS for ASP.NET work anyway, the development server that's included with Visual Studio is usually the best option anyway (it doesn't require Administrator privileges to debug).
Other than that, they'll all run SQL Server fine, and I see no reason why older versions of Visual Studio won't run, either (there may be issues with UAC, but nothing too dramatic for day-to-day use).
I'm a little confuse between the different SAPI version available.
First of all, I only find the SDK to develop with the 5.1 version, is there any SDK for the 5.3 version available, if not, why ?
Witch version can I use if I'm developing with the 3.5 version of the .Net framework.
Is there any good tutorial because the only one I found are pretty old (they use 2003 version of visual studio) : http://msdn.microsoft.com/en-us/library/ms986944.aspx
Is there any way I can use the speech API directly in Asp.Net web site in speech-to-text mode ?
Thx!
Wikipedia tells me that SAPI 5.3 was included in the Windows SDK, so go download that. SAPI 5.3 looks like it was included as part of Windows Vista, so I don't think you can use it in any other version of windows. The library is just a COM library, which means it's not dependent on your .NET version - i.e. you could use it in .NET version 1.0 even. In fact you could use it in almost any language because a lot of them support COM in some way these days.
I'll get your easy question out of the way, no you can't use the Speech API in any way from ASP.NET on the client's computer. If you're really serious about it though, you could look into either creating a Silverlight application which uses the Speech API on the client's computer, or alternatively look into constructing the voice data on the server and streaming it down to the user. However, both options would probably be quite difficult at the moment I think.
I learnt to use SAPI 5.1 from the tutorials on MSDN, just like the link you posted. They are old, I know, but they're all still relevant. SAPI 5.x hasn't changed for almost a decade now. Visual Studio 2008 can still do all the things Visual Studio 2003 could do (well, mostly I presume) and it definitely can use a COM library, so it's possible, you just got to use your brain a bit.
You should try the namespace System.Speech (it work's with VS2008 do not know if framework under 3.5 have it... and I am on Vista)
SpeechSynthesizer foo = new SpeechSynthesizer();
foo.Speak("Test");
You can have more detail here on MSDN