After linking Class Library: Microsoft.Common.targets

Hot Topic

launch 2 reports in same crystalviewer?
VSS 6c database lost all checkins and checkouts
browser app questions
Rotate Window
Why the name "DLinq"?
How to synchronize 2 VSS 2005 Servers
Before all builds and after all builds..
Hello world ... version control ?
Seroius error while having combobox into each column's cells
Dynamic Code Generation

Visual Studio

Crystal Report Error
Security diff between ReportViewer & ReportManager
Microsoft.VisualStudio.CommonIDE.TemplateWizard - IWizard Interface
Implementation for IVsMultiViewDocumentView interface for "Design" and "HTML" view
Anonymous Structs
obtain client address inside service
What abt Dynamic Where condition??
Unspecified error when doing Get Latest Version
Displaying columns as rows and rows as columns
Display string function not working

After linking Class Library: Microsoft.Common.targets

Hello,

I created a solution containing two projects. When I create a reference from the GUI to the Business Layer, the compilation fails:

Error 60 Specified condition "'D:\Documents\Projects\Brammekes Virtual Scrambler\BL\bin\Debug\Native.BL.manifest'" evaluates to "D:\Documents\Projects\Brammekes Virtual Scrambler\BL\bin\Debug\Native.BL.manifest" instead of a boolean. C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets 999 9 

I have absolutely no idea what happened instead of what was supposed to happen.

Can I solve this

Thank you,
Bram

Answer this question

After linking Class Library: Microsoft.Common.targets

  • k.Rahul

    Sorry for my late reply. I've been a bit too busy.

    I was able to solve the problem. There was a quote (') in my pathname which screwed up the compilation. After removing it, the compilation went just fine and the project ran as it has never ran before.

    Strangely enough, the problem occured again last week. This time, I'm working on a SmartPhone solution. 2 projects: a GUI and my logic. Whenever I link my logic in my GUI, compilation fails:

    Error 1 Invalid value for 'OSVersion'. C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets
    Line 2006
    Column 9

    I double click the error and it takes me to this line in Microsoft.Common.targets:

    <GenerateApplicationManifest AssemblyName="$(ApplicationManifestIdentity)" AssemblyVersion="$(ManifestVersion)" ConfigFile="@(AppConfigWithTargetPath)" ClrVersion="$(ClrVersion)" Dependencies="@(ManifestDependencies)" Description="$(Description)" EntryPoint="@(ManifestEntryPoint)" Files="@(ManifestFiles)" IconFile="@(ManifestIconFile)" InputManifest="@(BaseManifestWithTargetPath)" IsolatedComReferences="@(ResolvedIsolatedComModules)" ManifestType="$(ManifestType)" MaxTargetPath="$(MaxTargetPath)" OutputManifest="@(ApplicationManifest)" OSVersion="$(OSVersion)" Platform="$(PlatformTarget)" TargetCulture="$(TargetCulture)" TrustInfoFile="@(IntermediateTrustInfoFile)">

    When I remove the reference, it works fine (except for the referenced objects of course).

    Does this help Tongue Tied

    Bram

  • OdieTurbo

    For the time being, I've put all my logic in a folder in the main project and removed the reference. It works, but I lost my 2-tier approach. I'm not planning on a WinForms GUI right now, so I'll survive. It just doesn't look pretty. Smile

  • paulta

    Are you able to compile when you remove the reference   I am not exactly sure what's happening just yet.  If you haven't already tried this, try if removing that reference allows you to get back into the last known good state. 

    Also, what kind of reference is it   Are you doing a file reference or a project to project reference

    Any additional information would be useful - more detailed build log, the type of projects that you are using in your solution, etc....

    Faisal Mohamood
    MSBuild Team
  • After linking Class Library: Microsoft.Common.targets
Answer this question