0

I want to create a new shipping module (FedEx) for the built-in Store module in DotNetNuke 6. I have created simple C# class project and can make reference to the Shipping namespace and can start implementing my own provider. But is this is best way to do this? Would I be better off creating a module? I think the latter because I will be creating a small control to configure the provider.

Once I am done, how do I get the Store to see the provider and use it in the store provider drop-down list? I have seen examples on the web about creating a brand-new module. I'm creating a new one too, but I am inheriting the Shipping class and want to essentially create a subclass (Shipping.FedExShippingProvider) where is currently only Shipping.DefaultShippingProvider.

Thanks!

sshirley
  • 239
  • 2
  • 6
  • 19
  • I haven't been keeping up with the core store module. I always use a 3rd party component (dnnspot.com) - But as an aside, to make your life easier you may want to take a look at http://www.nsoftware.com/ .NET fedex library. Might cut down on the custom code you have to write. – Ryan Doom Sep 14 '11 at 23:41

1 Answers1

0

To answer your question - all DNN components should now be built as Extensions, packaged and installed using a DNN Manifest file.

A 'module' (really, extension) these days doesn't have to include any UI code. You can just bundle in the DLL and maybe some SQL scripts if that's what you need.

As for how to load the provider, you need to add in a provider entry and definition in your web.config file. This is the best way to do it. You can then use the in-built provider loading calls to load your provider when it is needed, although I've never worked with the store module so I don't know if this is easily achieved or not. There should be examples around that you can copy from.

As for creating the entries in your web.config, you can do this with your DNN manifest file as well.

Brock Adams
  • 90,639
  • 22
  • 233
  • 295
Bruce Chapman
  • 1,227
  • 3
  • 12
  • 19