> But i have a project where this is working. If i do the same thing in visual
> studio 2005 and instead of class library3 i create a WebService project and
[quoted text clipped - 3 lines]
> reference 1st project when i am not using it at all? And why does the same
> thing works in VS 2005 if the third project is a WebService?

Signature
http://barrkel.blogspot.com/
Thanks Berry,
But do Web projects also use the same model? even if the third project is a
website, i see the same results (as when i create a webservice).

Signature
Vivek Thakur (MCP)
www.vivekthakur.com
> > But i have a project where this is working. If i do the same thing in visual
> > studio 2005 and instead of class library3 i create a WebService project and
[quoted text clipped - 12 lines]
>
> -- Barry
Barry Kelly - 17 Jul 2006 14:16 GMT
> Thanks Berry,
>
> But do Web projects also use the same model? even if the third project is a
> website, i see the same results (as when i create a webservice).
ASP.NET applications follow this model.
-- Barry

Signature
http://barrkel.blogspot.com/
Also, one more thing as far as copying the DLLs is concerned:
In VS 2003, when i compile ClassLibrary3 project, i can see the assemblies
from ClassLibrary2 and ClassLibrary1 (too) even when i have not referenced
ClassLibrary1. So assemblies are copied in the bin folder of class library 3
but since i get an error the project does not compile.
This is confusing me. Let me know yr thgts on this.
thanks again

Signature
Vivek Thakur (MCP)
www.vivekthakur.com
> > But i have a project where this is working. If i do the same thing in visual
> > studio 2005 and instead of class library3 i create a WebService project and
[quoted text clipped - 12 lines]
>
> -- Barry
Barry Kelly - 17 Jul 2006 14:17 GMT
> Also, one more thing as far as copying the DLLs is concerned:
>
> In VS 2003, when i compile ClassLibrary3 project, i can see the assemblies
> from ClassLibrary2 and ClassLibrary1 (too) even when i have not referenced
> ClassLibrary1. So assemblies are copied in the bin folder of class library 3
> but since i get an error the project does not compile.
IIRC with VS 2003, there was a project file for ASP.NET applications.
I don't recall all the details, it is some years since I used VS 2003.
-- Barry

Signature
http://barrkel.blogspot.com/
Vivek Thakur - 17 Jul 2006 14:34 GMT
So basically even when we have DLLs in the /bin directory, the project wont
compile. i still do not understand this.

Signature
Vivek Thakur (MCP)
www.vivekthakur.com
> > Also, one more thing as far as copying the DLLs is concerned:
> >
[quoted text clipped - 7 lines]
>
> -- Barry
Amry - 18 Jul 2006 08:25 GMT
If I am not mistaken, for web projects, every DLL contained in its bin
directory will be automatically referred and loaded, whereas for other
types of projects, you must explicitly refer to the DLL you want in
order for it to compile.
> So basically even when we have DLLs in the /bin directory, the project wont
> compile. i still do not understand this.
[quoted text clipped - 13 lines]
> >
> > -- Barry
Vivek Thakur - 17 Jul 2006 14:37 GMT
i did some googling and found that this is some bug. see a related post:
http://www.dotnet247.com/247reference/msgs/56/284237.aspx

Signature
Vivek Thakur (MCP)
www.vivekthakur.com
> > Also, one more thing as far as copying the DLLs is concerned:
> >
[quoted text clipped - 7 lines]
>
> -- Barry
Markus Ewald - 18 Jul 2006 08:38 GMT
Vivek Thakur schrieb:
> Also, one more thing as far as copying the DLLs is concerned:
>
[quoted text clipped - 6 lines]
>
> thanks again
The files are always being copied because they are required to run the
application. For example, if A uses B and B uses C, then all three
assemblies will end up int A's bin folder.
References don't really have anything to do with files. If B does not
use any of the types of C in its public interface (by deriving or
expecting them as parameter), then B could be referenced needing another
reference to C (even if it is ultimately required in the bin folder)
However, if B makes use of the types of C in its public interface, then
any assembly that wants to use those methods or classes that are making
use of C's public types will need to also reference C in addition to B.
-Markus-
Vivek Thakur - 18 Jul 2006 18:26 GMT
thanks for the reply..
i know all these answers, but just wanted to confirm whether this is by
design or a bug in C# compiler. what forces me to think like this is the fact
that a similar problem is there which is a bug. see the post below:
http://www.dotnet247.com/247reference/msgs/56/284237.aspx
could this bug be the reason or this is completely un related ?

Signature
Vivek Thakur (MCP)
www.vivekthakur.com
> Vivek Thakur schrieb:
> > Also, one more thing as far as copying the DLLs is concerned:
[quoted text clipped - 22 lines]
>
> -Markus-