Migration Report RiemannMapper
Overview
Project
Path
Errors
Warnings
Messages
RiemannMapper
RiemannMapperRiemannMapper.vcproj
0
10
2
Solution
RiemannMapper.sln
0
1
3
Solution and projects
RiemannMapper
Message
RiemannMapperRiemannMapper.vcproj: VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings.
RiemannMapperRiemannMapper.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.
RiemannMapperRiemannMapper.vcproj: MSB4211: C:Program Files (x86)MSBuild12.0binMicrosoft.Common.CurrentVersion.targets (86,5); The property TargetPlatformIdentifier is being set to a value for the first time, but it was already consumed at C:Program Files (x86)MSBuildMicrosoft.Cppv4.0V120Microsoft.Cpp.Common.props (103,5).
RiemannMapperRiemannMapper.vcproj: MSB4211: C:Program Files (x86)MSBuild12.0binMicrosoft.Common.CurrentVersion.targets (87,5); The property TargetPlatformVersion is being set to a value for the first time, but it was already consumed at C:Program Files (x86)MSBuildMicrosoft.Cppv4.0V120Microsoft.Cpp.Common.props (103,5).
RiemannMapperRiemannMapper.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.
RiemannMapperRiemannMapper.vcproj: MSB4211: C:Program Files (x86)MSBuild12.0binMicrosoft.Common.CurrentVersion.targets (86,5); The property TargetPlatformIdentifier is being set to a value for the first time, but it was already consumed at C:Program Files (x86)MSBuildMicrosoft.Cppv4.0V120Microsoft.Cpp.Common.props (103,5).
RiemannMapperRiemannMapper.vcproj: MSB4211: C:Program Files (x86)MSBuild12.0binMicrosoft.Common.CurrentVersion.targets (87,5); The property TargetPlatformVersion is being set to a value for the first time, but it was already consumed at C:Program Files (x86)MSBuildMicrosoft.Cppv4.0V120Microsoft.Cpp.Common.props (103,5).
RiemannMapperRiemannMapper.vcproj: MSB8012: $(TargetPath) (J:DavidGu20152015_TeachingCSE325_Computer_SculptureGaussBonnetGaussCurvature_SampleGaussCurvatureRiemannMapper….binRiemannMapper.exe) does not match the Librarians OutputFile property value ….binRiemannMapper.exe (J:DavidGu20152015_TeachingCSE325_Computer_SculptureGaussBonnetbinRiemannMapper.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).
RiemannMapperRiemannMapper.vcproj: MSB8012: $(TargetName) (RiemannMapper) does not match the Linkers OutputFile property value ….binGaussCurvature.exe (GaussCurvature) 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).
RiemannMapperRiemannMapper.vcproj: MSB8012: $(TargetPath) (J:DavidGu20152015_TeachingCSE325_Computer_SculptureGaussBonnetGaussCurvature_SampleGaussCurvatureRiemannMapper….binRiemannMapper.exe) does not match the Linkers OutputFile property value ….binGaussCurvature.exe (J:DavidGu20152015_TeachingCSE325_Computer_SculptureGaussBonnetbinGaussCurvature.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 2 additional messages
Solution
Message
RiemannMapper.sln: Visual Studio needs to make non-functional changes to this project in order to enable the project to open in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without impacting project behavior.
Show 3 additional messages
Reviews
There are no reviews yet.