Forums Ultimate UI for ASP.NET Web Forms
Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
Close
Jane
100
Dependency cannot be found
posted

I have an earlier post about Infragistiics 2005 v.3, but this one seems more vexing.

I have a .net 1.nn web app; the app was compiled into a .dll, so when I made the changes to the vb, I tried to compile.  I'm getting errors 'dependency to [infragistics control in v3.2] could not be found'.  In addition, the error 'Cannot transform license file into binary error LC003: unable to resolve type ' and then the name of the 3.2 control.

Apparently this is because the app was originally under Visual Source Safe, and it's looking for these objects. 

I installed Infragistics on my workstation but I don't see a license.licx file; I copied the .licx from my staging server.  Could this be a problem?

Jane

  • 45049
    Suggested Answer
    posted

    Either your web application has a reference to the other assembly, or there's an entry in your licenses.licx file that contains such a reference.

    hollsys said:
    I installed Infragistics on my workstation but I don't see a license.licx file; I copied the .licx from my staging server.  Could this be a problem?

    It might be.  From the file you copied over to your website, clear out any references to Infragistics assemblies from the file.  (In practice, Visual Studio will re-add the current references when it needs it, when you next open the file at design-time.)  Alternately, you can manually update the version numbers in these references to point to the file names and versions you actually have installed.

    Another possibility is that you may have references to some of the design-time assemblies used by our controls (all of which contain the word "Design" in the file name).  If so, then you should remove these references altogether.  These design-time assemblies are not redistributable, so you shouldn't be deploying them along with to a website.

    If this doesn't resolve your issue, then we'll need more information.  What is the full message that comes up in the "unable to resolve type" error (or all such errors, if you're getting more than one)/