We have a variety of Windows CE 5.0, 6.0, 7.0 and Windows Mobile 5.0 devices. Our apps use Compact Framework 3.5, developed with Visual Studio 2008. The apps support multiple languages; the user is allowed to select the language when logging into the app.
Our issue is, while Visual Studio supports Spanish (United States) as a language choice, none of our devices have this installed. As a workaround, I can use the Spanish (Mexico) es_MX language, which is installed, and modify the DateTimeFormat and NumberInfo properties as run-time. However I don't feel comfortable with this approach, if there is a better way. Will I run into some other issues by taking this approach? Is there a preferred alternative? Note, .Net CF 3.5 does not support the CultureAndRegionBuilder class.
Related
I made the big mistake of taking some NuGet library updates today. It forced me to either roll back a week's worth of work or upgrade to ASP .NET Core 3.0. I hate to use stuff that's not production, but I didn't want to untangle the libraries either, so I upgraded. Then it forces me to retarget .NET Standard 2.1 libraries. Which I did.
My problem now is with the client UWP code. When I try to compile, I get:
error : Project '..\ClassLibrary1\ClassLibrary1.csproj' targets 'netstandard2.1'. It cannot be referenced by a project that targets 'UAP, Version=v10.0.10586'.
This happens even with a virgin UWP and .NET Standard 2.1 library. Any clues on how to make Visual Studio 2019 client code work with the latest upgrade?
All Windows 10 SDKs currently don't support .NET Standard 2.1.
Windows 10 19H2 is using the same SDK number as 19H1, so it is unlikely that it will support .NET Standard 2.1. (But I certainly hope it does.)
Microsoft hasn't made an official announcement, but Windows 10 20H1 is getting a meaningful SDK update, so it is likely that it will support it. And once that's the case, UWP apps will require 20H1 to run (so that will become the minimum supported version).
One of the big issue with this situation is that Entity Framework Core 3.0 requires .NET Standard 2.1, so it can't be used in UWP apps for now (Update: This issue is resolved with Entity Framework Core 3.1 supporting .NET Standard 2.0).
By the way, as an experiment, I was able to fork Entity Framework Core 3.0 (for SQLite) and make it compile on .NET Standard 2.0. I basically had to manually copy a few new APIs from .NET Core 3.0 (like IAsyncXXX). And it worked, so it is an option for people who really need it. Note that, I did not try it with the SQL Server provider.
Update: The UWP team is planning to enable UWP apps to use .NET 5 and that's when UWP will support .NET Standard 2.1 (and more). This could happen in 20H2 or 21H1.
UWP does not support .Net standard 2.1 yet. It only support till .Net standard 2.0 and that too from windows 1709 onwards.
If you look at the link for 2.1 it states
Platform Support
An upcoming version Universal Windows Platform
so it may be 19H2
UPDATE
Microsoft is going to release a new framework called WinUI 3, this is going to support UWP as well as Win32 based application model. WinUI 3 would support .Net 5 for both the platforms. WinUI 3 preview is going to be available in mid May 2020, with final release in late 2020. WinUI 3 would be supported on windows 10 1803+.
I am embarking on a cross platform app, but not mobile. It will be win/osx/linux. Would love to use Delphi + firemonkey, but it appears linux is not a possible target?
The GUI will not be extensive. Most of the code is non visual.
What are my options here? (Do I end up using lazerous for the linux side.... and then I have to have a special UI there?)
Please let me know my options here, how to solve this cross platform dev project (and hopefully avoid c++).
Linux is not currently one of the supported operating systems, as can clearly be seen from the product description on the Embarcadero web site. If you need Linux/Unix support, XE4 and FireMonkey aren't an option. (XE4 supports Win32, Win64, OSX, and iOS.)
There's support for Linux planned at some point in the future (after Android, which is currently being developed and slated for release later this year).
I've drawn the short straw at work and I have to support the Installshield 2009 setup application. When I open the .ISM file in InstallShield 2009 Professional I get this message:
The following languages will be disabled as they were included in this project but are not installed on this system:
Chinese (Traditional)
German
French (France)
Italian
Swedish
Chinese (Simplified)
Do I need to install something in Windows XP, or do I need to install something in InstallShield? Any insight would be very valuable!
The problem was that I need Installshield Premier and not Installshield Professional (which is the one I have).
You need Premier instead of Professional for multilingual setups. If you can't afford the upgrade, I'd suggest migrating to WiX.
I am facing problem while upgrading an Higher version over Lower version. I have implemented multilingual support; Assume that older version being installed in French while doing upgrade it is coming in English which is my Operating System language; in fact it should show in French.
Have you configured the installation to prompt for the users language, rather than detecting the OS locale? Simply go to the Releases view, find your release and ensure that the "Languages Dialog" is set to yes.
Since the installed language of the app is different to the OS language, you'll need to prompt the user. You can't detect a previously installed language that early in InstallShield as far as I know.
I'm curious about what it takes to program for mobile devices (Windows Mobile 6.1) and if I can use the IDE's we're already used to (RAD Studio 2009).
Is there a Mobile Development Community around where Delphi or C++Builder users can learn from?
Are there differences in development techniques, like: Drivers, Memory Limits, Device Specific Considerations and others?
Links to Documentation and Tutorials are always awesome!
Thanks!
You can do Compact Framework development in Delphi.NET (Prism?) but not natively in 2009.
It was a hot topic in the community a few years ago when I was involved, and it basically came down to resources, cost of implementation and potential license fees that made it not worth doing for Borland (as they were at the time).
That may have changed now, but reading the 2009 feature sheet it appears not...
Edit: It appears there is no designer support for CF in Prism.
If you prefer using Pascal you can use FreePascal to develop for Windows Mobile 6.1