Libraries

[Anonymous]

I have a VB code that access certain AEC Libraries in LDDT. Now I am going
to distrubute this program around. Is there anyway you can turn on or set
the libraries on other machines without physically going into references and
doing so. I mainly want people to go through a setup process and it is
embedded inside LDDT and it will work. Currently it comes up and lets you
know it doesn't have the correct libraries.

Thanks in advance Robert

[Anonymous]

I keep hearing that. How are people distibuting their apps? With a compiled
app (EXE, DLL or OCX), you should not need to set any references provided
the app your app was designed for is properly installed on the target
machine. With a decent installer (VB's Deployment Wizard doesn't count) you
should have no probelm with references. Try the Visual Studio Installer.
It's free for anyone with a Visual Studio product. You can find it here:
http://msdn.microsoft.com/vstudio/downloads/vsi/default.asp

--
Get free software and more at http://www2.stonemedia.com/franko

"Robert Gadbaw" wrote in message
news:891jpq$fen25@adesknews2.autodesk.com...
> I have a VB code that access certain AEC Libraries in LDDT. Now I am going
> to distrubute this program around. Is there anyway you can turn on or set
> the libraries on other machines without physically going into references
and
> doing so. I mainly want people to go through a setup process and it is
> embedded inside LDDT and it will work. Currently it comes up and lets you
> know it doesn't have the correct libraries.
>
> Thanks in advance Robert
>
>

[Anonymous]

All we have is just the *.dvb that we are distributing. We don't have any
Visual Studio Product at all. Is there another way of compiling this inside
AutoCad 2000 that would be better? Or do I need to go out and get a Visual
Studio Product? I personally have not written the code it has been given to
me to distribute but am finding this problem always occuring.

Thanks Robert
Frank Oquendo wrote in message
news:891kak$fem18@adesknews2.autodesk.com...
> I keep hearing that. How are people distibuting their apps? With a
compiled
> app (EXE, DLL or OCX), you should not need to set any references provided
> the app your app was designed for is properly installed on the target
> machine. With a decent installer (VB's Deployment Wizard doesn't count)
you
> should have no probelm with references. Try the Visual Studio Installer.
> It's free for anyone with a Visual Studio product. You can find it here:
> http://msdn.microsoft.com/vstudio/downloads/vsi/default.asp
>
> --
> Get free software and more at http://www2.stonemedia.com/franko
>
>
> "Robert Gadbaw" wrote in message
> news:891jpq$fen25@adesknews2.autodesk.com...
> > I have a VB code that access certain AEC Libraries in LDDT. Now I am
going
> > to distrubute this program around. Is there anyway you can turn on or
set
> > the libraries on other machines without physically going into references
> and
> > doing so. I mainly want people to go through a setup process and it is
> > embedded inside LDDT and it will work. Currently it comes up and lets
you
> > know it doesn't have the correct libraries.
> >
> > Thanks in advance Robert
> >
> >
>
>