Reading this article http://support.microsoft.com/kb/813878
I have a question: Where can I get ipseccmd.exe for Windows Server 2003?
From the article you link to:
IPSeccmd.exe is part of Windows XP Service Pack 2 (SP2) Support Tools.
A quick search suggests this is the download page:
Windows XP Service Pack 2 Support Tools
Related
I just recently found out about the need for a manifest file so that my native C++ Windows app will properly detect the Windows version. Previously my app was running under the "Operating System Context" of "Windows Vista", but thanks to the manifest file it now runs under the appropriate context for the OS it's running on.
This has sent me down a rabbit hole to learn more about what "Operating System Context" means, and why I should care about it. I've been searching for specific information on what happens under the hood and the best page I've found is:
https://msdn.microsoft.com/en-us/library/dd371711(VS.85).aspx
This page details what the Windows Vista (default) application behavior is, and what behavior you can get if you add Windows 7 support via the manifest file.
Here's my problem; I can't find any information like this for Windows 8, 2012, 10, or 2016. I read through the Windows Compatibility Cookbook, but it doesn't seem to contain the type of information available in the above link.
What terms should I be searching for? Is there an up-to-date MSDN page I can bookmark that keeps track of the "Operating System Context" differences?
Thanks!
Partial answer -
Microsoft's page on Application Manifests for Windows 8 and Server 2012 has a section on the SupportedOS element, which refers readers to the download page for the Windows 8 and Windows Server 2012 Compatibility Cookbook. This Cookbook also covers Windows 8.1 and Windows Server 2012 R2. Within this Cookbook, the heading "App (executable) manifest" discusses the the Windows features included in Windows 8 and 8.1 (as well as Windows Server 2012 & 2012 R2) which are impacted by the presence or absence of the corresponding supportedOS element. Search this doc for supportedOS, as it is mentioned in other sections as well.
As for Windows 10 (and implicitly Windows Server 2016), the latest Windows Compatibility Cookbook can be read online or downloaded from this web page. Unfortunately, this latest Cookbook does not go into the details of the specific Windows features that are new or impacted by the supportedOS element for Windows 10. But many of the various behavior changes or compatibility issues with Windows 10 are discussed here.
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.
am trying to use ServerManager class but I found that "Microsoft.Web.Administration" and "Web.Management.Server" are not found on XP OS.
Any help to download Microsoft.Web.Management dll or any other suggestions ?
am using VS2010 on XP machine.
These namespaces are available for IIS 7 and later. There is no way to implement them on downlevel platforms.
In order to code against IIS 5.1 (Windows XP) or IIS 6 (Windows Server 2003) please see the following:
IIS Programmatic Administration SDK
What helped me to solve the same issue is installing
"Web Services Enhancements (WSE) 2.0 SP3 for Microsoft .NET Redistributable Runtime MSI"
http://www.microsoft.com/en-us/download/confirmation.aspx?id=772
Hopefully this will help someone else ...
I'm a big fan of "Pure Win32 API Code". I use Windows 7 Ultimate SP1 and I'm surprised with it's Ribbon UI. Can we do that in Pure Win32 API? I don't mind complex coding... I use Code::Blocks with MinGW, installed with TDM-GCC 4.6.1_1. Please help...
Ribbon is available as a native control in Windows 7 and Windows Vista with Platform Upgrade installed. The API is COM-based (like many other recent API additions).
See Windows Ribbon Framework in MSDN for complete documentation.
I got that working. I removed MinGW and installed Windows 7 SDK. Code::Blocks integrates well with it. Now I'm enjoying new APIs in Windows 7. Thanks everyone for your answers.
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.