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

  • Home
  • SEARCH
  • 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 6731357
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T10:31:08+00:00 2026-05-26T10:31:08+00:00

I have had these two errors since I have started my project: A reference

  • 0

I have had these two errors since I have started my project:

"A reference was created to embedded interop assembly 'stdole' because of an indirect reference to that assembly from assembly 'AxInterop.MSComctlLib'. Consider changing the 'Embed Interop Types' property on either assembly."

and

A reference was created to embedded interop assembly 'stdole' because of an indirect reference to that assembly from assembly 'mscomctl'. Consider changing the 'Embed Interop Types' property on either assembly."

Then just a second ago, I started getting this error and now I cant publish the program.

"The referenced assembly "Microsoft.VisualBasic.PowerPacks, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL" could not be resolved because it has a dependency on "System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which is not in the currently targeted framework ".NETFramework,Version=v4.0,Profile=Client". Please remove references to assemblies not in the targeted framework or consider retargeting your project."

I’m not using power pack or mscomctl, the only things I am importing are:

System.Windows.Forms.DataVisualization.Charting,
System.IO,
System.Text.RegularExpressions,
Microsoft.Office.Interop.Excel

This is killing me, Ive checked my recent references and there is nothing in there, and I check my program properties>references and there is nothing referring to power pack or mscomctl.

  • 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-26T10:31:08+00:00Added an answer on May 26, 2026 at 10:31 am

    The reference to Microsoft.Office.Interop.Excel is creating the first two warnings. Here is a link to the Microsoft KB article that describes the issue:

    http://msdn.microsoft.com/en-us/library/ff182188.aspx

    You should be able to remove the error with the following steps:

    1) Open your references in Visual Studio

    2) Select Microsoft.Office.Interop.Excel

    3) Press F4 to display the properties page for the reference (or select Properties Window from the View menu)

    4) Change the Embed Interop Types value in the properties sheet to False.

    I would check your references again if the PowerPacks reference just started showing up because you may have accidentally dragged a control from PowerPacks onto one of your forms.

    If it still isn’t visible, try closing your project, then opening the .vbproj file in Notepad or Wordpad and manually remove the reference to PowerPacks then reopen the solution.

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

Sidebar

Related Questions

Since CS3 doesn't have a web service component, as previous versions had, is there
I have had many requests come in to a project that I work on,
EDIT : I had tried these two ways before - List<double> doubleList = stringList.ConvertAll(x
I had, and have since corrected, something like the following code: class SomeClass {
Have had to write my first proper multithreaded coded recently, and realised just how
We have had SharePoint where I work for a little while now, but we've
I have had to do this several times, usually when trying to find in
I have had a bug recently that only manifested itself when the library was
We have had issues with Mootools not being very backward compatible specifically in the
I have had a few problems with log files growing too big on my

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.