DotNetInvoice Forums

Well I'm one step closer to gettin my e-commerce site up and running.  I purchased your software a couple of days ago and set up a merchant account/gateway with Authorize.NET.  I started to nose through your application and have a few questions.

1.)  My site is going to be subscription based.  After signup a member will automatically be charged each month until they cancel.
      Are there code samples within your application that would show me how to create a generic invoice, after a member joins
     attach that invoice to their account through code and then charge that cc each month?  I was hoping for  more documentation
     on your app and how to handle different scenarios.  If there are such samples, can you point them out.

2.) Am I supposed to drop the whole DotNetInvoice folder inside of my web application folder?  Or combine them (add class files in
     your app_code to my root app app_code folder and so on)

3.) I have database all configured with tables and procedures.  Can I run the Install.sql against that existing database?  Will it conflict with
     what I have already setup in there.  It already has the default membership tables set up among other things.

Hi Mark,

1. We are currently working on implementing an API for easy developer integration, but for now the best approach is to look at /admin/invoices/edit.aspx.vb in the cmd_save_Click() method for the code that creates and updates an invoice. I've also attached a couple code snippets to this email that show how to create an invoice and how to create a recurring invoice. I apologize for the rawness of these code samples - we are currently working on improving this aspect of our product.

2. You can do either, but I would recommend keeping them separate. As long as you make the DotNetInvoice folder an IIS web application you should be fine.

3. You can run the install.sql against an existing database with Membership tables inside of it - we have done this with at least 10 databases and not run into any issues. However, please back up your database before doing so.