| ACM\lameACM_vc7.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. |
| ACM\lameACM_vc7.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). |
| ACM\lameACM_vc7.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. |
| ACM\lameACM_vc7.vcproj:
The C/C++ compiler switch /YX is lo longer supported. /YX has been removed from your project settings. |
| ACM\lameACM_vc7.vcproj:
VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings. |
| ACM\lameACM_vc7.vcproj:
The C/C++ compiler switch /Og has been deprecated and has been removed from your project settings. It is recommended that you use /O1 or /O2 instead. |
| ACM\lameACM_vc7.vcproj:
VCConvertEngine could not convert attribute GlobalOptimizations = TRUE under Tool VCCLCompilerTool. |
| ACM\lameACM_vc7.vcproj:
VCConvertEngine could not convert attribute GlobalOptimizations = TRUE under Tool VCCLCompilerTool. |
| ACM\lameACM_vc7.vcproj:
VCConvertEngine could not convert attribute GlobalOptimizations = TRUE under Tool VCCLCompilerTool. |
| ACM\lameACM_vc7.vcproj:
VCConvertEngine could not convert attribute GlobalOptimizations = TRUE under Tool VCCLCompilerTool. |
| ACM\lameACM_vc7.vcproj:
All user macros reported below for configuration 'LAME debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\lameACM_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\lameACM_vc7.vcproj:
All user macros reported below for configuration 'Debug NASM|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\lameACM_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\lameACM_vc7.vcproj:
All user macros reported below for configuration 'dll release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\lameACM_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\lameACM_vc7.vcproj:
All user macros reported below for configuration 'dll release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\lameACM_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\lameACM_vc7.vcproj:
All user macros reported below for configuration 'dll debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\lameACM_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\lameACM_vc7.vcproj:
All user macros reported below for configuration 'Release NASM|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\lameACM_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\lameACM_vc7.vcproj:
All user macros reported below for configuration 'Debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\lameACM_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\lameACM_vc7.vcproj:
All user macros reported below for configuration 'LAME release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\lameACM_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\lameACM_vc7.vcproj:
All user macros reported below for configuration 'Release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\lameACM_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\lameACM_vc7.vcproj:
All user macros reported below for configuration 'LAME release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\lameACM_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\LAME debug\lameACM.dll') does not match the Librarian's OutputFile property value 'LAME debug\lameACM.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME debug\lameACM.dll') in project configuration 'LAME 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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetExt) ('.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('.acm') in project configuration 'LAME debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetExt) property value matches the value specified in %(Link.OutputFile). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\LAME debug\lameACM.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\output\lameACM.acm') in project configuration 'LAME 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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\.\Debug_NASM\lameACM.dll') does not match the Librarian's OutputFile property value '.\Debug_NASM\lameACM.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug_NASM\lameACM.dll') in project configuration 'Debug NASM|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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetExt) ('.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('.acm') in project configuration 'Debug NASM|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetExt) property value matches the value specified in %(Link.OutputFile). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\.\Debug_NASM\lameACM.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\output\lameACM.acm') in project configuration 'Debug NASM|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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\dll release\lameACM.dll') does not match the Librarian's OutputFile property value 'dll release\lameACM.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release\lameACM.dll') in project configuration 'dll 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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetExt) ('.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('.acm') in project configuration 'dll release|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetExt) property value matches the value specified in %(Link.OutputFile). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\dll release\lameACM.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\output\lameACM.acm') in project configuration 'dll 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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\dll release Nasm\lameACM.dll') does not match the Librarian's OutputFile property value 'dll release Nasm\lameACM.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release Nasm\lameACM.dll') in project configuration 'dll release Nasm|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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetExt) ('.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('.acm') in project configuration 'dll release Nasm|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetExt) property value matches the value specified in %(Link.OutputFile). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\dll release Nasm\lameACM.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\output\lameACM.acm') in project configuration 'dll release Nasm|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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\dll debug\lameACM.dll') does not match the Librarian's OutputFile property value 'dll debug\lameACM.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll debug\lameACM.dll') in project configuration 'dll 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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetExt) ('.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('.acm') in project configuration 'dll debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetExt) property value matches the value specified in %(Link.OutputFile). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\dll debug\lameACM.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\output\lameACM.acm') in project configuration 'dll 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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\.\Release_NASM\lameACM.dll') does not match the Librarian's OutputFile property value '.\Release_NASM\lameACM.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release_NASM\lameACM.dll') in project configuration 'Release NASM|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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetExt) ('.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('.acm') in project configuration 'Release NASM|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetExt) property value matches the value specified in %(Link.OutputFile). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\.\Release_NASM\lameACM.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\output\lameACM.acm') in project configuration 'Release NASM|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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\.\Debug\lameACM.dll') does not match the Librarian's OutputFile property value '.\Debug\lameACM.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\lameACM.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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetExt) ('.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('.acm') in project configuration 'Debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetExt) property value matches the value specified in %(Link.OutputFile). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\.\Debug\lameACM.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\output\lameACM.acm') 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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\LAME release\lameACM.dll') does not match the Librarian's OutputFile property value 'LAME release\lameACM.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release\lameACM.dll') in project configuration 'LAME 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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetExt) ('.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('.acm') in project configuration 'LAME release|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetExt) property value matches the value specified in %(Link.OutputFile). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\LAME release\lameACM.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\output\lameACM.acm') in project configuration 'LAME 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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\.\Release\lameACM.dll') does not match the Librarian's OutputFile property value '.\Release\lameACM.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\lameACM.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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetExt) ('.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('.acm') in project configuration 'Release|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetExt) property value matches the value specified in %(Link.OutputFile). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\.\Release\lameACM.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\output\lameACM.acm') 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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\LAME release Nasm\lameACM.dll') does not match the Librarian's OutputFile property value 'LAME release Nasm\lameACM.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release Nasm\lameACM.dll') in project configuration 'LAME release Nasm|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). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetExt) ('.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('.acm') in project configuration 'LAME release Nasm|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetExt) property value matches the value specified in %(Link.OutputFile). |
| ACM\lameACM_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\LAME release Nasm\lameACM.dll') does not match the Linker's OutputFile property value '..\output\lameACM.acm' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\output\lameACM.acm') in project configuration 'LAME release Nasm|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
|
| ACM\lameACM_vc7.vcproj:
Converting project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\lameACM_vc7.vcproj'. |
| ACM\lameACM_vc7.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'. |
| ACM\lameACM_vc7.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. |
| ACM\lameACM_vc7.vcproj:
Web deployment to the local IIS server is no longer supported. The Web Deployment build tool has been removed from your project settings. |
| ACM\lameACM_vc7.vcproj:
Done converting to new project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\lameACM_vc7.vcxproj'. |
|
Hide 5 additional messages
|
| Dll\LameDll_vc7.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. |
| Dll\LameDll_vc7.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). |
| Dll\LameDll_vc7.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. |
| Dll\LameDll_vc7.vcproj:
The C/C++ compiler switch /YX is lo longer supported. /YX has been removed from your project settings. |
| Dll\LameDll_vc7.vcproj:
VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings. |
| Dll\LameDll_vc7.vcproj:
All user macros reported below for configuration 'LAME debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| Dll\LameDll_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| Dll\LameDll_vc7.vcproj:
All user macros reported below for configuration 'dll release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| Dll\LameDll_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| Dll\LameDll_vc7.vcproj:
All user macros reported below for configuration 'dll release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| Dll\LameDll_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| Dll\LameDll_vc7.vcproj:
All user macros reported below for configuration 'dll debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| Dll\LameDll_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| Dll\LameDll_vc7.vcproj:
All user macros reported below for configuration 'Release NASM|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| Dll\LameDll_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| Dll\LameDll_vc7.vcproj:
All user macros reported below for configuration 'Debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| Dll\LameDll_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| Dll\LameDll_vc7.vcproj:
All user macros reported below for configuration 'LAME release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| Dll\LameDll_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| Dll\LameDll_vc7.vcproj:
All user macros reported below for configuration 'Release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| Dll\LameDll_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| Dll\LameDll_vc7.vcproj:
All user macros reported below for configuration 'LAME release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| Dll\LameDll_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\LAME debug\LameMp3EncDll.dll') does not match the Librarian's OutputFile property value 'LAME debug\LameMp3EncDll.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME debug\LameMp3EncDll.dll') in project configuration 'LAME 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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetName) ('LameMp3EncDll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('lame_enc') in project configuration 'LAME 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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\LAME debug\LameMp3EncDll.dll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame_enc.dll') in project configuration 'LAME 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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\dll release\LameMp3EncDll.dll') does not match the Librarian's OutputFile property value 'dll release\LameMp3EncDll.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release\LameMp3EncDll.dll') in project configuration 'dll 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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetName) ('LameMp3EncDll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('lame_enc') in project configuration 'dll 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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\dll release\LameMp3EncDll.dll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame_enc.dll') in project configuration 'dll 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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\dll release Nasm\LameMp3EncDll.dll') does not match the Librarian's OutputFile property value 'dll release Nasm\LameMp3EncDll.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release Nasm\LameMp3EncDll.dll') in project configuration 'dll release Nasm|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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetName) ('LameMp3EncDll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('lame_enc') in project configuration 'dll release Nasm|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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\dll release Nasm\LameMp3EncDll.dll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame_enc.dll') in project configuration 'dll release Nasm|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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\dll debug\LameMp3EncDll.dll') does not match the Librarian's OutputFile property value 'dll debug\LameMp3EncDll.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll debug\LameMp3EncDll.dll') in project configuration 'dll 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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetName) ('LameMp3EncDll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('lame_enc') in project configuration 'dll 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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\dll debug\LameMp3EncDll.dll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame_enc.dll') in project configuration 'dll 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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\.\Release\LameMp3EncDll.dll') does not match the Librarian's OutputFile property value '.\Release\LameMp3EncDll.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\LameMp3EncDll.dll') in project configuration 'Release NASM|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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetName) ('LameMp3EncDll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('lame_enc') in project configuration 'Release NASM|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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\.\Release\LameMp3EncDll.dll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame_enc.dll') in project configuration 'Release NASM|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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\.\Debug\LameMp3EncDll.dll') does not match the Librarian's OutputFile property value '.\Debug\LameMp3EncDll.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\LameMp3EncDll.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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetName) ('LameMp3EncDll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('lame_enc') 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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\.\Debug\LameMp3EncDll.dll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame_enc.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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\LAME release\LameMp3EncDll.dll') does not match the Librarian's OutputFile property value 'LAME release\LameMp3EncDll.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release\LameMp3EncDll.dll') in project configuration 'LAME 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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetName) ('LameMp3EncDll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('lame_enc') in project configuration 'LAME 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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\LAME release\LameMp3EncDll.dll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame_enc.dll') in project configuration 'LAME 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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\.\Release\LameMp3EncDll.dll') does not match the Librarian's OutputFile property value '.\Release\LameMp3EncDll.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\LameMp3EncDll.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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetName) ('LameMp3EncDll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('lame_enc') 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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\.\Release\LameMp3EncDll.dll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame_enc.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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\LAME release Nasm\LameMp3EncDll.dll') does not match the Librarian's OutputFile property value 'LAME release Nasm\LameMp3EncDll.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release Nasm\LameMp3EncDll.dll') in project configuration 'LAME release Nasm|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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetName) ('LameMp3EncDll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('lame_enc') in project configuration 'LAME release Nasm|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). |
| Dll\LameDll_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\LAME release Nasm\LameMp3EncDll.dll') does not match the Linker's OutputFile property value '../output/lame_enc.dll' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame_enc.dll') in project configuration 'LAME release Nasm|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 6 additional messages
|
| Dll\LameDll_vc7.vcproj:
Converting project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\LameDll_vc7.vcproj'. |
| Dll\LameDll_vc7.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'. |
| Dll\LameDll_vc7.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. |
| Dll\LameDll_vc7.vcproj:
The single-threaded run-time library switches (/MLd, /ML) have been removed from the C++ compiler. The project has been automatically converted to use the corresponding multi-threaded run-time library switches (/MTd, /MT). |
| Dll\LameDll_vc7.vcproj:
Web deployment to the local IIS server is no longer supported. The Web Deployment build tool has been removed from your project settings. |
| Dll\LameDll_vc7.vcproj:
Done converting to new project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Dll\LameDll_vc7.vcxproj'. |
|
Hide 6 additional messages
|
| libmp3lame\libmp3lame_vc7.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. |
| libmp3lame\libmp3lame_vc7.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). |
| libmp3lame\libmp3lame_vc7.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. |
| libmp3lame\libmp3lame_vc7.vcproj:
VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings. |
| libmp3lame\libmp3lame_vc7.vcproj:
VCConvertEngine could not convert attribute OptimizeForProcessor = 3 under Tool VCCLCompilerTool. |
| libmp3lame\libmp3lame_vc7.vcproj:
All user macros reported below for configuration 'LAME debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| libmp3lame\libmp3lame_vc7.vcproj:
All user macros reported below for configuration 'dll release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| libmp3lame\libmp3lame_vc7.vcproj:
All user macros reported below for configuration 'dll release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| libmp3lame\libmp3lame_vc7.vcproj:
All user macros reported below for configuration 'Release GTK|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| libmp3lame\libmp3lame_vc7.vcproj:
All user macros reported below for configuration 'dll debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| libmp3lame\libmp3lame_vc7.vcproj:
All user macros reported below for configuration 'Release NASM|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| libmp3lame\libmp3lame_vc7.vcproj:
All user macros reported below for configuration 'Debug GTK|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| libmp3lame\libmp3lame_vc7.vcproj:
All user macros reported below for configuration 'Debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| libmp3lame\libmp3lame_vc7.vcproj:
All user macros reported below for configuration 'LAME release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| libmp3lame\libmp3lame_vc7.vcproj:
All user macros reported below for configuration 'Release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| libmp3lame\libmp3lame_vc7.vcproj:
All user macros reported below for configuration 'LAME release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\LAME debug\libmp3lame.lib') does not match the Librarian's OutputFile property value 'Debug\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\libmp3lame.lib') in project configuration 'LAME 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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\LAME debug\libmp3lame.lib') does not match the Linker's OutputFile property value 'LAME debug\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME debug\libmp3lame.lib') in project configuration 'LAME 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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\dll release\libmp3lame.lib') does not match the Librarian's OutputFile property value 'Debug\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\libmp3lame.lib') in project configuration 'dll 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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\dll release\libmp3lame.lib') does not match the Linker's OutputFile property value 'dll release\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release\libmp3lame.lib') in project configuration 'dll 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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\dll release Nasm\libmp3lame.lib') does not match the Librarian's OutputFile property value 'Release\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\libmp3lame.lib') in project configuration 'dll release Nasm|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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\dll release Nasm\libmp3lame.lib') does not match the Linker's OutputFile property value 'dll release Nasm\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release Nasm\libmp3lame.lib') in project configuration 'dll release Nasm|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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\.\libmp3lame___Win32_Release_GTK\libmp3lame.lib') does not match the Librarian's OutputFile property value 'Release\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\libmp3lame.lib') in project configuration 'Release GTK|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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\.\libmp3lame___Win32_Release_GTK\libmp3lame.lib') does not match the Linker's OutputFile property value '.\libmp3lame___Win32_Release_GTK\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame___Win32_Release_GTK\libmp3lame.lib') in project configuration 'Release GTK|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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\dll debug\libmp3lame.lib') does not match the Librarian's OutputFile property value 'Debug\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\libmp3lame.lib') in project configuration 'dll 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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\dll debug\libmp3lame.lib') does not match the Linker's OutputFile property value 'dll debug\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll debug\libmp3lame.lib') in project configuration 'dll 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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\.\Release_NASM\libmp3lame.lib') does not match the Librarian's OutputFile property value 'Release_NASM\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release_NASM\libmp3lame.lib') in project configuration 'Release NASM|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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\.\Release_NASM\libmp3lame.lib') does not match the Linker's OutputFile property value '.\Release_NASM\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release_NASM\libmp3lame.lib') in project configuration 'Release NASM|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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\.\libmp3lame___Win32_Debug_GTK\libmp3lame.lib') does not match the Librarian's OutputFile property value 'Debug\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\libmp3lame.lib') in project configuration 'Debug GTK|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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\.\libmp3lame___Win32_Debug_GTK\libmp3lame.lib') does not match the Linker's OutputFile property value '.\libmp3lame___Win32_Debug_GTK\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame___Win32_Debug_GTK\libmp3lame.lib') in project configuration 'Debug GTK|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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\.\Debug\libmp3lame.lib') does not match the Librarian's OutputFile property value 'Debug\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\libmp3lame.lib') 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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\.\Debug\libmp3lame.lib') does not match the Linker's OutputFile property value '.\Debug\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\libmp3lame.lib') 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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\LAME release\libmp3lame.lib') does not match the Librarian's OutputFile property value 'Debug\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\libmp3lame.lib') in project configuration 'LAME 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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\LAME release\libmp3lame.lib') does not match the Linker's OutputFile property value 'LAME release\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release\libmp3lame.lib') in project configuration 'LAME 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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\.\Release\libmp3lame.lib') does not match the Librarian's OutputFile property value 'Release\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\libmp3lame.lib') 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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\.\Release\libmp3lame.lib') does not match the Linker's OutputFile property value '.\Release\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\libmp3lame.lib') 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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\LAME release Nasm\libmp3lame.lib') does not match the Librarian's OutputFile property value 'Release\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\libmp3lame.lib') in project configuration 'LAME release Nasm|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). |
| libmp3lame\libmp3lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\LAME release Nasm\libmp3lame.lib') does not match the Linker's OutputFile property value 'LAME release Nasm\libmp3lame.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release Nasm\libmp3lame.lib') in project configuration 'LAME release Nasm|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
|
| libmp3lame\libmp3lame_vc7.vcproj:
Converting project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\libmp3lame_vc7.vcproj'. |
| libmp3lame\libmp3lame_vc7.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'. |
| libmp3lame\libmp3lame_vc7.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. |
| libmp3lame\libmp3lame_vc7.vcproj:
The single-threaded run-time library switches (/MLd, /ML) have been removed from the C++ compiler. The project has been automatically converted to use the corresponding multi-threaded run-time library switches (/MTd, /MT). |
| libmp3lame\libmp3lame_vc7.vcproj:
Done converting to new project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\libmp3lame\libmp3lame_vc7.vcxproj'. |
|
Hide 5 additional messages
|
| mpglib\mpglib_vc7.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. |
| mpglib\mpglib_vc7.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). |
| mpglib\mpglib_vc7.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. |
| mpglib\mpglib_vc7.vcproj:
VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings. |
| mpglib\mpglib_vc7.vcproj:
The C/C++ compiler switch /YX is lo longer supported. /YX has been removed from your project settings. |
| mpglib\mpglib_vc7.vcproj:
All user macros reported below for configuration 'LAME debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| mpglib\mpglib_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| mpglib\mpglib_vc7.vcproj:
All user macros reported below for configuration 'dll release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| mpglib\mpglib_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| mpglib\mpglib_vc7.vcproj:
All user macros reported below for configuration 'dll release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| mpglib\mpglib_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| mpglib\mpglib_vc7.vcproj:
All user macros reported below for configuration 'Release GTK|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| mpglib\mpglib_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| mpglib\mpglib_vc7.vcproj:
All user macros reported below for configuration 'dll debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| mpglib\mpglib_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| mpglib\mpglib_vc7.vcproj:
All user macros reported below for configuration 'Release NASM|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| mpglib\mpglib_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| mpglib\mpglib_vc7.vcproj:
All user macros reported below for configuration 'Debug GTK|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| mpglib\mpglib_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| mpglib\mpglib_vc7.vcproj:
All user macros reported below for configuration 'Debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| mpglib\mpglib_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| mpglib\mpglib_vc7.vcproj:
All user macros reported below for configuration 'LAME release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| mpglib\mpglib_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| mpglib\mpglib_vc7.vcproj:
All user macros reported below for configuration 'Release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| mpglib\mpglib_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| mpglib\mpglib_vc7.vcproj:
All user macros reported below for configuration 'LAME release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| mpglib\mpglib_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\LAME debug\mpglib.lib') does not match the Librarian's OutputFile property value 'Debug\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\mpglib.lib') in project configuration 'LAME 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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\LAME debug\mpglib.lib') does not match the Linker's OutputFile property value 'LAME debug\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME debug\mpglib.lib') in project configuration 'LAME 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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\dll release\mpglib.lib') does not match the Librarian's OutputFile property value 'Debug\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\mpglib.lib') in project configuration 'dll 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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\dll release\mpglib.lib') does not match the Linker's OutputFile property value 'dll release\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release\mpglib.lib') in project configuration 'dll 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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\dll release Nasm\mpglib.lib') does not match the Librarian's OutputFile property value 'Release\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\mpglib.lib') in project configuration 'dll release Nasm|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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\dll release Nasm\mpglib.lib') does not match the Linker's OutputFile property value 'dll release Nasm\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release Nasm\mpglib.lib') in project configuration 'dll release Nasm|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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\.\mpglib___Win32_Release_GTK\mpglib.lib') does not match the Librarian's OutputFile property value 'Release\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\mpglib.lib') in project configuration 'Release GTK|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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\.\mpglib___Win32_Release_GTK\mpglib.lib') does not match the Linker's OutputFile property value '.\mpglib___Win32_Release_GTK\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib___Win32_Release_GTK\mpglib.lib') in project configuration 'Release GTK|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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\dll debug\mpglib.lib') does not match the Librarian's OutputFile property value 'Debug\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\mpglib.lib') in project configuration 'dll 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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\dll debug\mpglib.lib') does not match the Linker's OutputFile property value 'dll debug\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll debug\mpglib.lib') in project configuration 'dll 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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\.\mpglib___Win32_Release_NASM\mpglib.lib') does not match the Librarian's OutputFile property value 'Release\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\mpglib.lib') in project configuration 'Release NASM|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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\.\mpglib___Win32_Release_NASM\mpglib.lib') does not match the Linker's OutputFile property value '.\mpglib___Win32_Release_NASM\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib___Win32_Release_NASM\mpglib.lib') in project configuration 'Release NASM|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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\.\mpglib___Win32_Debug_GTK\mpglib.lib') does not match the Librarian's OutputFile property value 'Debug\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\mpglib.lib') in project configuration 'Debug GTK|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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\.\mpglib___Win32_Debug_GTK\mpglib.lib') does not match the Linker's OutputFile property value '.\mpglib___Win32_Debug_GTK\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib___Win32_Debug_GTK\mpglib.lib') in project configuration 'Debug GTK|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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\.\Debug\mpglib.lib') does not match the Librarian's OutputFile property value 'Debug\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\mpglib.lib') 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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\.\Debug\mpglib.lib') does not match the Linker's OutputFile property value '.\Debug\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\mpglib.lib') 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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\LAME release\mpglib.lib') does not match the Librarian's OutputFile property value 'Debug\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\mpglib.lib') in project configuration 'LAME 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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\LAME release\mpglib.lib') does not match the Linker's OutputFile property value 'LAME release\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release\mpglib.lib') in project configuration 'LAME 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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\.\Release\mpglib.lib') does not match the Librarian's OutputFile property value 'Release\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\mpglib.lib') 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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\.\Release\mpglib.lib') does not match the Linker's OutputFile property value '.\Release\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\mpglib.lib') 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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\LAME release Nasm\mpglib.lib') does not match the Librarian's OutputFile property value 'Release\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\mpglib.lib') in project configuration 'LAME release Nasm|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). |
| mpglib\mpglib_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\LAME release Nasm\mpglib.lib') does not match the Linker's OutputFile property value 'LAME release Nasm\mpglib.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release Nasm\mpglib.lib') in project configuration 'LAME release Nasm|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
|
| mpglib\mpglib_vc7.vcproj:
Converting project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\mpglib_vc7.vcproj'. |
| mpglib\mpglib_vc7.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'. |
| mpglib\mpglib_vc7.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. |
| mpglib\mpglib_vc7.vcproj:
The single-threaded run-time library switches (/MLd, /ML) have been removed from the C++ compiler. The project has been automatically converted to use the corresponding multi-threaded run-time library switches (/MTd, /MT). |
| mpglib\mpglib_vc7.vcproj:
Done converting to new project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\mpglib\mpglib_vc7.vcxproj'. |
|
Hide 5 additional messages
|
| frontend\lame_vc7.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. |
| frontend\lame_vc7.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). |
| frontend\lame_vc7.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. |
| frontend\lame_vc7.vcproj:
The C/C++ compiler switch /YX is lo longer supported. /YX has been removed from your project settings. |
| frontend\lame_vc7.vcproj:
VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings. |
| frontend\lame_vc7.vcproj:
All user macros reported below for configuration 'LAME debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\lame_vc7.vcproj:
All user macros reported below for configuration 'dll release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\lame_vc7.vcproj:
All user macros reported below for configuration 'dll release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\lame_vc7.vcproj:
All user macros reported below for configuration 'dll debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\lame_vc7.vcproj:
All user macros reported below for configuration 'Release NASM|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\lame_vc7.vcproj:
All user macros reported below for configuration 'Debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\lame_vc7.vcproj:
All user macros reported below for configuration 'LAME release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\lame_vc7.vcproj:
All user macros reported below for configuration 'Release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\lame_vc7.vcproj:
All user macros reported below for configuration 'LAME release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\lame_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\LAME debug\lame.exe') does not match the Librarian's OutputFile property value 'LAME debug\lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME debug\lame.exe') in project configuration 'LAME 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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\LAME debug\lame.exe') does not match the Linker's OutputFile property value '../output/lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame.exe') in project configuration 'LAME 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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\dll release\lame.exe') does not match the Librarian's OutputFile property value 'dll release\lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release\lame.exe') in project configuration 'dll 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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\dll release\lame.exe') does not match the Linker's OutputFile property value '../output/lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame.exe') in project configuration 'dll 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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\dll release Nasm\lame.exe') does not match the Librarian's OutputFile property value 'dll release Nasm\lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release Nasm\lame.exe') in project configuration 'dll release Nasm|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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\dll release Nasm\lame.exe') does not match the Linker's OutputFile property value '../output/lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame.exe') in project configuration 'dll release Nasm|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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\dll debug\lame.exe') does not match the Librarian's OutputFile property value 'dll debug\lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll debug\lame.exe') in project configuration 'dll 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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\dll debug\lame.exe') does not match the Linker's OutputFile property value '../output/lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame.exe') in project configuration 'dll 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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\.\Release_NASM\lame.exe') does not match the Librarian's OutputFile property value '.\Release_NASM\lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release_NASM\lame.exe') in project configuration 'Release NASM|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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\.\Release_NASM\lame.exe') does not match the Linker's OutputFile property value '../output/lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame.exe') in project configuration 'Release NASM|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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\.\Debug\lame.exe') does not match the Librarian's OutputFile property value '.\Debug\lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\lame.exe') 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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\.\Debug\lame.exe') does not match the Linker's OutputFile property value '../output/lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame.exe') 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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\LAME release\lame.exe') does not match the Librarian's OutputFile property value 'LAME release\lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release\lame.exe') in project configuration 'LAME 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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\LAME release\lame.exe') does not match the Linker's OutputFile property value '../output/lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame.exe') in project configuration 'LAME 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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\.\Release\lame.exe') does not match the Librarian's OutputFile property value '.\Release\lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\lame.exe') 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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\.\Release\lame.exe') does not match the Linker's OutputFile property value '../output/lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame.exe') 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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\LAME release Nasm\lame.exe') does not match the Librarian's OutputFile property value 'LAME release Nasm\lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release Nasm\lame.exe') in project configuration 'LAME release Nasm|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). |
| frontend\lame_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\LAME release Nasm\lame.exe') does not match the Linker's OutputFile property value '../output/lame.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/lame.exe') in project configuration 'LAME release Nasm|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 6 additional messages
|
| frontend\lame_vc7.vcproj:
Converting project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\lame_vc7.vcproj'. |
| frontend\lame_vc7.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'. |
| frontend\lame_vc7.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. |
| frontend\lame_vc7.vcproj:
The single-threaded run-time library switches (/MLd, /ML) have been removed from the C++ compiler. The project has been automatically converted to use the corresponding multi-threaded run-time library switches (/MTd, /MT). |
| frontend\lame_vc7.vcproj:
Web deployment to the local IIS server is no longer supported. The Web Deployment build tool has been removed from your project settings. |
| frontend\lame_vc7.vcproj:
Done converting to new project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\lame_vc7.vcxproj'. |
|
Hide 6 additional messages
|
| ACM\ADbg\ADbg_vc7.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. |
| ACM\ADbg\ADbg_vc7.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). |
| ACM\ADbg\ADbg_vc7.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. |
| ACM\ADbg\ADbg_vc7.vcproj:
The C/C++ compiler switch /YX is lo longer supported. /YX has been removed from your project settings. |
| ACM\ADbg\ADbg_vc7.vcproj:
VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings. |
| ACM\ADbg\ADbg_vc7.vcproj:
All user macros reported below for configuration 'LAME debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\ADbg\ADbg_vc7.vcproj:
All user macros reported below for configuration 'dll release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\ADbg\ADbg_vc7.vcproj:
All user macros reported below for configuration 'dll release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\ADbg\ADbg_vc7.vcproj:
All user macros reported below for configuration 'dll debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\ADbg\ADbg_vc7.vcproj:
All user macros reported below for configuration 'Debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\ADbg\ADbg_vc7.vcproj:
All user macros reported below for configuration 'LAME release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\ADbg\ADbg_vc7.vcproj:
All user macros reported below for configuration 'Release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\ADbg\ADbg_vc7.vcproj:
All user macros reported below for configuration 'LAME release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\LAME debug\ADbg.lib') does not match the Librarian's OutputFile property value '.\Debug\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\ADbg.lib') in project configuration 'LAME 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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\LAME debug\ADbg.lib') does not match the Linker's OutputFile property value 'LAME debug\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME debug\ADbg.lib') in project configuration 'LAME 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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\dll release\ADbg.lib') does not match the Librarian's OutputFile property value '.\Debug\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\ADbg.lib') in project configuration 'dll 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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\dll release\ADbg.lib') does not match the Linker's OutputFile property value 'dll release\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release\ADbg.lib') in project configuration 'dll 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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\dll release Nasm\ADbg.lib') does not match the Librarian's OutputFile property value '.\Release\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\ADbg.lib') in project configuration 'dll release Nasm|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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\dll release Nasm\ADbg.lib') does not match the Linker's OutputFile property value 'dll release Nasm\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release Nasm\ADbg.lib') in project configuration 'dll release Nasm|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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\dll debug\ADbg.lib') does not match the Librarian's OutputFile property value '.\Debug\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\ADbg.lib') in project configuration 'dll 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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\dll debug\ADbg.lib') does not match the Linker's OutputFile property value 'dll debug\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll debug\ADbg.lib') in project configuration 'dll 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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\.\Debug\ADbg.lib') does not match the Librarian's OutputFile property value '.\Debug\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\ADbg.lib') 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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\.\Debug\ADbg.lib') does not match the Linker's OutputFile property value '.\Debug\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\ADbg.lib') 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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\LAME release\ADbg.lib') does not match the Librarian's OutputFile property value '.\Debug\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\ADbg.lib') in project configuration 'LAME 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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\LAME release\ADbg.lib') does not match the Linker's OutputFile property value 'LAME release\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release\ADbg.lib') in project configuration 'LAME 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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\.\Release\ADbg.lib') does not match the Librarian's OutputFile property value '.\Release\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\ADbg.lib') 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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\.\Release\ADbg.lib') does not match the Linker's OutputFile property value '.\Release\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\ADbg.lib') 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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\LAME release Nasm\ADbg.lib') does not match the Librarian's OutputFile property value '.\Release\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\ADbg.lib') in project configuration 'LAME release Nasm|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). |
| ACM\ADbg\ADbg_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\LAME release Nasm\ADbg.lib') does not match the Linker's OutputFile property value 'LAME release Nasm\ADbg.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release Nasm\ADbg.lib') in project configuration 'LAME release Nasm|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
|
| ACM\ADbg\ADbg_vc7.vcproj:
Converting project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\ADbg_vc7.vcproj'. |
| ACM\ADbg\ADbg_vc7.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'. |
| ACM\ADbg\ADbg_vc7.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. |
| ACM\ADbg\ADbg_vc7.vcproj:
The single-threaded run-time library switches (/MLd, /ML) have been removed from the C++ compiler. The project has been automatically converted to use the corresponding multi-threaded run-time library switches (/MTd, /MT). |
| ACM\ADbg\ADbg_vc7.vcproj:
Done converting to new project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\ADbg\ADbg_vc7.vcxproj'. |
|
Hide 5 additional messages
|
| ACM\tinyxml\tinyxml_vc7.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. |
| ACM\tinyxml\tinyxml_vc7.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). |
| ACM\tinyxml\tinyxml_vc7.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. |
| ACM\tinyxml\tinyxml_vc7.vcproj:
The C/C++ compiler switch /YX is lo longer supported. /YX has been removed from your project settings. |
| ACM\tinyxml\tinyxml_vc7.vcproj:
VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings. |
| ACM\tinyxml\tinyxml_vc7.vcproj:
All user macros reported below for configuration 'LAME debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\tinyxml\tinyxml_vc7.vcproj:
All user macros reported below for configuration 'dll release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\tinyxml\tinyxml_vc7.vcproj:
All user macros reported below for configuration 'dll release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\tinyxml\tinyxml_vc7.vcproj:
All user macros reported below for configuration 'dll debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\tinyxml\tinyxml_vc7.vcproj:
All user macros reported below for configuration 'Debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\tinyxml\tinyxml_vc7.vcproj:
All user macros reported below for configuration 'LAME release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\tinyxml\tinyxml_vc7.vcproj:
All user macros reported below for configuration 'Release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\tinyxml\tinyxml_vc7.vcproj:
All user macros reported below for configuration 'LAME release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\LAME debug\tinyxml.lib') does not match the Librarian's OutputFile property value '.\Debug\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\tinyxml.lib') in project configuration 'LAME 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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\LAME debug\tinyxml.lib') does not match the Linker's OutputFile property value 'LAME debug\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME debug\tinyxml.lib') in project configuration 'LAME 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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\dll release\tinyxml.lib') does not match the Librarian's OutputFile property value '.\Debug\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\tinyxml.lib') in project configuration 'dll 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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\dll release\tinyxml.lib') does not match the Linker's OutputFile property value 'dll release\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release\tinyxml.lib') in project configuration 'dll 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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\dll release Nasm\tinyxml.lib') does not match the Librarian's OutputFile property value '.\Release\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\tinyxml.lib') in project configuration 'dll release Nasm|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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\dll release Nasm\tinyxml.lib') does not match the Linker's OutputFile property value 'dll release Nasm\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release Nasm\tinyxml.lib') in project configuration 'dll release Nasm|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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\dll debug\tinyxml.lib') does not match the Librarian's OutputFile property value '.\Debug\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\tinyxml.lib') in project configuration 'dll 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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\dll debug\tinyxml.lib') does not match the Linker's OutputFile property value 'dll debug\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll debug\tinyxml.lib') in project configuration 'dll 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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\.\Debug\tinyxml.lib') does not match the Librarian's OutputFile property value '.\Debug\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\tinyxml.lib') 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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\.\Debug\tinyxml.lib') does not match the Linker's OutputFile property value '.\Debug\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\tinyxml.lib') 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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\LAME release\tinyxml.lib') does not match the Librarian's OutputFile property value '.\Debug\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Debug\tinyxml.lib') in project configuration 'LAME 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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\LAME release\tinyxml.lib') does not match the Linker's OutputFile property value 'LAME release\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release\tinyxml.lib') in project configuration 'LAME 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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\.\Release\tinyxml.lib') does not match the Librarian's OutputFile property value '.\Release\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\tinyxml.lib') 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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\.\Release\tinyxml.lib') does not match the Linker's OutputFile property value '.\Release\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\tinyxml.lib') 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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\LAME release Nasm\tinyxml.lib') does not match the Librarian's OutputFile property value '.\Release\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\Release\tinyxml.lib') in project configuration 'LAME release Nasm|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). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\LAME release Nasm\tinyxml.lib') does not match the Linker's OutputFile property value 'LAME release Nasm\tinyxml.lib' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release Nasm\tinyxml.lib') in project configuration 'LAME release Nasm|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
|
| ACM\tinyxml\tinyxml_vc7.vcproj:
Converting project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\tinyxml_vc7.vcproj'. |
| ACM\tinyxml\tinyxml_vc7.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'. |
| ACM\tinyxml\tinyxml_vc7.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. |
| ACM\tinyxml\tinyxml_vc7.vcproj:
The single-threaded run-time library switches (/MLd, /ML) have been removed from the C++ compiler. The project has been automatically converted to use the corresponding multi-threaded run-time library switches (/MTd, /MT). |
| ACM\tinyxml\tinyxml_vc7.vcproj:
Done converting to new project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\ACM\tinyxml\tinyxml_vc7.vcxproj'. |
|
Hide 5 additional messages
|
| frontend\mp3x_vc7.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. |
| frontend\mp3x_vc7.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). |
| frontend\mp3x_vc7.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. |
| frontend\mp3x_vc7.vcproj:
VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings. |
| frontend\mp3x_vc7.vcproj:
All user macros reported below for configuration 'LAME debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\mp3x_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\mp3x_vc7.vcproj:
All user macros reported below for configuration 'dll release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\mp3x_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\mp3x_vc7.vcproj:
All user macros reported below for configuration 'dll release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\mp3x_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\mp3x_vc7.vcproj:
All user macros reported below for configuration 'Release GTK|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\mp3x_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\mp3x_vc7.vcproj:
All user macros reported below for configuration 'dll debug|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\mp3x_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\mp3x_vc7.vcproj:
All user macros reported below for configuration 'Debug GTK|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\mp3x_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\mp3x_vc7.vcproj:
All user macros reported below for configuration 'LAME release|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\mp3x_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\mp3x_vc7.vcproj:
All user macros reported below for configuration 'LAME release Nasm|Win32' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros. |
| frontend\mp3x_vc7.vcproj:
MSB4211: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (128,5); The property "WindowsTargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.WindowsSDK.props (29,5)". |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\LAME debug\MP3x.exe') does not match the Librarian's OutputFile property value 'LAME debug\MP3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME debug\MP3x.exe') in project configuration 'LAME 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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\LAME debug\MP3x.exe') does not match the Linker's OutputFile property value '../output/mp3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/mp3x.exe') in project configuration 'LAME 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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\dll release\MP3x.exe') does not match the Librarian's OutputFile property value 'dll release\MP3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release\MP3x.exe') in project configuration 'dll 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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\dll release\MP3x.exe') does not match the Linker's OutputFile property value '../output/mp3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/mp3x.exe') in project configuration 'dll 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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\dll release Nasm\MP3x.exe') does not match the Librarian's OutputFile property value 'dll release Nasm\MP3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll release Nasm\MP3x.exe') in project configuration 'dll release Nasm|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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\dll release Nasm\MP3x.exe') does not match the Linker's OutputFile property value '../output/mp3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/mp3x.exe') in project configuration 'dll release Nasm|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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\.\MP3x___Win32_Release_GTK\MP3x.exe') does not match the Librarian's OutputFile property value '.\MP3x___Win32_Release_GTK\MP3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\MP3x___Win32_Release_GTK\MP3x.exe') in project configuration 'Release GTK|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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\.\MP3x___Win32_Release_GTK\MP3x.exe') does not match the Linker's OutputFile property value '../output/mp3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/mp3x.exe') in project configuration 'Release GTK|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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\dll debug\MP3x.exe') does not match the Librarian's OutputFile property value 'dll debug\MP3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\dll debug\MP3x.exe') in project configuration 'dll 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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\dll debug\MP3x.exe') does not match the Linker's OutputFile property value '../output/mp3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/mp3x.exe') in project configuration 'dll 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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\.\MP3x___Win32_Debug_GTK\MP3x.exe') does not match the Librarian's OutputFile property value '.\MP3x___Win32_Debug_GTK\MP3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\MP3x___Win32_Debug_GTK\MP3x.exe') in project configuration 'Debug GTK|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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\.\MP3x___Win32_Debug_GTK\MP3x.exe') does not match the Linker's OutputFile property value '../output/mp3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/mp3x.exe') in project configuration 'Debug GTK|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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\LAME release\MP3x.exe') does not match the Librarian's OutputFile property value 'LAME release\MP3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release\MP3x.exe') in project configuration 'LAME 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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\LAME release\MP3x.exe') does not match the Linker's OutputFile property value '../output/mp3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/mp3x.exe') in project configuration 'LAME 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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\LAME release Nasm\MP3x.exe') does not match the Librarian's OutputFile property value 'LAME release Nasm\MP3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\LAME release Nasm\MP3x.exe') in project configuration 'LAME release Nasm|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). |
| frontend\mp3x_vc7.vcproj:
MSB8012: $(TargetPath) ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\LAME release Nasm\MP3x.exe') does not match the Linker's OutputFile property value '../output/mp3x.exe' ('C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\../output/mp3x.exe') in project configuration 'LAME release Nasm|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 6 additional messages
|
| frontend\mp3x_vc7.vcproj:
Converting project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\mp3x_vc7.vcproj'. |
| frontend\mp3x_vc7.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'. |
| frontend\mp3x_vc7.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. |
| frontend\mp3x_vc7.vcproj:
The single-threaded run-time library switches (/MLd, /ML) have been removed from the C++ compiler. The project has been automatically converted to use the corresponding multi-threaded run-time library switches (/MTd, /MT). |
| frontend\mp3x_vc7.vcproj:
Web deployment to the local IIS server is no longer supported. The Web Deployment build tool has been removed from your project settings. |
| frontend\mp3x_vc7.vcproj:
Done converting to new project file 'C:\Users\zahradt\Documents\MediaManager-17.0.1\Support\lame\lamesrc\frontend\mp3x_vc7.vcxproj'. |
|
Hide 6 additional messages
|