All geek questions in one place

Deploying an ASP.NET Portal Application

There is a requirement to write a portal as an ASP.NET-based web application . A lightweight central application must existwhich implements basic navigation and authentication . Design is achieved using masterpages .

Then there are several more or less independent applications. (old and new!) that should be integrated easily and independent is the central application (which should be the entry point of these applications). What methods , architectures , patterns , methods and capabilities can help and support to achieve these goals? For example, does it make sense to run (under) applications in an iframe ?

Are there (easy and easy to learn) portal frameworks that you can use (not as big things as "DOTNETNUKE")?

Many thanks in advance for tips, advice and help!

+3
source share
2 answers

DO NOT EXPOSE THE WHEEL! The thing about DotNetNuke is that it can be as big or small as you make it. If you use it correctly, you will find that you can limit it to what you need. Do not expose yourself to the same pain that others have already passed. Unless, of course, you are only interested in your pain.

I am not saying that DNN is right for you. This may not be true, but take the time to research several open source portals before you decide to write your own. The features you describe will take 1000 hours to develop and test if you write them all from scratch.

@ , . , , , , , Codeplex, .

+3

, ( ), :

  • MVC 2.0
  • / (, StructureMap)
  • Framework
  • NHibernate ( , , ​​ Sh # rp Spring.NET
  • (, NServiceBus).

MVC, ( MEF), (NHibernate), , " " , (NServiceBus).

IoC DI, , . MEF ", " , , , , ..

+2

Source: https://habr.com/ru/post/1753266/

More articles:


All Articles