Authorize.net

[shutter]

Can someone tell me if discountasp.net supports CCTranman from Macrobright? I have purchased this component and want to use it with my authorize.net account.

[bruce]

I did some research on the Net and could find out whether CCTranman is a COM or .NET object. Post the installation instruction here if you want me to confirm.

We cannot support COM component but can support .NET component that do not require server registration.

[b]quote:Originally posted by shutter

Can someone tell me if discountasp.net supports CCTranman from Macrobright? I have purchased this component and want to use it with my authorize.net account.
</blockquote id="quote"></font id="quote">

[bruce]

BTW,

if you using .NET, there's a component installed on our server that handles CC transaction (supports AuthNet)

See http://kb.discountasp.net/article.aspx?id=10103

[b]quote:Originally posted by bruce

I did some research on the Net and could find out whether CCTranman is a COM or .NET object. Post the installation instruction here if you want me to confirm.

We cannot support COM component but can support .NET component that do not require server registration.

[b]quote:Originally posted by shutter

Can someone tell me if discountasp.net supports CCTranman from Macrobright? I have purchased this component and want to use it with my authorize.net account.
</blockquote id="quote"></font id="quote">
</blockquote id="quote"></font id="quote">

[shutter]

I received an email from their tech guys:

Mr. XXX,

The installation package automatically puts it in the GAC in order to support COM clients as well as .NET clients. However, if you install it to your local machine for example, you can simply copy the dll to the bin directory of your .NET site. Therefore, there is no registration required on the server. As far as licensing, right now the licensing model is such that you only need one license per Authorize.net account. So it is fine to have a copy on both your development and production server. I hope this answers you questions. Please feel free to contact me directly in the future if you have any further questions.

Sincerely,
YYYY


So it appears we could use theirs via just the bin directory. But alas, they were too slow in responding, so I went with IPWorksCC as per the knowledgebase article, but now the problem I have is that the server does not recognize my reference. (Im refering to it via the GAC as another knowlegebase article advises for installed components). Ive opened a support ticked for this, hopefully will get an answer soon.

[bruce]

you know what.

Unlike other .net component we have, ipworks cc is not installed to the GAC. You'll need to upload the dll to the bin directory. The license key is already on the server.

[b]quote:Originally posted by shutter

I received an email from their tech guys:

Mr. XXX,

The installation package automatically puts it in the GAC in order to support COM clients as well as .NET clients. However, if you install it to your local machine for example, you can simply copy the dll to the bin directory of your .NET site. Therefore, there is no registration required on the server. As far as licensing, right now the licensing model is such that you only need one license per Authorize.net account. So it is fine to have a copy on both your development and production server. I hope this answers you questions. Please feel free to contact me directly in the future if you have any further questions.

Sincerely,
YYYY


So it appears we could use theirs via just the bin directory. But alas, they were too slow in responding, so I went with IPWorksCC as per the knowledgebase article, but now the problem I have is that the server does not recognize my reference. (Im refering to it via the GAC as another knowlegebase article advises for installed components). Ive opened a support ticked for this, hopefully will get an answer soon.
</blockquote id="quote"></font id="quote">

[pjoyce]

Just one person's opinion here, but why not just use the component you already have? It looks like you just have to stick it in the /bin directory and everything will work fine with your existing code. You've already paid for it, and if you find you need to upgrade later, you can always switch to the ipworks one then.

One major advantage is that because you have a licensed copy of it, you can run it on your development machine easily.

[b]quote:Originally posted by bruce

you know what.

Unlike other .net component we have, ipworks cc is not installed to the GAC. You'll need to upload the dll to the bin directory. The license key is already on the server.

[b]quote:Originally posted by shutter

I received an email from their tech guys:

Mr. XXX,

The installation package automatically puts it in the GAC in order to support COM clients as well as .NET clients. However, if you install it to your local machine for example, you can simply copy the dll to the bin directory of your .NET site. Therefore, there is no registration required on the server. As far as licensing, right now the licensing model is such that you only need one license per Authorize.net account. So it is fine to have a copy on both your development and production server. I hope this answers you questions. Please feel free to contact me directly in the future if you have any further questions.

Sincerely,
YYYY


So it appears we could use theirs via just the bin directory. But alas, they were too slow in responding, so I went with IPWorksCC as per the knowledgebase article, but now the problem I have is that the server does not recognize my reference. (Im refering to it via the GAC as another knowlegebase article advises for installed components). Ive opened a support ticked for this, hopefully will get an answer soon.
</blockquote id="quote"></font id="quote">
</blockquote id="quote"></font id="quote">