| mmc\mmc.vcproj:
+ Due to the requirement that Visual C++ projects produce an embedded (by default) Windows SxS manifest, manifest files in the project are now automatically built with the Manifest Tool. You may need to change your build in order for it to work correctly. For instance, it is recommended that the dependency information contained in any manifest files be converted to "#pragma comment(linker,"<insert dependency here>")" in a header file that is included from your source code. If your project already embeds a manifest in the RT_MANIFEST resource section through a resource (.rc) file, the line may need to be commented out before the project will build correctly. |
| mmc\mmc.vcproj:
+ Due to a conformance change in the C++ compiler, code change may be required before your project will build without errors. Previous versions of the C++ compiler allowed specification of member function pointers by member function name (e.g. MemberFunctionName). The C++ standard requires a fully qualified name with the use of the address-of operator (e.g. &ClassName::MemberFunctionName). If your project contains forms or controls used in the Windows Forms Designer, you may have to change code in InitializeComponent because the designer generated code used the non-conformant syntax in delegate construction (used in event handlers). |
| mmc\mmc.vcproj:
+ This application has been updated to include settings related to the User Account Control (UAC) feature of Windows Vista. By default, when run on Windows Vista with UAC enabled, this application is marked to run with the same privileges as the process that launched it. This marking also disables the application from running with virtualization. You can change UAC related settings from the Property Pages of the project. |
| mmc\mmc.vcproj:
+ Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion. |
| mmc\mmc.vcproj:
+ VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings. |
| mmc\mmc.vcproj:
+ Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion. |
| mmc\mmc.vcproj:
+ MSB8012: $(TargetPath) ('D:\OpenXP\inetsrv\uddi\source\mmc\Debug\mmc.dll') does not match the Librarian's OutputFile property value 'Debug\mmc.dll' ('D:\OpenXP\inetsrv\uddi\source\Debug\mmc.dll') in project configuration 'Debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Lib.OutputFile). |
| mmc\mmc.vcproj:
+ MSB8012: $(TargetName) ('mmc') does not match the Linker's OutputFile property value 'Debug\uddi.mmc.dll' ('uddi.mmc') in project configuration 'Debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetName) property value matches the value specified in %(Link.OutputFile). |
| mmc\mmc.vcproj:
+ MSB8012: $(TargetPath) ('D:\OpenXP\inetsrv\uddi\source\mmc\Debug\mmc.dll') does not match the Linker's OutputFile property value 'Debug\uddi.mmc.dll' ('D:\OpenXP\inetsrv\uddi\source\Debug\uddi.mmc.dll') in project configuration 'Debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Link.OutputFile). |
| mmc\mmc.vcproj:
+ MSB8012: $(TargetPath) ('D:\OpenXP\inetsrv\uddi\source\mmc\Release\mmc.dll') does not match the Librarian's OutputFile property value 'Release\mmc.dll' ('D:\OpenXP\inetsrv\uddi\source\Release\mmc.dll') in project configuration 'Release|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Lib.OutputFile). |
| mmc\mmc.vcproj:
+ MSB8012: $(TargetName) ('mmc') does not match the Linker's OutputFile property value 'Release\uddi.mmc.dll' ('uddi.mmc') in project configuration 'Release|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetName) property value matches the value specified in %(Link.OutputFile). |
| mmc\mmc.vcproj:
+ MSB8012: $(TargetPath) ('D:\OpenXP\inetsrv\uddi\source\mmc\Release\mmc.dll') does not match the Linker's OutputFile property value 'Release\uddi.mmc.dll' ('D:\OpenXP\inetsrv\uddi\source\Release\uddi.mmc.dll') in project configuration 'Release|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Link.OutputFile). |
|
+ Show 5 additional messages
+ |
| mmc\mmc.vcproj:
+ Converting project file 'D:\OpenXP\inetsrv\uddi\source\mmc\mmc.vcproj'. |
| mmc\mmc.vcproj:
+ Visual C++ now provides improved safety in its C and C++ Libraries. This includes new and improved functions, additional checking and validation, and internal design changes. These libraries are turned on by default. You may see some warnings about unsafe functions or parameters when you build your project. The warnings will generally suggest an alternative safer coding style or function. It is advised that you correct these warnings, in order to make your code more safe. Full details can be found in the documentation by searching for 'Security Enhancements in the CRT' and for 'Checked Iterators'. |
| mmc\mmc.vcproj:
+ The C/C++ compiler default settings have been modified to be more compliant with ISO Standard C++. Included in those changes are enforcing Standard C++ for loop scoping and supporting wchar_t as a native type. These changes may cause existing code to no longer compile without changes to the code or the compiler options with which it is built. |
| mmc\mmc.vcproj:
+ Web deployment to the local IIS server is no longer supported. The Web Deployment build tool has been removed from your project settings. |
| mmc\mmc.vcproj:
+ Done converting to new project file 'D:\OpenXP\inetsrv\uddi\source\mmc\mmc.vcxproj'. |
|
+ Hide 5 additional messages
+ |
| filter\filter.vcproj:
+ Due to the requirement that Visual C++ projects produce an embedded (by default) Windows SxS manifest, manifest files in the project are now automatically built with the Manifest Tool. You may need to change your build in order for it to work correctly. For instance, it is recommended that the dependency information contained in any manifest files be converted to "#pragma comment(linker,"<insert dependency here>")" in a header file that is included from your source code. If your project already embeds a manifest in the RT_MANIFEST resource section through a resource (.rc) file, the line may need to be commented out before the project will build correctly. |
| filter\filter.vcproj:
+ Due to a conformance change in the C++ compiler, code change may be required before your project will build without errors. Previous versions of the C++ compiler allowed specification of member function pointers by member function name (e.g. MemberFunctionName). The C++ standard requires a fully qualified name with the use of the address-of operator (e.g. &ClassName::MemberFunctionName). If your project contains forms or controls used in the Windows Forms Designer, you may have to change code in InitializeComponent because the designer generated code used the non-conformant syntax in delegate construction (used in event handlers). |
| filter\filter.vcproj:
+ This application has been updated to include settings related to the User Account Control (UAC) feature of Windows Vista. By default, when run on Windows Vista with UAC enabled, this application is marked to run with the same privileges as the process that launched it. This marking also disables the application from running with virtualization. You can change UAC related settings from the Property Pages of the project. |
| filter\filter.vcproj:
+ VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings. |
| filter\filter.vcproj:
+ MSB8012: $(TargetPath) ('D:\OpenXP\inetsrv\uddi\source\filter\debug\filter.dll') does not match the Librarian's OutputFile property value '.\debug\filter.dll' ('D:\OpenXP\inetsrv\uddi\source\debug\filter.dll') in project configuration 'Unicode Debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Lib.OutputFile). |
| filter\filter.vcproj:
+ MSB8012: $(TargetName) ('filter') does not match the Linker's OutputFile property value '.\debug\uddi.filter.dll' ('uddi.filter') in project configuration 'Unicode Debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetName) property value matches the value specified in %(Link.OutputFile). |
| filter\filter.vcproj:
+ MSB8012: $(TargetPath) ('D:\OpenXP\inetsrv\uddi\source\filter\debug\filter.dll') does not match the Linker's OutputFile property value '.\debug\uddi.filter.dll' ('D:\OpenXP\inetsrv\uddi\source\debug\uddi.filter.dll') in project configuration 'Unicode Debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Link.OutputFile). |
| filter\filter.vcproj:
+ MSB8012: $(TargetPath) ('D:\OpenXP\inetsrv\uddi\source\filter\release\filter.dll') does not match the Librarian's OutputFile property value '.\release\filter.dll' ('D:\OpenXP\inetsrv\uddi\source\release\filter.dll') in project configuration 'Unicode Release|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Lib.OutputFile). |
| filter\filter.vcproj:
+ MSB8012: $(TargetName) ('filter') does not match the Linker's OutputFile property value '.\release\uddi.filter.dll' ('uddi.filter') in project configuration 'Unicode Release|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetName) property value matches the value specified in %(Link.OutputFile). |
| filter\filter.vcproj:
+ MSB8012: $(TargetPath) ('D:\OpenXP\inetsrv\uddi\source\filter\release\filter.dll') does not match the Linker's OutputFile property value '.\release\uddi.filter.dll' ('D:\OpenXP\inetsrv\uddi\source\release\uddi.filter.dll') in project configuration 'Unicode Release|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Link.OutputFile). |
|
+ Show 5 additional messages
+ |
| filter\filter.vcproj:
+ Converting project file 'D:\OpenXP\inetsrv\uddi\source\filter\filter.vcproj'. |
| filter\filter.vcproj:
+ Visual C++ now provides improved safety in its C and C++ Libraries. This includes new and improved functions, additional checking and validation, and internal design changes. These libraries are turned on by default. You may see some warnings about unsafe functions or parameters when you build your project. The warnings will generally suggest an alternative safer coding style or function. It is advised that you correct these warnings, in order to make your code more safe. Full details can be found in the documentation by searching for 'Security Enhancements in the CRT' and for 'Checked Iterators'. |
| filter\filter.vcproj:
+ The C/C++ compiler default settings have been modified to be more compliant with ISO Standard C++. Included in those changes are enforcing Standard C++ for loop scoping and supporting wchar_t as a native type. These changes may cause existing code to no longer compile without changes to the code or the compiler options with which it is built. |
| filter\filter.vcproj:
+ Web deployment to the local IIS server is no longer supported. The Web Deployment build tool has been removed from your project settings. |
| filter\filter.vcproj:
+ Done converting to new project file 'D:\OpenXP\inetsrv\uddi\source\filter\filter.vcxproj'. |
|
+ Hide 5 additional messages
+ |
| xp\xp.vcproj:
+ Due to the requirement that Visual C++ projects produce an embedded (by default) Windows SxS manifest, manifest files in the project are now automatically built with the Manifest Tool. You may need to change your build in order for it to work correctly. For instance, it is recommended that the dependency information contained in any manifest files be converted to "#pragma comment(linker,"<insert dependency here>")" in a header file that is included from your source code. If your project already embeds a manifest in the RT_MANIFEST resource section through a resource (.rc) file, the line may need to be commented out before the project will build correctly. |
| xp\xp.vcproj:
+ Due to a conformance change in the C++ compiler, code change may be required before your project will build without errors. Previous versions of the C++ compiler allowed specification of member function pointers by member function name (e.g. MemberFunctionName). The C++ standard requires a fully qualified name with the use of the address-of operator (e.g. &ClassName::MemberFunctionName). If your project contains forms or controls used in the Windows Forms Designer, you may have to change code in InitializeComponent because the designer generated code used the non-conformant syntax in delegate construction (used in event handlers). |
| xp\xp.vcproj:
+ This application has been updated to include settings related to the User Account Control (UAC) feature of Windows Vista. By default, when run on Windows Vista with UAC enabled, this application is marked to run with the same privileges as the process that launched it. This marking also disables the application from running with virtualization. You can change UAC related settings from the Property Pages of the project. |
| xp\xp.vcproj:
+ Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion. |
| xp\xp.vcproj:
+ VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings. |
| xp\xp.vcproj:
+ Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion. |
| xp\xp.vcproj:
+ MSB8012: $(TargetPath) ('D:\OpenXP\inetsrv\uddi\source\xp\Debug\xp.dll') does not match the Librarian's OutputFile property value 'Debug\xp.dll' ('D:\OpenXP\inetsrv\uddi\source\Debug\xp.dll') in project configuration 'Debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Lib.OutputFile). |
| xp\xp.vcproj:
+ MSB8012: $(TargetPath) ('D:\OpenXP\inetsrv\uddi\source\xp\Debug\xp.dll') does not match the Linker's OutputFile property value 'Debug\xp.dll' ('D:\OpenXP\inetsrv\uddi\source\Debug\xp.dll') in project configuration 'Debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Link.OutputFile). |
| xp\xp.vcproj:
+ MSB8012: $(TargetPath) ('D:\OpenXP\inetsrv\uddi\source\xp\Release\xp.dll') does not match the Librarian's OutputFile property value 'Release\xp.dll' ('D:\OpenXP\inetsrv\uddi\source\Release\xp.dll') in project configuration 'Release|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Lib.OutputFile). |
| xp\xp.vcproj:
+ MSB8012: $(TargetPath) ('D:\OpenXP\inetsrv\uddi\source\xp\Release\xp.dll') does not match the Linker's OutputFile property value 'Release\xp.dll' ('D:\OpenXP\inetsrv\uddi\source\Release\xp.dll') in project configuration 'Release|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Link.OutputFile). |
|
+ Show 5 additional messages
+ |
| xp\xp.vcproj:
+ Converting project file 'D:\OpenXP\inetsrv\uddi\source\xp\xp.vcproj'. |
| xp\xp.vcproj:
+ Visual C++ now provides improved safety in its C and C++ Libraries. This includes new and improved functions, additional checking and validation, and internal design changes. These libraries are turned on by default. You may see some warnings about unsafe functions or parameters when you build your project. The warnings will generally suggest an alternative safer coding style or function. It is advised that you correct these warnings, in order to make your code more safe. Full details can be found in the documentation by searching for 'Security Enhancements in the CRT' and for 'Checked Iterators'. |
| xp\xp.vcproj:
+ The C/C++ compiler default settings have been modified to be more compliant with ISO Standard C++. Included in those changes are enforcing Standard C++ for loop scoping and supporting wchar_t as a native type. These changes may cause existing code to no longer compile without changes to the code or the compiler options with which it is built. |
| xp\xp.vcproj:
+ Web deployment to the local IIS server is no longer supported. The Web Deployment build tool has been removed from your project settings. |
| xp\xp.vcproj:
+ Done converting to new project file 'D:\OpenXP\inetsrv\uddi\source\xp\xp.vcxproj'. |
|
+ Hide 5 additional messages
+ |
