Last post Jul 07, 2010 12:28 PM by harlock1975
Jun 11, 2010 11:21 AM|harlock1975|LINK
Hi there, I am new to the forum but a long time ASPNET developer.
The project I am working on is getting quite big, so I'd like to split it in several subprojects. I could not use the "usual" approach described in variuos sites (and in this forum), so I managed to do it this way
- copying the main project file in the same folder (proj1.csproj to proj2.csproj)
- opening proj1 and leaving only the theme files, master pages and base classes (excluding all the other files)
- opening proj2 and leaving only some of the content files (excluding also the files already present in proj1)
- adding a reference to proj1 in proj2 (the content pages inherit from a class in proj1 assembly)
This solution compiles to proj1.dll and proj2.dll and seems to run just fine, I have only a few "conceptual" concerns:
- do you think this is something that is likely to break in future releases of ASPNET? I tested it only with version 2.0 (in both VS 2010 and 2005), as I cannot switch to ASP.NET 4 right now (the app is using some 2.0-only controls)
- can there be some security and/or performance issues using this architecture? can you spot any flaw?
Thanks in advance
Jun 17, 2010 02:54 AMemail@example.com|LINK
it might be issue in your application performance.
you can add more project in one aplication(module wise) and integrate it.
add sub project in main application and add their refrences in main application.
define in more than one layers. paresentation layer for all pages. business logic, business objects, Data Access, logic, custom control and common function etc...
it will be better approach for security and web performance.
Jun 18, 2010 09:13 AM|Live Wire|LINK
I would like to say one thing here. Any architecture or design should be such that it should be resilient to changes. In your case if you think the present architecture can accommodate any changes/enhancement with least impact then u r there.
Now talking about the performance and security you need to gauge and prioritize by asking questions like.
How many concurrent users are there?
What is the size of data that may flow to and fro?
What’s the level of security required?
Jun 21, 2010 06:42 AM|Live Wire|LINK
This link is superb reference for designing performance rich apps
Jul 07, 2010 12:28 PM|harlock1975|LINK
Sorry if I did not reply, I have been away for vacation (too short, unfortunately!!!)
My solution is already split in several projects (UI, business, data, a common layer and a few controls).
My goals were
- minimize startup time by jitting less objects grouped together
- in each subproject I could have less references, so less assemblies to load
- work concurrently on different areas of the product
My concerns are related to having several subprojects reference the same assemblies (proj1 and proj2 share a reference to proj3, is this loaded only once?) and to the fact that this approach looks like a "glitch" in ASPNET rather than a proper solution.
Any more ideas/thoughts?
Thanks for the help!