Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
platform
active.directory
adsi
adsi.iis-admin
base
com_ole
complus_mts
component_svcs
database
directx
gdi
graphics_mm
internet.client
internet.server
internet.server.isapi-dev
localization
mapi
messaging
msi
mslayerforunicode
multimedia
networking
networking.ipv6
sdk_install
security
shell
telephony.tapi_2
telephony.tapi_3
telephony.tsp
telephony.wte
tools
ui
ui_shell
win_base_svcs
win16
  
 
date: Sat, 25 Mar 2006 09:27:39 -0800,    group: microsoft.public.platformsdk.tools        back       


platform sdk 64-bit   
Did anyone used the Visual C++ 7.1 (aka .NET 2003) 64-bit libraries?
If so, what do you think and what did you do when Visual Studio 2005 was
released? I know from the EULA the license for the Visual C++ 7.1 64-bit
libraries terminates at that time.
If you didn't, what did you think of the mixture of a prerelease of the
Visual C++ 2005 compiler and the Visual C++ 6.0 libraries and the issues it
caused, included the need to link to bufferoverflowu.lib to enable /GS?
For everyone who used the 64-bit tools in the Platform SDK (any version),
was it the first exposure to Profile-Guided Optimization?
date: Sat, 25 Mar 2006 09:27:39 -0800   author:   Yuhong Bao

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us