We are trying to port our inhouse used web projects to .NET, thats based on
multiple libraries developed by our different programmers/teams.

I just want to know, what are available options to share different
assemblies across different web projects.

GAC is good, but xcopy deployment is our primary reason for .NET adaption.
Does one have to unregister and register global assembly like COM? If their
is change in interface/class signatures?

Each ASP.NET application look for assemblies in \bin folder, can we specify
mutliple folders to look for, for instance we have c:\team1, c:\team2...
folders, accessable to our teams over FTP where they upload their work, and
our projects, from c:\project1, c:\project2 can access these sharred
assemblies apart of respective \bin folders




Regards

well aziz.....
If u have the class project then one can always reference the project as a
whole... in that case u dont have to copy the dll from the class projects
dll and paste it to ur web-project /bin folder.... 

hope every teams class projects are different projects.... 

keep me posted if u have issues

==============================
S.Ramanujam
Programmer Analyst
Cognizant technology Solutions (p) Ltd. - CTS
38 & 39 Whites Road,
WCB - Whites Road Circular Building
Royapettah, Chennai - 600014
Ph : +xx xx xxx xxxx Extn 5113 [Off]


-----Original Message-----
From: Khurram Aziz [mailto:khurram@n...]
Sent: Tuesday, September 03, 2002 6:53 PM
To: ASP+
Subject: [aspx] sharring assemblies


We are trying to port our inhouse used web projects to .NET, thats based on
multiple libraries developed by our different programmers/teams.

I just want to know, what are available options to share different
assemblies across different web projects.

GAC is good, but xcopy deployment is our primary reason for .NET adaption.
Does one have to unregister and register global assembly like COM? If their
is change in interface/class signatures?

Each ASP.NET application look for assemblies in \bin folder, can we specify
mutliple folders to look for, for instance we have c:\team1, c:\team2...
folders, accessable to our teams over FTP where they upload their work, and
our projects, from c:\project1, c:\project2 can access these sharred
assemblies apart of respective \bin folders




Regards



---

ASP.NET 1.0 Namespace Reference with C#
http://www.wrox.com/acon11.asp?ISBN=1861007442

ASP.NET 1.0 Namespace Reference with VB.NET
http://www.wrox.com/acon11.asp?ISBN=1861007450

These books are a complete reference to the ASP.NET namespaces 
for developers who are already familiar with using ASP.NET. 
There is no trivial introductory material or useless .NET 
hype and the presentation of the namespaces, in an easy-to use 
alphabetical order ensures a user-friendly reference format.
We provide in-depth coverage of all the major ASP.NET classes, 
giving you those real-world tips that the documentation doesn't 
offer, and demonstrating complex techniques with simple 
examples.  

---