Separate dlls - RunUO

yarex · 09-14-2006, 08:58 AM

Hi,

What about to separate some or related classes / namespaces into separated dlls/assemblies, that would be referenced from main server project?

Also, would be nice to have an option to do the same with all custom scripts and easily to attach/compile them into main "core" as another dll.

That would separate better related code (for example some bigger namespace = separate assembly) but also would allow to speed up compilation and recompile only assemblies that have been changed.

Your Opinions?

Courageous · 09-14-2006, 05:02 PM

Try it, and see how it works. I often add a lot of stuff under Scripts/Custom. I twould be nice if that area alone had a different compilation rule for the rest.

C//

yarex · 09-14-2006, 05:16 PM

I tried it, but the problem is, that the main function is too much bound with the rest of the code, so its not so easy to split it into dlls and separate logic not only by folders, but also by dlls. Also, even if i would spent that energy to separate it, the problem is, that it would became my "custom" core, that isn't unfortunately (but logically) supported by runuo developers.

The best would be, if sources in runuo source control would be splitted into separate subprojects and joined into one big solution that could be then easily loaded / fast compiled / logically separated.

**Mark** · 09-08-2007, 07:57 AM

I have actually considered the benefits of this but the complexity of resolving interdependancies is brutal.

EDIT: Yes, I know it is a year later. :P

HellRazor · 09-08-2007, 11:24 AM

Mark's a little slow these days but we're sure glad he's around.

09-14-2006, 08:58 AM	#1 (permalink)
yarex Forum Newbie Join Date: Jun 2005 Age: 31 Posts: 45	Separate dlls Hi, What about to separate some or related classes / namespaces into separated dlls/assemblies, that would be referenced from main server project? Also, would be nice to have an option to do the same with all custom scripts and easily to attach/compile them into main "core" as another dll. That would separate better related code (for example some bigger namespace = separate assembly) but also would allow to speed up compilation and recompile only assemblies that have been changed. Your Opinions?

09-08-2007, 11:24 AM	#5 (permalink)
HellRazor Forum Expert Join Date: Oct 2002 Age: 45 Posts: 4,372	Mark's a little slow these days but we're sure glad he's around. __________________

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

09-14-2006, 05:02 PM	#2 (permalink)
Courageous Forum Expert Join Date: Nov 2005 Location: San Diego, CA Posts: 1,825	Try it, and see how it works. I often add a lot of stuff under Scripts/Custom. I twould be nice if that area alone had a different compilation rule for the rest. C//

09-14-2006, 05:16 PM	#3 (permalink)
yarex Forum Newbie Join Date: Jun 2005 Age: 31 Posts: 45	I tried it, but the problem is, that the main function is too much bound with the rest of the code, so its not so easy to split it into dlls and separate logic not only by folders, but also by dlls. Also, even if i would spent that energy to separate it, the problem is, that it would became my "custom" core, that isn't unfortunately (but logically) supported by runuo developers. The best would be, if sources in runuo source control would be splitted into separate subprojects and joined into one big solution that could be then easily loaded / fast compiled / logically separated.

09-08-2007, 07:57 AM	#4 (permalink)
Mark Forum Administrator Join Date: Jan 2003 Location: Northern Virginia Posts: 1,554	I have actually considered the benefits of this but the complexity of resolving interdependancies is brutal. EDIT: Yes, I know it is a year later. :P

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)