Hi,

I am fairly new to DotNetNuke and could do with some guidance. I have been tasked with extending DotNetNukes functionality for a client who has a specific requirement to use .Net remoting for data access. They wish to have the DotNetNuke database deployed onto its own server and communication for resources should occur over HTTP using binary serialization.

In order to achieve this goal I had planned on doing something along the following lines:

1) Create a class library to act as the remote server instance (hosted within IIS). Within this library there would be an interface to be exposed to the client application, that would closely match the abstract method implementation within the base DataProvider class. There would also be a class that implements this interface and actually performs the data access functions using the enterprise library.

2) Create a new data provider project within DotNetNuke (RemotingDataProvider), that implements the same functions as the SqlDataProvider, except for whenever access is required to the database, remoting is used to generate a proxy and call the various functions exposed by the interface.

Due to the sheer size and number of functions within the SqlDataProvider class, it could take me a rather long time to implement such a mechanism and I am sure there would be a number of headaches along the way. Plus testing of such changes would be difficult as in order to test effectiviely you would want to test all the method calls within the class.

Due to the timescales on this project, going down this route does not seem like a viable option, so I was hoping someone might be able to offer a simpler solution to the problem, or be able to point me at resources where this has been done before within the community?

Any help would be greatly appreciated...