Re: Help on designing a modular ASP.NET architecture
- From: Don Huan <don@xxxxxxxxx>
- Date: Tue, 09 Aug 2005 11:03:19 +0200
I checked it and there's no way to compile a *UserControl* into a dll and reference it. That can be done with CustomControls only..
Grant Merwitz wrote:
Not sure about that actually.
I know you can compile them into a dll, but not sure if it can be referenced like a project reference,
but i can't imagine why not.
"Don Huan" <don@xxxxxxxxx> wrote in message news:OOikmXCnFHA.3936@xxxxxxxxxxxxxxxxxxxxxxx
ASAIK there's no way to compile and reference UserControls across projects (like custom controls), or is there one? At least, VS doesn't provide me the ability to create a UserControl inside of a project other than WebProject (like in a Web Class Library).
I'm relatively new to asp.net, so sorry for dumb question :)
Don
Grant Merwitz wrote:
How come you can't use UserControls.
It's definately a way to modularise a WebSite (i've found), and you can compile them, and reference and use them across projects.
Hence you could modularise them.
But this sounds like an awfull amout of work.
Considering they will most likely only be used in one solution - the website,
why not group them all together under one solutiong, in a folder structure simulating your current modules.
They are, after all, just a UI to your modules, and shouldn't contain too much functionality as it will be using the code you already have
"Don Huan" <don@xxxxxxxxx> wrote in message news:uR4ag%23BnFHA.3408@xxxxxxxxxxxxxxxxxxxxxxx
Thanks all for quick responce.
Actually every of our modules consists of 3-4 Projects like - module.buisnesslogic - module.common - module.winform
So the requirement is to create one project like - module.aspnet for every module.
And that's the reason I can't use UserControls.
My further thoughts are about orginizing css/js and so on in such a big solution. The aim is to keep web site both modular and simply.
Grant Merwitz wrote:
I think you spot on with your solution.
You don't necessarily have to use controls, but they are nice if there's set pieces of functionality you want to reuse.
The nice thing about keeping it in the same solution, is that you don't have to keep referencing your compiled dll's,
as you make changes to your projects it will update the project references set up in Visual Studio.
I have a project setup similair to the one you are talking - a tad smaller though - but it works like a charm.
one annoying thing however, may be compile time when developing, you can ofcourse just rebuild the web project on its own, but when debugging this may be frustrating.
"Don Huan" <don@xxxxxxxxx> wrote in message news:OjyPRgBnFHA.3988@xxxxxxxxxxxxxxxxxxxxxxx
Hi
my job is to migrate our WinForms application to ASP.NET. This app was build very modular so every peace of code can be replaced by another "modul". There are 1 VS-solution with about 60 projects (dll's) in it.
Now I have to design a Web-Client modul (actually the web-interface). To maintain the modularity, I thought of making one ASP.NET-Project inside of the solution and create some projects containing Custom Web Controls.
Did somebody has similar design requirements? Is there any better/alternative solutions (links)? What is your advice?
Don
.
- References:
- Help on designing a modular ASP.NET architecture
- From: Don Huan
- Re: Help on designing a modular ASP.NET architecture
- From: Grant Merwitz
- Re: Help on designing a modular ASP.NET architecture
- From: Don Huan
- Re: Help on designing a modular ASP.NET architecture
- From: Grant Merwitz
- Re: Help on designing a modular ASP.NET architecture
- From: Don Huan
- Re: Help on designing a modular ASP.NET architecture
- From: Grant Merwitz
- Help on designing a modular ASP.NET architecture
- Prev by Date: Transactions
- Next by Date: Re: Help on designing a modular ASP.NET architecture
- Previous by thread: Re: Help on designing a modular ASP.NET architecture
- Next by thread: Re: Help on designing a modular ASP.NET architecture
- Index(es):
Relevant Pages
|