Would you like to just focus on your business domain and host it anywhere easily rather than fussing with infrastructure? With DomainAspects you just write the interface in a project called [MyDomain].Common and the implementation is a project called [MyDomain]. Now add a brief and easy configuration string to both client and service host and xcopy deploy. Restart your hosting service if you are using the domain remotely.
With DomainAspects, all access to the implementation is now controlled as you have specified through easy attributes on your implementation without ever writing specific code to validate and authorize. Each and every call is logged without adding any logging code. Each and every exception is logged without ever adding a try/catch block in your code. And exceptions are captured, logged, and thrown up the chain to the client.
Introducing the 2.0 version of DomainAspects. This new version contains some major changes, the chief among them is the introduction of a WCF host container that allows you to access your aspect oriented domain layer remotely. More on the changes and features later, but first, let’s review what has come before and contributed to this new release:
And some earlier posts that have formed the creation of the WCF host in this new version:
DomainAspects 2.0 Introduced Today
Over the last couple of months, I’ve spend considerable time on the weekends to complete the idea of merging my previous work on a generic WCF host into my DomainAspects project. Since I had not touched either of these projects for some time, it was fun and interesting to look at them from a new perspective. There are many changes for the better here. Please download it and give it a try. I am eager to hear your feedback.
New in DomainAspects 2.0
Today, I’m releasing DomainAspects 2.0 which supports the following new features:
- A WCF host service for accessing domain services running in another process or server with the following features/benefits:
- Fast and encrypted net.tcp binding with Windows permissions.
- Simplified custom configuration section that is the same on client and server.
- Custom instance provider uses the DomainAspects service factory and Windsor for instance creation and release.
- Ability to specify service instance lifestyle closely matching Windsor (PerThread, Pooled, Singelton, SingleCall).
- Service host that will run in console mode for easy debugging.
- Flip a config switch and install the service host as a windows service. No recompile required.
- RemoteClient implements IDisposable correctly, dealing with Abort vs Close for you.
- Host can be configured to use a fake PrincipalProvider for easily testing a variety of user roles and combinations.
- Reliance on DomainAspects for authorization rather than configured local Windows groups.
- A light remote client assembly allows access DomainAspects with minimal deployment requirements.
- Local client and remote client both return an instance of the service interface, allowing a domain to be moved to another process or remote server with minimal changes to client code.
- Upgrade to the current stable release Castle Windsor 3.0 container libraries.
- Improved domain service factory allows greater instance creation control.
- Additional tests, including multi-threaded remote tests focusing on instance creation and pooling.
- More intuitive, self-describing classes to make understanding the code easier.
Using DomainAspects 2.0
Using the DomainAspects solution is easy. You must have Visual Studio 2010 Pro or higher. If you do not, you may spend considerable time trying to get it running. I would not recommend it.
Download the code and make sure you right click the zip file and go to properties and unlock the zip file before you extract it.
To run remote tests, be sure to start the DomainAspects.Host without debugging first. I recommend running the MultiRemoteTests class using a multiple project startup with the host running first and the DomainAspects.TestConsole running the test rather than the automated tests runner since I have not found a way to get those tests to run properly within the test harness.
Now run the tests. Watch the host console as the MultiRemoteTests run. Note the instance creation on second and third run take zero time because these instances have been pooled.
When you are ready to build your own domain service, just follow the examples in the TestDomain and TestDomain.Common projects. Configure the host and the client as shown in the app.config files in the included projects appropriately to match your new domain and domain.Common assemblies.
If you are going remote, build and deploy the DomainAspects.Host. Make sure you switch the “consoleMode” attribute in the config on the server side to “Off” so that it will install and run as a service.
Download DomainAspects20.zip (2.10 mb)