Vibrant discussion about CSLA .NET and using the framework to build great business applications.

Forum has moved

New location: CSLA .NET forum

CSLA .NET Resources:
  • CSLA .NET forum
  • CSLA .NET home page
  • Late binding VB.net com class

    rated by 0 users
    Answered (Verified) This post has 1 verified answer | 1 Reply | 1 Follower

    Not Ranked
    9 Posts
    Daniel Morey posted on Wed, Nov 23 2011 6:18 AM

    I've create a my first vb.net assembly with CSLA business objects in. I have then created a seperate vb.net assembly with a com class in it that I'm using to join my business objects to vb6. So in my old vb6 program I late bind to the com class and I call the methods on that, without direct referencing the proper business objects (none of the com class functions return any custom classes)

    Doing this I can successfully get data out of my business objects, but when I try and save them I get a run time error "Unable to find assembly" that looks like it is trying to get my business object component. However the vb6 component does reference the com class that does reference the business object component so I can't see what is going wrong.

    Can anyone shed some light onto why this error occurs? I'm thinking that I don't know enough about how things work when they get referenced, as I've been confused by weird referencing behaviour before (probably only weird due to my lack of knowledge) .

    Answered (Verified) Verified Answer

    Not Ranked
    9 Posts
    Verified by Daniel Morey

    I found that if I signed my assemblies and added them to the GAC then this error can be avoided.

    Not sure if this is the only solution, but it suits me for now.

    Page 1 of 1 (2 items) | RSS

    Copyright (c) 2006-2014 Marimer LLC. All rights reserved.
    Email admin@lhotka.net for support.
    Powered by Community Server (Non-Commercial Edition), by Telligent Systems