OnTheAnvil
Regular
I'm trying to seperate some of my business logic into DLLs for the first time and I'm hitting some problems. To simplify what I'm trying to do assume I have an new Visual Basic Class Library Project Named "TestApp" with a Car class(car.vb) and a tire class(tire.vb). The car class needs to use the tire class so it has a "Imports TestApp.Tire" at the top.
The problem occurs when I try to compile using vbc.exe
I can compile the tire class into a DLL just fine by running:
vbc /t:library /out:tire.dll tire.vb
but when I try to compile the car class by running:
vbc /t:library /reference:tire.dll /out:car.dll car.vb
I get an error "error BC30002: Type 'TestApp.Tire' is not defined"
The reason I need these to be seperate dll's is because I want to be able to have multiple applications running that use the same car class but each appliction will have it's own version of the tire class. Just for clarification the tire class will always expose the same public methods but it will need to have different variations of the private methods.
So ultimately I'd like to be able to move the car.dll into an application and then place the appropriate tire.dll and have everything work together without having to compile a combined car-tire.dll specifically for each application.
Is this even possible?
Thanks,
OnTheAnvil
The problem occurs when I try to compile using vbc.exe
I can compile the tire class into a DLL just fine by running:
vbc /t:library /out:tire.dll tire.vb
but when I try to compile the car class by running:
vbc /t:library /reference:tire.dll /out:car.dll car.vb
I get an error "error BC30002: Type 'TestApp.Tire' is not defined"
The reason I need these to be seperate dll's is because I want to be able to have multiple applications running that use the same car class but each appliction will have it's own version of the tire class. Just for clarification the tire class will always expose the same public methods but it will need to have different variations of the private methods.
So ultimately I'd like to be able to move the car.dll into an application and then place the appropriate tire.dll and have everything work together without having to compile a combined car-tire.dll specifically for each application.
Is this even possible?
Thanks,
OnTheAnvil