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 546121
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T10:50:01+00:00 2026-05-13T10:50:01+00:00

I have three machines. one installed VS2008 another two installed SDK6 and Framework3.5 (one

  • 0

I have three machines. one installed VS2008 another two installed SDK6 and Framework3.5 (one of these two is a build machine).

When I use MSBuild to build our application, all of them get this warning:

C:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets : warning MSB3245: Could not resolve this reference. Could not locate the assembly “WPFToolkit, Version=3.5.40128.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35”. Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

and the build machine comes with some errors:

scsm\SCSM.cs(234,13): error CS1501: No
overload for method ‘Invoke’ takes ‘1’
arguments scsm\SCSM.cs(235,13): error
CS1501: No overload for method
‘Invoke’ takes ‘1’ arguments
scsm\SCSM.cs(304,13): error CS1501: No
overload for method ‘Invoke’ takes ‘1’
arguments scsm\SCSM.cs(314,13): error
CS1501: No overload for method
‘Invoke’ takes ‘1’ arguments
scsm\SCSM.cs(317,13): error CS1501: No
overload for method ‘Invoke’ takes ‘1’
arguments scsm\SCSM.cs(323,17): error
CS1501: No overload for method
‘Invoke’ takes ‘1’ arguments
scsm\SCSM.cs(324,17): error CS1501: No
overload for method ‘Invoke’ takes ‘1’
arguments scsm\SCSM.cs(325,17): error
CS1501: No overload for method
‘Invoke’ takes ‘1’ arguments

but other machines are passed without error. Resources are identical in those three machines.

searched online but cannot find answer. Anybody here can help me resolve this?
thanks

  • 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-13T10:50:01+00:00Added an answer on May 13, 2026 at 10:50 am

    Could not locate the assembly “WPFToolkit, Version=3.5.40128.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35”.

    WPFToolkit is not part of the .net Framework but a component that can be downloaded.

    Did you download and copy the WPFToolkit-DLL to some place on the build machine where your project can find it? (either some directory set in your project references or the GAC)


    scsm\SCSM.cs(325,17): error CS1501: No overload for method ‘Invoke’ takes ‘1’ arguments

    In my experience, this problem can mean that you are missing SP1 for .net Framework 3.5.

    EDIT: After seeing your code, I’m pretty sure this is the problem. Dispatcher.Invoke(delegate, params object[] args), which you are calling here, was added in Framework 3.5 SP1, see the MSDN page of this method:

    Supported in: 3.5 SP1, 3.0 SP2

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

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.