Where to place the assemblies?

[ResolutionsNET]

If I have a setup of a web server and a database server, and my application is split into three layers, UI, Business and Data. With the Data layer calling stored procedures, where is the best place to these assemblies. e.g. if the DAL assembly sits on the SQL server what are the security/performance implications and does this mean I have to make this a remoting object.

If the DAL assembly stays on the web server, what are the
security/performance implications.

Thanks for any help.

 

[jfrost10]

I've never worked in a multi-box scenario before, but a co-worker has. They had seperate machines for data, logic, and presentation. He said that they did notice a performance hit, because of all the network traffic overhead of passing the data accross the three boxes.

But, the trade off is that going with three boxes you're VERY secure, so it all depends on what you're willing to sacrifice.

D'Arcy

 

[chiph]

You could leave your DAL on your webserver, but in a different directory outside your IIS directory tree. You would then register those assemblies in the GAC using GacUtil.

Doing this has some side-effects:
1. You need to be very disciplined about your versioning (If you leave your AssemblyInfo version attribute as the "1.0.*" default you will have problems)
2. Some people don't care to use the GAC for user assemblies -- they feel it should only be used for Microsoft's code.
3. You can't do a XCopy update anymore - you'll have to use an update script of some kind to call GacUtil.

Chip H.


If you want to get the best response to a question, please check out FAQ222-2244 first