CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 6 of 6
  1. #1
    Join Date
    Jun 2004
    Posts
    61

    [RESOLVED] exception error when replacing dll

    Hello all,

    I have an old dll which not in use anymore in my asp.net application which calls infrastructure.dll
    I tried to remove it and replce it by new dll which also called infrastructure.dll
    Building web site sucseeds, but when I try to run the application, I get
    this TypeLoadException (during site upload):
    Code:
    Could not load type 'InfraStructure.LogClass' from assembly 'Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'.
    and cannot continue...(LogClass is a function from old dll which not in use anymore as I said and not appears at all in the application)
    any ideas?

    10x!

  2. #2
    Join Date
    Sep 2008
    Location
    Netherlands
    Posts
    865

    Re: exception error when replacing dll

    It looks like it tries to load this 'InfraStructure.LogClass', but the question is where..

    Maybe it the web.config there is some reference to this type?

  3. #3
    Join Date
    Jun 2004
    Posts
    61

    Re: exception error when replacing dll

    I looked for this string in the entire solution (including web.config) but didn't find anything...

  4. #4
    Join Date
    Jun 2004
    Location
    Kashmir, India
    Posts
    6,808

    Re: exception error when replacing dll

    This looks to be an issue with references. Check if you have proper references set. Does it refer to the proper DLL that you created?

  5. #5
    Join Date
    Jun 2004
    Posts
    61

    Re: exception error when replacing dll

    I double checked it...I removed from project properties the old refeernce and added the new one.
    I added the new dll as a project to my solution and verified the new refrence taken from the project.
    what do I miss?

  6. #6
    Join Date
    Jun 2004
    Posts
    61

    Re: exception error when replacing dll

    Finally solved the mistery...
    I had another dll in my project which was using the old infrastructure.dll...
    removing from this dll the reference to old infrastructure.dll solved the problem!
    haleluya

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  





Click Here to Expand Forum to Full Width

Featured