Update Project Vs2005 For 2015

[gta2]

alguem pode me ajudar como posso mover meu projeto para compilar

vs 2015

 

quando eu abrir o meu erro de projeto ao iniciar no vs 2015

 

como eu faço para atualizar sem erro?

 

Relatório de Migração - L2Extend - VS2005

 

Migration Report - L2Extend - VS2005

Overview

Project Path Errors Warnings Messages

L2Extend - VS2005 L2Extend\L2Extend - VS2005.vcproj 0 15 5

NPCExt NPCExt\NPCExt.vcproj 0 14 5

CachedExt CachedExt\CachedExt.vcproj 0 10 5

Solution L2Extend - VS2005.sln 0 1 2

L2Extend L2Extend\L2Extend - VS2005.vcproj 0 0 0

Solution and projects

L2Extend - VS2005

Message

L2Extend\L2Extend - VS2005.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.

L2Extend\L2Extend - VS2005.vcproj: VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings.

L2Extend\L2Extend - VS2005.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.

L2Extend\L2Extend - VS2005.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.

L2Extend\L2Extend - VS2005.vcproj: Attribute 'OptimizeForWindows98' of 'VCLinkerTool' is not supported in this version and has been removed during conversion.

L2Extend\L2Extend - VS2005.vcproj: The following file(s) were found multiple times in the project/filter and duplicates were ignored: '.\CStaticObject.cpp, .\CStaticObject.h'.

L2Extend\L2Extend - VS2005.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.

L2Extend\L2Extend - VS2005.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)".

L2Extend\L2Extend - VS2005.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.

L2Extend\L2Extend - VS2005.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)".

L2Extend\L2Extend - VS2005.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.

L2Extend\L2Extend - VS2005.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)".

L2Extend\L2Extend - VS2005.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.

L2Extend\L2Extend - VS2005.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)".

L2Extend\L2Extend - VS2005.vcproj: Tool name 'MASM x64' is not supported in this version and it was renamed as 'MASM_x64'.

Show 5 additional messages

NPCExt

Message

NPCExt\NPCExt.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.

Rules\masm64.rules: Semicolon is the only supported separator in MSBuild. Usage of any other separator for Custom Build Rule string properties is invalid after conversion.

NPCExt\NPCExt.vcproj: VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings.

NPCExt\NPCExt.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.

NPCExt\NPCExt.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.

NPCExt\NPCExt.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.

NPCExt\NPCExt.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)".

NPCExt\NPCExt.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.

NPCExt\NPCExt.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)".

NPCExt\NPCExt.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.

NPCExt\NPCExt.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)".

NPCExt\NPCExt.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.

NPCExt\NPCExt.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)".

NPCExt\NPCExt.vcproj: Tool name 'MASM x64' is not supported in this version and it was renamed as 'MASM_x64'.

Show 5 additional messages

CachedExt

Message

CachedExt\CachedExt.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.

Rules\masm86.rules: Semicolon is the only supported separator in MSBuild. Usage of any other separator for Custom Build Rule string properties is invalid after conversion.

CachedExt\CachedExt.vcproj: VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings.

CachedExt\CachedExt.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.

CachedExt\CachedExt.vcproj: Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.

CachedExt\CachedExt.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.

CachedExt\CachedExt.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)".

CachedExt\CachedExt.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.

CachedExt\CachedExt.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)".

CachedExt\CachedExt.vcproj: Tool name 'MASM x86' is not supported in this version and it was renamed as 'MASM_x86'.

Show 5 additional messages

Solution

Message

L2Extend - VS2005.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

L2Extend

 

Edited October 7, 2015 by gta2

[xeL]

1st: Please post on english or next time i lock topic.

 

2nd: use vs 2005 i don't realy recommand to update to new vs

Edited October 7, 2015 by xeL