Submit My Question - Recent Questions - Recent Answer
Msdn Tech >> Visual Studio >> Visual Studio MSBuild

Beta2 microsoft.common.targets errors

There are 57 warnings when I created new project after failing to convert from beta1, some of the warnings are listed below. Anybody knows why are these warnings?

<ResolveAssemblyReferencesDependsOn>


Warning 1 The element 'PropertyGroup' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003' has invalid child element 'CustomBeforeMicrosoftCommonTargets' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003'. Expected 'Property' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003'. R:\WINNT\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets 18 10 Miscellaneous Files
Warning 9 The element 'ItemGroup' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003' has invalid child element 'AppConfigFileDestination' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003'. Expected 'Item' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003'. R:\WINNT\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets 170 10 Miscellaneous Files

<GetFrameworkSDKPath>

<Microsoft.VisualStudio.EnterpriseTools.MappingTool.CompileTime.ObjectRelationalValidator

Warning 32 The element 'Target' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003' has invalid child element 'GetFrameworkSDKPath' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003'. Expected 'Task, OnError' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003'. R:\WINNT\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets 718 10 Miscellaneous Files

<RunDependsOn></RunDependsOn>

Warning 57 The element 'PropertyGroup' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003' has invalid child element 'RunDependsOn' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003'. Expected 'Property' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003'. R:\WINNT\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets 3774 10 Miscellaneous Files
[2580 byte] By [gulatis] at [2008-2-5]
«« declared
»» Custom formatter
# 1
These are errors from the schema validation of the file Microsoft.Common.targets which is part of Visual Studio. This file is not expected to validate against the schema, so these errors should be ignored. It looks like you have this file open in Visual Studio - if you close it, the errors should vanish.

Dan

DanMoseley at 2007-9-8 > top of Msdn Tech,Visual Studio,Visual Studio MSBuild...
# 2
well, I did that. I am not sure why is this file keep showing me these error.
Any ideas how to fix rafing errors?
gulatis at 2007-9-8 > top of Msdn Tech,Visual Studio,Visual Studio MSBuild...
# 3

So you don't have microsoft.common.targets or any similar files open in visual studio and you still see these errors? That is very odd.

If so when exactly are you getting these errors? When you create a brand new project or when you convert a project?

What exactly do you mean by failing to convert from beta 1? Did the upgrade of VS fail or the project conversion fail?

Dan (msbuild@microsoft.com)

DanMoseley at 2007-9-8 > top of Msdn Tech,Visual Studio,Visual Studio MSBuild...
# 4
Thanks for your help but I am not sure where that microsoft.common.targets errors came from. I think while converting (automatic) from beta 1. there are few other who also experience same thing at my work.

But after closing that file, the warning go away. so those are gone now. There are some rafing errors left. I read somewhere that comment all lines having rafting in them. Is that correct?

gulatis at 2007-9-8 > top of Msdn Tech,Visual Studio,Visual Studio MSBuild...
# 5
What do you mean by rafting? I'm confused.

Dan

DanMoseley at 2007-9-8 > top of Msdn Tech,Visual Studio,Visual Studio MSBuild...
# 6
When I opened my beta1 code in beta 2, which has controls and form. Now I am tring to compile and getting rafing errors.
gulatis at 2007-9-8 > top of Msdn Tech,Visual Studio,Visual Studio MSBuild...
# 7
I'm just not understanding the word "rafing". Could you explain in different words?
DanMoseley at 2007-9-8 > top of Msdn Tech,Visual Studio,Visual Studio MSBuild...
# 8
Here you can find raftingcontainer and other similar classes:
http://msdn2.microsoft.com/library/tyycx6ws(en-us,vs.80).aspx
gulatis at 2007-9-8 > top of Msdn Tech,Visual Studio,Visual Studio MSBuild...
# 9
Ah - rafting in Windows Forms. Can you ask your question in a Windows Forms forum? I'm not an expert on that.

Here are their forums:
http://forums.microsoft.com/msdn/default.aspx?ForumGroupID=2

DanMoseley at 2007-9-8 > top of Msdn Tech,Visual Studio,Visual Studio MSBuild...
# 10
hi, I am having the same problem as well with a 2003 project i converted over to vb 2005 beta 2, I get about 65 errors even when i close the file it doesn't go away so i can't build my project, also one of the error is a the microsoft.data.odbc reference in my project folder which has a yellow error triangle on it. also is there any way i can get my hands on a developer hand book (reference) with all the new changes in 2005 beta 2 from previous versions?

<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">

<!-- These tasks are specific to the build process defined in this file, and are not considered general-purpose build tasks. -->

<UsingTask TaskName="Microsoft.Build.Tasks.AssignTargetPath" AssemblyName="Microsoft.Build.Tasks, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

<UsingTask TaskName="Microsoft.Build.Tasks.FormatUrl" AssemblyName="Microsoft.Build.Tasks, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

<UsingTask TaskName="Microsoft.Build.Tasks.FormatVersion" AssemblyName="Microsoft.Build.Tasks, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

<UsingTask TaskName="Microsoft.Build.Tasks.FxCop" AssemblyName="Microsoft.Build.Tasks, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

<UsingTask TaskName="Microsoft.Build.Tasks.GenerateTrustInfo" AssemblyName="Microsoft.Build.Tasks, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

<UsingTask TaskName="Microsoft.Build.Tasks.ResolveManifestFiles" AssemblyName="Microsoft.Build.Tasks, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

<UsingTask TaskName="Microsoft.Build.Tasks.ResolveVCProjectOutput" AssemblyName="Microsoft.Build.Tasks, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

<UsingTask TaskName="Microsoft.Build.Tasks.ResolveNonMSBuildProjectOutput" AssemblyName="Microsoft.Build.Tasks, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

<UsingTask TaskName="Microsoft.Build.Tasks.UpdateManifest" AssemblyName="Microsoft.Build.Tasks, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

<UsingTask TaskName="Microsoft.VisualStudio.EnterpriseTools.MappingTool.CompileTime.ObjectRelationalValidator" AssemblyName="Microsoft.VisualStudio.EnterpriseTools.MappingTool"/>

<Import Project="$(MSBuildProjectFullPath).user" Condition="Exists('$(MSBuildProjectFullPath).user')"/>

<PropertyGroup>

<CustomBeforeMicrosoftCommonTargets Condition="'$(CustomBeforeMicrosoftCommonTargets)'==''">$(MSBuildExtensionsPath)\v2.0\Custom.Before.Microsoft.Common.targets</CustomBeforeMicrosoftCommonTargets>

<CustomAfterMicrosoftCommonTargets Condition="'$(CustomAfterMicrosoftCommonTargets)'==''">$(MSBuildExtensionsPath)\v2.0\Custom.After.Microsoft.Common.targets</CustomAfterMicrosoftCommonTargets>

<ReportingServicesTargets Condition="'$(ReportingServicesTargets)'==''">$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v8.0\ReportingServices\Microsoft.ReportingServices.targets</ReportingServicesTargets>

</PropertyGroup>

<Import Project="$(CustomBeforeMicrosoftCommonTargets)" Condition="Exists('$(CustomBeforeMicrosoftCommonTargets)')"/>

<Error Condition=" '$(InvalidConfigurationError)' == 'true' " Text="The OutputPath property is not set for this project. Please check to make sure that you have specified a valid Configuration/Platform combination. Configuration='$(Configuration)' Platform='$(Platform)'"/>

<Warning Condition=" '$(InvalidConfigurationWarning)' == 'true' " Text="The OutputPath property is not set for this project. Please check to make sure that you have specified a valid Configuration/Platform combination. Configuration='$(Configuration)' Platform='$(Platform)'"/>

<Message Text="Configuration=$(Configuration)" Importance="Low" />

<Message Text="Platform=$(Platform)" Importance="Low" />

<!--

Several properties must be set in the main project file, before using this .TARGETS file.

However, if the properties are not set, we pick some defaults.

-->

<PropertyGroup>

<AssemblyName Condition=" '$(AssemblyName)'=='' ">$(MSBuildProjectName)</AssemblyName>

<!--

Be careful not to give OutputPath a default value in the case of an invalid Configuration.

We use OutputPath specifically to check for invalid configurations.

-->

<OutputPath Condition=" '$(Configuration)$(OutputPath)' == '' ">bin\Debug\</OutputPath>

<Configuration Condition=" '$(Configuration)'=='' ">Debug</Configuration>

<Platform Condition=" '$(Platform)'=='' ">AnyCPU</Platform>

<OutputType Condition=" '$(TargetType)' != ''">$(TargetType)</OutputType>

<OutputType Condition=" '$(TargetType)' == 'Container' or '$(TargetType)' == 'DocumentContainer' ">library</OutputType>

<OutputType Condition=" '$(OutputType)' == '' ">exe</OutputType>

<DebugSymbols Condition=" '$(Configuration)_$(DebugSymbols)_$(DebugType)'=='Debug__'">true</DebugSymbols>

<!-- Whether or not a .pdb file is produced. -->

<DebugSymbols>false</DebugSymbols>

<DebugSymbols Condition="'$(DebugSymbols)'=='true'">true</DebugSymbols>

<DebugSymbols Condition="'$(DebugType)'=='none'">false</DebugSymbols>

<DebugSymbols Condition="'$(DebugType)'=='pdbonly'">true</DebugSymbols>

<DebugSymbols Condition="'$(DebugType)'=='full'">true</DebugSymbols>

<!-- Whether or not a .xml file is produced. -->

<DocumentationFile>true</DocumentationFile>

lew26 at 2007-9-8 > top of Msdn Tech,Visual Studio,Visual Studio MSBuild...
Visual Studio
Visual Studio MSBuild

Visual Studio Hot Topic

Visual Studio New Topic

Visual Studio

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech

Site Classified