CSLA 1.53: Compiling into single assembly

CSLA 1.53: Compiling into single assembly

Old forum URL: forums.lhotka.net/forums/t/1956.aspx


cjherasmus posted on Tuesday, December 12, 2006

Hi,

I've compiled all the CSLA libraries into a single assembly, but now I can't get remoting to work. I think I should be changing something in the web.config file, but I don't know what or how it should be changed. Could anyone please help me.

Much appreciated,

Thanks

Q Johnson replied on Wednesday, December 13, 2006

I'm a little surprised at your attempt to compile all the CSLA components into a single assembly.  I can't articulate the reasons they  should be in separate ones, but I believe they should be.

I believe the book is pretty clear on this in both 1.x and 2.x - but I'm in a hotel room about 2000 miles from those books.  The end of chapter two (framework design, namespace organization ) and most of chapter three (framework implementation) address these issues - at least in the 2.x book (I looked at the pdf version on my laptop).

Maybe by separating them back out, you'll get what you want.

Michael Hildner replied on Wednesday, December 13, 2006

cjherasmus,

You just compiled CSLA, right? You didn't modify any source?

cjherasmus replied on Wednesday, December 13, 2006

Michael,

Yes, just compile, no modifications to the existing source.

cjherasmus replied on Wednesday, December 13, 2006

The idea was to keep the CSLA namespaces as they are,but to have only one dll.

There's no particular reason why I want to compile CSLA into a single assembly. To me it doesn't matter if there are one dll or 4 dll's. I was just experimenting with the idea.

 

ajj3085 replied on Thursday, December 14, 2006

Well I don't think the 2.0 book explains why the assemblies must be seperate, because in 2.0 its all one assembly now.  Personally I think that's easier to work with, but there might be something in .Net 1.1 that forces the assemblies to be seperate.

Copyright (c) Marimer LLC