By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,065 Members | 1,560 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,065 IT Pros & Developers. It's quick & easy.

Reference DLL Question

P: n/a
Hi,

lets say that i have A.DLL and B.DLL.

A.Dll hold reference to B.DLL.

if i changed the B.DLL should i recompile A.DLL in order to get the new
version ?

does the A.DLL will Work with the new version of B.DLL without recompile ?

how can i prevent this dependency ?

one more question,

i have some project which hold 1 vb file and 1 aspx file or other type of
file.

when i build the project it will build the vb and the other files to one dll
or it will build just the vb file ?
Best Regards ,

Tiraman :-)
Nov 20 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Tiraman,

1. You should put both the A project and the B project in the same solution
and reference the B project from the A project. You can do this from the
"Projects" tabe on the Add Reference dialog after both projects are in the
same solution.

2. Both the vb and aspx file are built when you run the project or choose
the build/rebuild option.

-Sam Matzen
"Tiraman" <ti*****@netvision.net.il> wrote in message
news:ua**************@TK2MSFTNGP11.phx.gbl...
Hi,

lets say that i have A.DLL and B.DLL.

A.Dll hold reference to B.DLL.

if i changed the B.DLL should i recompile A.DLL in order to get the new
version ?

does the A.DLL will Work with the new version of B.DLL without recompile ?

how can i prevent this dependency ?

one more question,

i have some project which hold 1 vb file and 1 aspx file or other type of
file.

when i build the project it will build the vb and the other files to one dll or it will build just the vb file ?
Best Regards ,

Tiraman :-)

Nov 20 '05 #2

P: n/a
Hi,

Thanks for your explanation but i asked for some thing else :-)


"Samuel L Matzen" <sm*****@slm.com> wrote in message
news:el**************@TK2MSFTNGP10.phx.gbl...
Tiraman,

1. You should put both the A project and the B project in the same solution and reference the B project from the A project. You can do this from the
"Projects" tabe on the Add Reference dialog after both projects are in the
same solution.

2. Both the vb and aspx file are built when you run the project or choose
the build/rebuild option.

-Sam Matzen
"Tiraman" <ti*****@netvision.net.il> wrote in message
news:ua**************@TK2MSFTNGP11.phx.gbl...
Hi,

lets say that i have A.DLL and B.DLL.

A.Dll hold reference to B.DLL.

if i changed the B.DLL should i recompile A.DLL in order to get the new
version ?

does the A.DLL will Work with the new version of B.DLL without recompile ?
how can i prevent this dependency ?

one more question,

i have some project which hold 1 vb file and 1 aspx file or other type of file.

when i build the project it will build the vb and the other files to one

dll
or it will build just the vb file ?
Best Regards ,

Tiraman :-)


Nov 20 '05 #3

P: n/a
If the interface in B.dll changed, then of course the answer is yes.

Otherwise, simply copying B.dll into the application directory, should be
sufficient for the new version of B.dll to be used at run time.

"Tiraman" <ti*****@netvision.net.il> wrote in message
news:ua**************@TK2MSFTNGP11.phx.gbl...
Hi,

lets say that i have A.DLL and B.DLL.

A.Dll hold reference to B.DLL.

if i changed the B.DLL should i recompile A.DLL in order to get the new
version ?

does the A.DLL will Work with the new version of B.DLL without recompile ?

how can i prevent this dependency ?

one more question,

i have some project which hold 1 vb file and 1 aspx file or other type of
file.

when i build the project it will build the vb and the other files to one dll or it will build just the vb file ?
Best Regards ,

Tiraman :-)

Nov 20 '05 #4

P: n/a
Thanks !

"Marina" <so*****@nospam.com> wrote in message
news:eJ**************@tk2msftngp13.phx.gbl...
If the interface in B.dll changed, then of course the answer is yes.

Otherwise, simply copying B.dll into the application directory, should be
sufficient for the new version of B.dll to be used at run time.

"Tiraman" <ti*****@netvision.net.il> wrote in message
news:ua**************@TK2MSFTNGP11.phx.gbl...
Hi,

lets say that i have A.DLL and B.DLL.

A.Dll hold reference to B.DLL.

if i changed the B.DLL should i recompile A.DLL in order to get the new
version ?

does the A.DLL will Work with the new version of B.DLL without recompile ?
how can i prevent this dependency ?

one more question,

i have some project which hold 1 vb file and 1 aspx file or other type of file.

when i build the project it will build the vb and the other files to one

dll
or it will build just the vb file ?
Best Regards ,

Tiraman :-)


Nov 20 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.