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.
I use Visual Studio Team Services. I goto - My Profile - Locale - choose another language. But the language in the browser there is in English. How to change language in Visual Team Services?
From Brian Harry's Blog Post about Microsoft's first non-US hosted instance of Visual Studio Online:
Although we have our first instance in a non-US, non-English speaking
region, we do not yet support a localized experience for VS Online.
You can enter data in any language you wish but the UI for VS Online
is currently English only. This is something we expect to begin
addressing sometime next year.
Emphasis mine.
I had a problem where my TFS online was displaying in French rather than English even though other sites that I had been on were displayed in English. I discovered that my language had been set to French in Chrome and when I changed it back to English TFS also changed. So basically if you want to change the language of TFS online just change the default language in your browser!
The reason this works is that a lot of new web applications which are localised will look at the language settings for your browser and use that information to decide what language the website should be displayed in.
Source: I work with web applications that use this technique.
You can manage VS Team Explorer locales here:
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer
For example, you can rename folder with current team explorer locale to anything else (be sure to shutdown VS). After that locale will be switched to default (en-us).
I just downloaded the Delphi 2010 iso from my SA-subscription and wanted to install it in addition to my other Delphi installations on my notebook computer. Unfortunately it refuses to install because the machine is running Windows 2000.
Is it possible somehow to get it to install it anyway? Or is there a technical reason why it might not work, even if it installed?
edit:
Some more information:
Delphi 2009 installed fine on that computer, so dotNET 2.0 is already installed.
The Delphi 2010 installer comes up, asks me for the language to use and then says "This product requires at least Windows XP. Setup cannot continue."
What I am looking for now, is either:
a way to get the installer to skip this check and install anyway - or -
a reason why this would not work (e.g. Delphi is using some Windows API that is not available in Windows 2000)
You could try to start the setup.exe with the /Win2K parameter. Maybe this helps. But I heard from a German forum that a user who installed Delphi 2010 into Windows 2000 had lots of problems with the IDE. So use the /Win2K parameter at your own risk.
And you must have at least .NET 2.0 SP1 installed
According to the minimum system requirements, Windows 2000 is not supported. They might use some XP+ specific API's these days, but then again they might not, as Delphi 2009 installed fine on Windows 2000.
The first thing you might want to check is if you have .Net (2.0 minimum) on your machine. According to the document linked above, they try to install The .Net 3.5 distributable otherwise, and that one definitely requires XP minimum.
windows 2000 is supported in Delphi 2010, check the following link:
Target Windows 2000, XP, Vista, and Windows 7 from single source
I think the problem is from your pc, maybe because there are other versions are installed, can you post the message?
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 tried to install Delphi 7 on Vista several times and Vista prevented me from doing so by telling me that there are known problems with this application (Delphi 7). Several other people in my company experienced problems with installing D7 on Vista.
This lead to the conclusion that we were at risk with our D7 application, as the company could within the lifetime of the app switch to Vista or Windows 7 and newer Delphi versions are not in the policy of the company. Therefore management decided on rewriting the app in C#.
My question(s):
How to install D7 on Vista
Experience with such an installation
Risk assessment concerning stability of IDE and developed programs
Risk assessment concerning executability under Windows 7
Not using any third party components or database - there should be no problem running the developed app under Vista. If not able to develop and debug under Vista (which at the point being will be the only customer platform, yes, internal programming) will result in a sort of cross platform development - if we would be allowed to keep XP as the development platform.
It is not a developers decision to rewrite, it has been done in the company for the last 3 years: if you had to significantly touch an app developed in Delphi or if there was a certain risk of it not to survive the planned life circle/life span, it had to be rewritten. The life cycle just expanded to 2015 due to canceling another project.
So the main issue here would really be: I would like to have educated arguments about the risks.
Running Delphi 7 under Vista is no problem if you can turn UAC off. With UAC on, you get an error message when starting D7, but it still works, just click ok and go on.
Programs compiled with D7 have no problem with Vista. But new features of Vista are supported by Delphi 2007/2009 only.
We use D7 on XP and on Vista, building and maintaining a commercial App which has gone from D2 to D4, D5 to D7. Besides problems with the BDE, which made us switch to DBX (Corelabs) there are no problems.
Just follow these instructions and you'll be fine. No reason to turn off UAC! I've been running Delphi 7 on Vista for about a year without any problem at all. Debugging is totally fine too.
http://www.drbob42.com/examines/examin84.htm
For installing Delphi 7 in Vista, you can try this patch from Microsoft.
http://support.microsoft.com/default.aspx/kb/932246
As for the rest someone else I suspect will have more knowledge.
I have Delphi 7 working fine on my Vista development box. Yes there was a few issues during installation, but no more than other applications and these issues have been resolved in subsequent versions of Delphi.
None of this should cause problems with apps developed by D7 for Vista. We use Delphi as our primary development tool for all our applications and they work just fine with Vista.
It sounds like this is an excuse by someone in the company to get rid of Delphi and move to C#. Typical FUD tactics. There may be genuine reasons for your company to move away from Delphi, but Vista compatibility should not be one of them.
Also, if you'd like all the Vista-ready features in your Delphi 7 application, have a look at this article here: Creating Windows Vista Ready Applications with Delphi
This will make it so that your application correctly appears when doing Flip3D, or when showing a preview thumbnail when hovering over the app in the taskbar. Essentially, this will give you the "Vista-readiness" of Delphi 2007, from within older versions of Delphi (I have used this with Delphi 2006 and it works very well).
You also get the new Vista task dialogs and new Common dialogs with the modifications listed on the linked website.
I think there's a big jump from having trouble installing D7 in Vista (D7 which after all contains low-level bits and pieces for the debugger and which doesn't know about the 'correct' place to put things under Vista), to assuming that your own app will have problems with Vista...
You have the source code, you can test your program running under Vista, you can make whatever (usually minor) tweaks are necessary to your code.... I'm really surprised that you would decide to rewrite the app in another language just because you can't get the (old) development tool to install under Vista.
We need to know more about what your application does, and what components you make use of, to be able to make any guess at your 3rd and 4th questions. They're too general.
FOr instance, I have several D7 applications on the market, one of which uses open-source Interbase 6 with Delphi and can be a problem to get installed/working on Vista Home (the process seems less painful on Vista Business). Another of our apps uses SQL Express 2005 and runs quite happily on Vista. Our newest app, written in D2007, runs fine on Vista. On both Delphi platforms, our two main 'third party' tools are DevExpress controls and ReportBuilder.
I have been using D4 with Vista for year as one of our key products uses it, its good version still and there are workarounds to make it use new Vista features. You can call any win32 API (new functions) so there is no point to update to D7.
I installed/moved D4 to my new machine by hand:
1. by exporting registry hive(s)
2. registering a few components
3. copying files
thats it.. no need to run slow setupper.
As others have noted, there is no problem running Delphi 7 applications under Vista: We do this with a multi-hundred-thousand line Delphi 7 application that uses numerous third-party controls (Developer Express grids, TSILang translation components, etc.).
We use Vista as our primary operating system, but we run the Delphi 7 development environment in a Windows XP Virtual machine. It works perfectly, and there are no installation issues.
It is very simple really.. All what you have to is the following:
Search UAC (User Account Control) off and then intall delphi7 but, you must have no other version of delphi on your computer.
1,2 in Vista) no problems heard if you install http://support.microsoft.com/kb/947562 and configure UAC;
3) None stability issues are known to any of my friends here...
4) Not using Windows 7 with Delphi 7... But heard of many problems with both...