Hi, I am not sure where to post a question like this on these forums, so if anyone can point me in a better direction, please do so!

I have created a custom DNN module that processes credit card payments for our website. To accomplish this, the module interacts with a remote web service that I have not created, nor do I control. I am just adding a reference to the web service, and calling one function from it. The custom module is working great, and is ready to package and roll out to the live server, but I am not sure how to go about adding the reference to the web service on the live server once the module is packaged and deployed.

When I package the module, I see a list of the files that it writes to the zip file, and none of them correspond to the web service. The only thing I can possibly think of is to recompile a new version of DNN that includes the web service built into it, but there must be a better way.

Does anyone have experience with this sort of thing?

Ask in the ExtendIt forums at DotNetNuke.com.

Now, I assume that you have developed this module using a DotNetNuke installation on a local computer. You could start by looking in all of the "usual" places for items related to the web service. This would include "resources" folders, the bin directory and web.config. You can build appropriate changes into your installation package for all of those, but the ExtendIt is probably a better place to go into all of those details.