# Migration Report - windirstat.vs8

## Overview

| Project | Path | Errors | Warnings | Messages
--- | --- | --- | --- | --- | ---
| minilua.vs8 | 3rdparty\lua\src\minilua.vs8.vcproj | 0 | 7 | 3
| windirstat.vs8 | windirstat\windirstat.vs8.vcproj | 0 | 30 | 3
| luaconf.vs8 | sandbox\luaconf\luaconf.vs8.vcproj | 0 | 16 | 3
| buildvm.vs8 | 3rdparty\lua\src\buildvm.vs8.vcproj | 0 | 14 | 3
| luajit2.vs8 | 3rdparty\lua\src\luajit2.vs8.vcproj | 0 | 14 | 3
| Solution | windirstat.vs8.sln | 0 | 1 | 2
| buildvm | 3rdparty\lua\src\buildvm.vs8.vcproj | 0 | 0 | 0
| luaconf | sandbox\luaconf\luaconf.vs8.vcproj | 0 | 0 | 0
| luajit2 | 3rdparty\lua\src\luajit2.vs8.vcproj | 0 | 0 | 0
| minilua | 3rdparty\lua\src\minilua.vs8.vcproj | 0 | 0 | 0
| windirstat | windirstat\windirstat.vs8.vcproj | 0 | 0 | 0

## Solution and projects

### minilua.vs8

| Message
--- | ---
| 3rdparty\lua\src\minilua.vs8.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.
| 3rdparty\lua\src\minilua.vs8.vcproj: VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings.
| 3rdparty\lua\src\minilua.vs8.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
| 3rdparty\lua\src\minilua.vs8.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.
| 3rdparty\lua\src\minilua.vs8.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)".
| 3rdparty\lua\src\minilua.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\.\minilua.exe') does not match the Librarian's OutputFile property value '.\minilua.exe' ('D:\INFOMOV P3\windirstat\ready\minilua.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).
| 3rdparty\lua\src\minilua.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\.\minilua.exe') does not match the Linker's OutputFile property value '.\minilua.exe' ('D:\INFOMOV P3\windirstat\ready\minilua.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).
| Show 3 additional messages
| 3rdparty\lua\src\minilua.vs8.vcproj: Converting project file 'D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\minilua.vs8.vcproj'.
| 3rdparty\lua\src\minilua.vs8.vcproj: Web deployment to the local IIS server is no longer supported. The Web Deployment build tool has been removed from your project settings.
| 3rdparty\lua\src\minilua.vs8.vcproj: Done converting to new project file 'D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\minilua.vs8.vcxproj'.
| Hide 3 additional messages

### windirstat.vs8

| Message
--- | ---
| windirstat\windirstat.vs8.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.
| windirstat\windirstat.vs8.vcproj: VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings.
| windirstat\windirstat.vs8.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
| windirstat\windirstat.vs8.vcproj: VCConvertEngine could not convert attribute ProgramDataBaseFileName = $(OutDir)wds32D.pdb under Tool VCLinkerTool.
| windirstat\windirstat.vs8.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
| windirstat\windirstat.vs8.vcproj: VCConvertEngine could not convert attribute ProgramDataBaseFileName = $(OutDir)wds64D.pdb under Tool VCLinkerTool.
| windirstat\windirstat.vs8.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
| windirstat\windirstat.vs8.vcproj: VCConvertEngine could not convert attribute ProgramDataBaseFileName = $(OutDir)wds32.pdb under Tool VCLinkerTool.
| windirstat\windirstat.vs8.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
| windirstat\windirstat.vs8.vcproj: VCConvertEngine could not convert attribute ProgramDataBaseFileName = $(OutDir)wds64.pdb under Tool VCLinkerTool.
| windirstat\windirstat.vs8.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.
| windirstat\windirstat.vs8.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)".
| windirstat\windirstat.vs8.vcproj: All user macros reported below for configuration 'Debug|x64' 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.
| windirstat\windirstat.vs8.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)".
| windirstat\windirstat.vs8.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.
| windirstat\windirstat.vs8.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)".
| windirstat\windirstat.vs8.vcproj: All user macros reported below for configuration 'Release|x64' 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.
| windirstat\windirstat.vs8.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)".
| windirstat\windirstat.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\windirstat\..\build\windirstat.exe') does not match the Librarian's OutputFile property value '..\build\windirstat.exe' ('D:\INFOMOV P3\windirstat\build\windirstat.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).
| windirstat\windirstat.vs8.vcproj: MSB8012: $(TargetName) ('windirstat') does not match the Linker's OutputFile property value '..\build\wds32D.exe' ('wds32D') 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).
| windirstat\windirstat.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\windirstat\..\build\windirstat.exe') does not match the Linker's OutputFile property value '..\build\wds32D.exe' ('D:\INFOMOV P3\windirstat\build\wds32D.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).
| windirstat\windirstat.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\windirstat\..\build\windirstat.exe') does not match the Librarian's OutputFile property value '..\build\windirstat.exe' ('D:\INFOMOV P3\windirstat\build\windirstat.exe') in project configuration 'Debug|x64'. 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).
| windirstat\windirstat.vs8.vcproj: MSB8012: $(TargetName) ('windirstat') does not match the Linker's OutputFile property value '..\build\wds64D.exe' ('wds64D') in project configuration 'Debug|x64'. 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).
| windirstat\windirstat.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\windirstat\..\build\windirstat.exe') does not match the Linker's OutputFile property value '..\build\wds64D.exe' ('D:\INFOMOV P3\windirstat\build\wds64D.exe') in project configuration 'Debug|x64'. 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).
| windirstat\windirstat.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\windirstat\..\build\windirstat.exe') does not match the Librarian's OutputFile property value '..\build\windirstat.exe' ('D:\INFOMOV P3\windirstat\build\windirstat.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).
| windirstat\windirstat.vs8.vcproj: MSB8012: $(TargetName) ('windirstat') does not match the Linker's OutputFile property value '..\build\wds32.exe' ('wds32') 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).
| windirstat\windirstat.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\windirstat\..\build\windirstat.exe') does not match the Linker's OutputFile property value '..\build\wds32.exe' ('D:\INFOMOV P3\windirstat\build\wds32.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).
| windirstat\windirstat.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\windirstat\..\build\windirstat.exe') does not match the Librarian's OutputFile property value '..\build\windirstat.exe' ('D:\INFOMOV P3\windirstat\build\windirstat.exe') in project configuration 'Release|x64'. 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).
| windirstat\windirstat.vs8.vcproj: MSB8012: $(TargetName) ('windirstat') does not match the Linker's OutputFile property value '..\build\wds64.exe' ('wds64') in project configuration 'Release|x64'. 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).
| windirstat\windirstat.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\windirstat\..\build\windirstat.exe') does not match the Linker's OutputFile property value '..\build\wds64.exe' ('D:\INFOMOV P3\windirstat\build\wds64.exe') in project configuration 'Release|x64'. 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 3 additional messages
| windirstat\windirstat.vs8.vcproj: Converting project file 'D:\INFOMOV P3\windirstat\ready\windirstat\windirstat.vs8.vcproj'.
| windirstat\windirstat.vs8.vcproj: Web deployment to the local IIS server is no longer supported. The Web Deployment build tool has been removed from your project settings.
| windirstat\windirstat.vs8.vcproj: Done converting to new project file 'D:\INFOMOV P3\windirstat\ready\windirstat\windirstat.vs8.vcxproj'.
| Hide 3 additional messages

### luaconf.vs8

| Message
--- | ---
| sandbox\luaconf\luaconf.vs8.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.
| sandbox\luaconf\luaconf.vs8.vcproj: VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings.
| sandbox\luaconf\luaconf.vs8.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
| sandbox\luaconf\luaconf.vs8.vcproj: VCConvertEngine could not convert attribute ProgramDataBaseFileName = $(OutDir)luaconf32.pdb under Tool VCLinkerTool.
| sandbox\luaconf\luaconf.vs8.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
| sandbox\luaconf\luaconf.vs8.vcproj: VCConvertEngine could not convert attribute ProgramDataBaseFileName = $(OutDir)luaconf64.pdb under Tool VCLinkerTool.
| sandbox\luaconf\luaconf.vs8.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.
| sandbox\luaconf\luaconf.vs8.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)".
| sandbox\luaconf\luaconf.vs8.vcproj: All user macros reported below for configuration 'Release|x64' 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.
| sandbox\luaconf\luaconf.vs8.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)".
| sandbox\luaconf\luaconf.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\sandbox\luaconf\..\..\build\luaconf.exe') does not match the Librarian's OutputFile property value '..\..\build\luaconf.exe' ('D:\INFOMOV P3\build\luaconf.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).
| sandbox\luaconf\luaconf.vs8.vcproj: MSB8012: $(TargetName) ('luaconf') does not match the Linker's OutputFile property value '..\..\build\luaconf32.exe' ('luaconf32') 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).
| sandbox\luaconf\luaconf.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\sandbox\luaconf\..\..\build\luaconf.exe') does not match the Linker's OutputFile property value '..\..\build\luaconf32.exe' ('D:\INFOMOV P3\build\luaconf32.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).
| sandbox\luaconf\luaconf.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\sandbox\luaconf\..\..\build\luaconf.exe') does not match the Librarian's OutputFile property value '..\..\build\luaconf.exe' ('D:\INFOMOV P3\build\luaconf.exe') in project configuration 'Release|x64'. 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).
| sandbox\luaconf\luaconf.vs8.vcproj: MSB8012: $(TargetName) ('luaconf') does not match the Linker's OutputFile property value '..\..\build\luaconf64.exe' ('luaconf64') in project configuration 'Release|x64'. 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).
| sandbox\luaconf\luaconf.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\sandbox\luaconf\..\..\build\luaconf.exe') does not match the Linker's OutputFile property value '..\..\build\luaconf64.exe' ('D:\INFOMOV P3\build\luaconf64.exe') in project configuration 'Release|x64'. 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 3 additional messages
| sandbox\luaconf\luaconf.vs8.vcproj: Converting project file 'D:\INFOMOV P3\windirstat\ready\sandbox\luaconf\luaconf.vs8.vcproj'.
| sandbox\luaconf\luaconf.vs8.vcproj: Web deployment to the local IIS server is no longer supported. The Web Deployment build tool has been removed from your project settings.
| sandbox\luaconf\luaconf.vs8.vcproj: Done converting to new project file 'D:\INFOMOV P3\windirstat\ready\sandbox\luaconf\luaconf.vs8.vcxproj'.
| Hide 3 additional messages

### buildvm.vs8

| Message
--- | ---
| 3rdparty\lua\src\buildvm.vs8.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.
| 3rdparty\lua\src\buildvm.vs8.vcproj: VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings.
| 3rdparty\lua\src\buildvm.vs8.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
| 3rdparty\lua\src\buildvm.vs8.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
| 3rdparty\lua\src\buildvm.vs8.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.
| 3rdparty\lua\src\buildvm.vs8.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)".
| 3rdparty\lua\src\buildvm.vs8.vcproj: All user macros reported below for configuration 'Release|x64' 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.
| 3rdparty\lua\src\buildvm.vs8.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)".
| 3rdparty\lua\src\buildvm.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\.\buildvm.exe') does not match the Librarian's OutputFile property value '.\buildvm.exe' ('D:\INFOMOV P3\windirstat\ready\buildvm.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).
| 3rdparty\lua\src\buildvm.vs8.vcproj: MSB8012: $(TargetName) ('buildvm') does not match the Linker's OutputFile property value '.\buildvm32.exe' ('buildvm32') 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).
| 3rdparty\lua\src\buildvm.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\.\buildvm.exe') does not match the Linker's OutputFile property value '.\buildvm32.exe' ('D:\INFOMOV P3\windirstat\ready\buildvm32.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).
| 3rdparty\lua\src\buildvm.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\.\buildvm.exe') does not match the Librarian's OutputFile property value '.\buildvm.exe' ('D:\INFOMOV P3\windirstat\ready\buildvm.exe') in project configuration 'Release|x64'. 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).
| 3rdparty\lua\src\buildvm.vs8.vcproj: MSB8012: $(TargetName) ('buildvm') does not match the Linker's OutputFile property value '.\buildvm64.exe' ('buildvm64') in project configuration 'Release|x64'. 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).
| 3rdparty\lua\src\buildvm.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\.\buildvm.exe') does not match the Linker's OutputFile property value '.\buildvm64.exe' ('D:\INFOMOV P3\windirstat\ready\buildvm64.exe') in project configuration 'Release|x64'. 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 3 additional messages
| 3rdparty\lua\src\buildvm.vs8.vcproj: Converting project file 'D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\buildvm.vs8.vcproj'.
| 3rdparty\lua\src\buildvm.vs8.vcproj: Web deployment to the local IIS server is no longer supported. The Web Deployment build tool has been removed from your project settings.
| 3rdparty\lua\src\buildvm.vs8.vcproj: Done converting to new project file 'D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\buildvm.vs8.vcxproj'.
| Hide 3 additional messages

### luajit2.vs8

| Message
--- | ---
| 3rdparty\lua\src\luajit2.vs8.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.
| 3rdparty\lua\src\luajit2.vs8.vcproj: VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings.
| 3rdparty\lua\src\luajit2.vs8.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
| 3rdparty\lua\src\luajit2.vs8.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
| 3rdparty\lua\src\luajit2.vs8.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.
| 3rdparty\lua\src\luajit2.vs8.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)".
| 3rdparty\lua\src\luajit2.vs8.vcproj: All user macros reported below for configuration 'Release|x64' 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.
| 3rdparty\lua\src\luajit2.vs8.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)".
| 3rdparty\lua\src\luajit2.vs8.vcproj: MSB8012: $(TargetName) ('luajit2') does not match the Librarian's OutputFile property value '..\..\..\..\..\build\luajit2_Win32.lib' ('luajit2_Win32') 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 %(Lib.OutputFile).
| 3rdparty\lua\src\luajit2.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\..\..\..\..\..\build\luajit2.lib') does not match the Librarian's OutputFile property value '..\..\..\..\..\build\luajit2_Win32.lib' ('D:\build\luajit2_Win32.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).
| 3rdparty\lua\src\luajit2.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\..\..\..\..\..\build\luajit2.lib') does not match the Linker's OutputFile property value '..\..\..\..\..\build\luajit2.lib' ('D:\build\luajit2.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).
| 3rdparty\lua\src\luajit2.vs8.vcproj: MSB8012: $(TargetName) ('luajit2') does not match the Librarian's OutputFile property value '..\..\..\..\..\build\luajit2_x64.lib' ('luajit2_x64') in project configuration 'Release|x64'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetName) property value matches the value specified in %(Lib.OutputFile).
| 3rdparty\lua\src\luajit2.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\..\..\..\..\..\build\luajit2.lib') does not match the Librarian's OutputFile property value '..\..\..\..\..\build\luajit2_x64.lib' ('D:\build\luajit2_x64.lib') in project configuration 'Release|x64'. 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).
| 3rdparty\lua\src\luajit2.vs8.vcproj: MSB8012: $(TargetPath) ('D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\..\..\..\..\..\build\luajit2.lib') does not match the Linker's OutputFile property value '..\..\..\..\..\build\luajit2.lib' ('D:\build\luajit2.lib') in project configuration 'Release|x64'. 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 3 additional messages
| 3rdparty\lua\src\luajit2.vs8.vcproj: Converting project file 'D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\luajit2.vs8.vcproj'.
| 3rdparty\lua\src\luajit2.vs8.vcproj: Web deployment to the local IIS server is no longer supported. The Web Deployment build tool has been removed from your project settings.
| 3rdparty\lua\src\luajit2.vs8.vcproj: Done converting to new project file 'D:\INFOMOV P3\windirstat\ready\3rdparty\lua\src\luajit2.vs8.vcxproj'.
| Hide 3 additional messages

### Solution

| Message
--- | ---
| windirstat.vs8.sln: Visual Studio needs to make non-functional changes to this project in order to enable the project to open in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without impacting project behavior.
| Show 2 additional messages
| windirstat.vs8.sln: File successfully backed up as D:\INFOMOV P3\windirstat\ready\Backup\windirstat.vs8.sln
| windirstat.vs8.sln: Solution migrated successfully
| Hide 2 additional messages

### buildvm

| Message
--- | ---
| buildvm logged no messages.

### luaconf

| Message
--- | ---
| luaconf logged no messages.

### luajit2

| Message
--- | ---
| luajit2 logged no messages.

### minilua

| Message
--- | ---
| minilua logged no messages.

### windirstat

| Message
--- | ---
| windirstat logged no messages.