I have a few applications that I plan to build through VS.NET. I want to
employ some common UI framework in all of the apps; a collection of user
controls.

I cannot figure out a good way of doing this. I built a DLL for the control
library and added that to a project, but that requires deploying the DLL
across a whole bunch of projects (in the future) if the UI should change.
I'd like one centralized location.

Any tips?

Wells Oliver
Web Application Programmer
Leviton Voice & Data
xxx-xxx-xxxx
http://www.levitonvoicedata.com

There's a good tutorial at http://www.wilsondotnet.com

Alvin

> -----Original Message-----
> From: Oliver, Wells [mailto:WOliver@l...] 
> Sent: Thursday, September 26, 2002 6:02 PM
> To: ASP+
> Subject: [aspx] Employing a common UI framework across applications?
> 
> 
> I have a few applications that I plan to build through 
> VS.NET. I want to employ some common UI framework in all of 
> the apps; a collection of user controls.
> 
> I cannot figure out a good way of doing this. I built a DLL 
> for the control library and added that to a project, but that 
> requires deploying the DLL across a whole bunch of projects 
> (in the future) if the UI should change. I'd like one 
> centralized location.
> 
> Any tips?
> 
> Wells Oliver
> Web Application Programmer
> Leviton Voice & Data
> xxx-xxx-xxxx
> http://www.levitonvoicedata.com
> 
> 
> ---
> 
> 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.  
> 
> ---
> 
> 
> 

If you put the DLL into the GAC (Global Assembly Cache), it becomes
available for use by all projects running on that machine, and if you update
the registry appropriately, you can make that DLL available in the .Net part
of the "Add A Reference" dialog instead of making an external reference to
the DLL. 

You can add DLLs to the GAC by using the gacutil utility or you can refer to
this excellent article
http://www.microsoft.com/india/msdn/experiencedotnet/static/data/articles/ga
c.htm


Hope this helps

Jagdeep Dua
.Net Architect
netdecisions ltd.



-----Original Message-----
From: Oliver, Wells [mailto:WOliver@l...] 
Sent: 26 September 2002 23:02
To: ASP+
Subject: [aspx] Employing a common UI framework across applications?

I have a few applications that I plan to build through VS.NET. I want to
employ some common UI framework in all of the apps; a collection of user
controls.

I cannot figure out a good way of doing this. I built a DLL for the control
library and added that to a project, but that requires deploying the DLL
across a whole bunch of projects (in the future) if the UI should change.
I'd like one centralized location.

Any tips?

Wells Oliver
Web Application Programmer
Leviton Voice & Data
xxx-xxx-xxxx
http://www.levitonvoicedata.com


---

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.  

---