Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 575831
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T13:58:56+00:00 2026-05-13T13:58:56+00:00

A .NET 3.5 solution ended up with this warning when compiling with msbuild. Sometimes

  • 0

A .NET 3.5 solution ended up with this warning when compiling with msbuild.

Sometimes NDepend might help out but in this case it didn’t give any further details. Like Bob I ended up having to resort to opening each assembly in ILDASM until I found the one that was referencing an older version of the dependant assembly.

I did try using MSBUILD from VS 2010 Beta 2 (as the Connect article indicated this was fixed in the next version of the CLR) but that didn’t provide any more detail either (maybe fixed post Beta 2)

Is there a better (more automated) approach?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-13T13:58:56+00:00Added an answer on May 13, 2026 at 1:58 pm

    Change the “MSBuild project build output verbosity” to “Detailed” or above. To do this, follow these steps:

    1. Bring up the Options dialog (Tools -> Options…).
    2. In the left-hand tree, select the Projects and Solutions node, and then select Build and Run.
      • Note: if this node doesn’t show up, make sure that the checkbox at the bottom of the dialog Show all settings is checked.
    3. In the tools/options page that appears, set the MSBuild project build output verbosity level to the appropriate setting depending on your version:

      • Diagnostics when on VS2012, VS2013 or VS2015 (the message in these versions says you should use “Detailed”, but this is plain wrong, you should use “Diagnostics”)
      • Detailed when you’re on VS2010
      • Normal will suffice in VS2008 or older.
    4. Build the project and look in the output window.

    Check out the MSBuild messages. The ResolveAssemblyReferences task, which is the task from which MSB3247 originates, should help you debug this particular issue.

    My specific case was an incorrect reference to SqlServerCe. See below. I had two projects referencing two different versions of SqlServerCe. I went to the project with the older version, removed the reference, then added the correct reference.

    Target ResolveAssemblyReferences:
        Consider app.config remapping of assembly "System.Data.SqlServerCe, ..." 
            from Version "3.5.1.0" [H:\...\Debug\System.Data.SqlServerCe.dll] 
            to Version "9.0.242.0" [C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PublicAssemblies\System.Data.SqlServerCe.dll]
            to solve conflict and get rid of warning.
        C:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets : 
            warning MSB3247: Found conflicts between different versions of the same dependent assembly.
    

    You do not have to open each assembly to determine the versions of referenced assemblies.

    • You can check the Properties of each Reference.
    • Open the project properties and check the versions of the References section.
    • Open the projects with a Text Editor.
    • Use .Net Reflector.
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 289k
  • Answers 289k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer Just change it to var appointmentNoShow = from a in… May 13, 2026 at 5:37 pm
  • Editorial Team
    Editorial Team added an answer Search (e.g. using /) for \%x1b. You can also type… May 13, 2026 at 5:37 pm
  • Editorial Team
    Editorial Team added an answer Instead of using the system's http_proxy, set the proxy directly… May 13, 2026 at 5:37 pm

Related Questions

I have a small (or perhaps not so small) issue with some ASP.NET/Castle Monorail
I have a Windows Service developed in C# and .NET 3.5 to perform various
What I am trying to achieve is a form that has a button on
We are replacing an old classic asp website with a .NET 3.5 solution. We
I am having an issue with Visual Studio 2008 SP1. Basically, I have a

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.