It looks like an IP license is the way for me as a website designer and webspace reseller.  All uploaded websites have the same IP address. (BTW, I find the licensing wording and structure confusing across products and within products.) 

 

Question 1:  if I get the IP license will I be able to configure the "editable-only" regions differently for each client's website?  Basically, I'm asking if the IP license allows me to configure each client website uniquely? 

 

Question #2: if my web hoster supports both ASP 'classic' and .NET, can someone tell me why I should pay the extra licensing cost to go .NET 4.0?  My reselling business would be calssified as a 'small business owner.'

 

Question #3: if I start with ASP 3.0, would there be a problem upgrading to .NET 4.0?  If no problem, what would be the cost to upgrade?

dklauk,

Question:

Question 1:  if I get the IP license will I be able to configure the "editable-only" regions differently for each client's website?  Basically, I'm asking if the IP license allows me to configure each client website uniquely? 

 

 

Yes. Each site should have uniques setting.

For your ASP.NET applications, you need to choose the CuteEditor for ASP.NET.

For the regular ASP applications. you should choose the CuteEditor for Classic ASP.


Question: 

Question #3: if I start with ASP 3.0, would there be a problem upgrading to .NET 4.0?  If no problem, what would be the cost to upgrade?

You can't upgrade ASP version to .NET version. You need to purchase the .NET version separately.

 

I think I'm beginning to understand the various licenses v. the various products. 

When I finally do buy the ASP Server license, will I be adding some HTML lines of code into a page (index.htm?) of each of the client websites or will CuteEditor be a separate asp appl. with a link to it from a browser?  I am trying to get a feel for how I would configure for on/off editing features/client website before I give them editing access?

dklauk,

 

First you need to make sure your server meet the requirements.

 

For Cute Editor for ASP:

 

Ability to execute ASP scripts

 

 

Cute Editor is a text area replacement. For Cute Editor ASP version, you can't embed it into the static html file. You have to use it in your ASP pages.

You need to have the ASP knowledge to install and deploy the CuteEditor for ASP.

 

Hope it helps.

 

Let me know if you have any further questions.

 

 

Currently, I have the Open Source HTML Editor working in an asp page that uses a SQL server db to save and retrieve content with HTML tags.  I give each client their own link to the asp page that then gives a list of editble pages from within their own website.  This works okay, but the Open Source Editor is pretty basic and I don't have the resources to add all of the features your product has.  Also, Open source Editor is not fully tested, so support is an issue for my clients.

How much effort would there be for me to replace the Open Source HTML references in the asp page to point to CuteEditorASP's editor?  Or, will I not be able to use a SQLServer db with CuteEditorASP?

I now there is a lot of info that is not included in this scenario, but maybe you can give me a feel for what I should be considering before I buy.

Thanks.

dklauk,

 

If you've already use the html editor in your code, you can easily replace it with Cute Editor.