I have a Win XP Embedded machine (WES2009), that does not have preinstalled "Microsoft Windows Embedded Studio" (MSWES).
I need MSWES as a preposition for development (RTX by IntervalZero).
All I found on MS site related to this product is docs: http://msdn.microsoft.com/en-us/library/ms838630(v=WinEmbedded.5).aspx
Anyone with a clue:
Can I simply install MSWES product on my WES2009 machine ?
Where can I download it simply ? (Preferably without using MS account.)
You don't run Embedded Studio on XP Embedded; you run it on your development host, and use it to create an XP Embedded OS image for your target application.
You need a development license, and ultimately deployment licenses.
You can simply and officialy download the WES2009 here:
http://www.microsoft.com/en-gb/download/details.aspx?id=14947
This should be a trial version, or you apply your bought licence to this.
Related
I need to install webmatrix 3 in a pc without internet connection.
I have win7 64bit.
so i downloaded webmatrix x64 exe and all his dependencies and services exe/msi files - include web platform installer.
I installed all and run the webmatrix app but an message box pop up and said that I need to have the latest webPI installed (4.6 in this days..).
But it is a problem because the wpilauncher.exe file (webPI installer file) install version 4.0 for some reaseon, i think it because I dont have internet accsess.
so?
help, thx.
you can download offline installer from Web Platform Installer
Run on your PC with internet connection WebMatrixWeb.exe, click Install
You will see installation plan and download link on the right.
this may help
There's a link to an offline instaler for x86 available at download.microsoft.com/download/c/2/a/c2a485fa-013a-45ef-baba-c568e40f4b50/WebMatrix_x86_en-US.msi. Requires IIS 7.5 Express or IIS 8.0 Express.
I can see you've specifically asked for x64 version, but this might work for someone searching for x86 version.
WebMatrix needs an active internet connection to install since it pulls in some other required services from the Web Platform Installer.
Quote:
"..WebMatrix needs other components installed to function correctly,
and those are all pulled in by Web Platform Installer automatically.
In that sense, the true installer is not really "offline"."
Source: http://connect.microsoft.com/VisualStudio/feedback/details/641843/webmatirx-offline-installer
It seems that it is impossible to find an image of Windows XP Professional x86 checked build. But I still need to support the software and do my work for that system. :(
Yes, I know that I can install only the checked kernel on the free build, but I still want to have a checked system, not a mix of the two.
Solutions, anyone?
UPDATE: It appears it is not clear from the question itself that what I am looking for is the installation image itself (an ISO image), so I can have the full checked build of the OS installed. NOT the service packs. NOT x64 image.
UPDATE 2: Why calling MS won't help: see http://msdn.microsoft.com/en-us/subscriptions/ff723773.aspx after "Products Unavailable due to Java-related Settlement".
UPDATE 3: See http://social.msdn.microsoft.com/Forums/en/wdk/thread/5fa40892-8207-425a-8866-0fcaebb0c343 -- someone suggests that "The only install disk of a checked XP was the release, i.e. no service packs. MSDN and Technet distributions had the disk as one of the set." Does anybody here have those disks? Seems that ours were lost in the sands of time.
UPDATE 4: Narrowed it down to a MSDN CD named "Windows® XP Professional Checked/Debug Build (English)", disc 1013, volume label X08-48914, dated October 2001. Anyone has that one?..
I bet that if you support your software to work in Windows Server 2003 then your software will also work in Windows XP, even though Microsoft's debugging symbols differ. You can install the checked build of Windows Server 2003 RTM, add the optional component for desktop experience, and it will be approximately the same as Windows XP with SP1 with some increased security. Checked build service packs are available for Windows Server 2003. So you can approximate every service pack version of Windows XP except for Windows XP RTM.
Checked versions are only available in English. You can install an MUI pack but the result is not identical to an actual Russian version of Windows. You'll have to test your software again in the actual version of Windows that your customers use, and that will not be a checked version.
These files are downloadable from MSDN:
en_windows_server_2003_enterprise_chk.iso
en_windows_server_2003_enterprise_x64_chk.iso
(The first paragraph was edited to mention that the Windows Server 2003 RTM download is also a checked build. Of course the download would be useless otherwise.)
I am interested in windows mobile7 application development and struggling with setting up the development environment. I found this DISCUSSED LINK.
(So it answered one problem that I had. I have already installed VS2010 Ultimate edition. I guess when I install Windows mobile7 SDK, it will install all the Windows mobile7 SDK tools without affecting the VS2010 that I have already Installed)
In my laptop I have windows7 64Bit operating system. Can someone please send me the steps that I should follow to make the environment to start windows mobile7 application development without affecting existing VS2010.
If someone can post the steps in sequence (including where I can find the SDK tools), Highly appreciated. Thanks inadvance...!!!
You can't install Windows Phone tools without affecting existing VS2010 installation. How would you create Phone apps without adding phone tools to the existing installation? Adding tools is an affect, is it not? Why worry about adding more tools? It's not going to take anything away from VS.
Download the tools from create.msdn.com. Run the Windows Phone tools, and start writing phone apps. It really is that simple. As for the tools installing the express version, I don't think so. I have ultimate, and looking through my file system now, there is only one devenv.exe, not a second one for express.
I have an old VB6 application that depends on MSINET.OCX. I'd like to know if I can distribute this application without registering MSINET OCX component. My target OSes are XP, Vista and Windows 7. Do all of them have this component preinstalled?
See if this information from technet helps you. The short of it seems to be that it does not come preinstalled, it is installed when you install an application that uses it. You will need to include it in your installation.
It's not shipping with the OS. It is however delivered with Visual Basic. You must include it within your application setup. For details on Vista and Win7 support see: Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008 and Windows 7
My company is planning on developing for Windows Phone 7. The build server we have, however runs Windows Server 2008. According to the Windows Phone SDK release notes I've read that only Windows Server is not supported for the SDK.
Does anyone have any experience on whether there's a possible workaround to have a Windows Server 2008 machine build Windows Phone 7 projects?
Update: I'm interested in building on a WS 2008 as we're talking about a project with a larger team where continous integration and centralized builds are essential. I'd be hoping we wouldn't have to set up an additional Windows 7 build server for this task.
Most the issues of this nature come into play meeting the emulator's requirements rather than the development tools.
With that said some are hacking around the walls put up to stop people going into the unsupported territory of WS2008.
Judging by your requirements I'd say dive in. If you have the option to test on device or in emulators in Win7, that will place you well.
This post likely of interest.
Aaron Stebner's WebLog : How to install the Windows Phone Developer Tools CTP Refresh on Windows Server 2008
If someone is interested here is instruction how to modify ISO image of the WinPhone 7.1 SDK for installing it on Windows Server. Basically it's the same Aaron Stebner solution, the only difference is that you need to modify it in the ISO image.