materix
Posts: 161
|
| Posted: 03/29/2007, 9:43 AM |
|
An interesting question: Do any of you somehow "anonymize" the applications that you create with Codecharge Studio, so that the clients are not able to see that the source-code is originally built with CCS?
|
 |
 |
wkempees
|
| Posted: 03/29/2007, 2:30 PM |
|
To be honest, NO.
I even let my customers know exactly what we are using, which version and
even the price and the place where to buy.
I do not however cheaply sell the project files itself.
I do offer them to follow training, assist in further development and so on,
specifically application and database design which are almost never their
core bussiness.
It is my long term experience that this open approach is reveived as
professional and in fact
supports long term relationships.
Also it is good to know that if someone buys a fully equiped toolbox with
screwdrivers and wrenches and the likes
one can still not build or repair for instance a washing machine!
Walter
|
|
|
|
JimmyCrackedCorn
Posts: 583
|
| Posted: 03/29/2007, 8:44 PM |
|
Although we have not yet done it with CodeCharge projects, we use a variety of techniques, including obfuscation, on our delivered projects to protect our intellectual property.
And yes, we consider the tools we have invested in as well as our techniques to be intellectual property; we invest significant time and expense in evaluating, procuring, learning and customizing our tools. To freely give this experience away to customers is not something we typically choose to do! :)
Our philosophy is pretty basic. If you hire us to create something unique and original and you want all source code, tools, etc. then you pay a much higher price because we may not be able to benefit from reselling/reusing that product.
On the other hand, the vast majority of our customers have no interest in the back-end and are only interested in the delivered, working solution so they only pay for use of the system rather than full ownership. They get the system they want and need, at a cost they can afford.
The only issue that has come up is corporate customers who want protection of their investment in case our company goes out of business. For these customers we offer to place source code, tools, etc. in an escrow account that is only accessible in the event of our demise. That way the company knows they can always get service with or without us.
_________________
Walter Kempees...you are dearly missed. |
|
|
|
Edd
Posts: 547
|
| Posted: 04/01/2007, 5:09 PM |
|
You can compile ASP / PHP and ASP.Net apps into .EXEs
See
http://www.octopod.net/products/ActiveSiteCompiler/overview.asp
_________________
Accepting and instigating change are life's challenges.
http://www.syntech.com.au |
|
|
|
JimmyCrackedCorn
Posts: 583
|
| Posted: 04/02/2007, 3:23 AM |
|
for ASP.NET you can compile with VS2005 (and probably Visual Web Developer Express Edition as well). BUT, if you do not obfuscate first, your code can be easily decompiled and read.
_________________
Walter Kempees...you are dearly missed. |
|
|
|
Wkempees
|
| Posted: 04/02/2007, 7:31 AM |
|
Shorter answer:
Yes you can by identifying which actual statements you think can
identify the use of CCS.
For instance META generated with CodeCharge Studio......
You can remove that line without any pain to the application.
You can define your own META Tags.
Further identification can be by styles and style names, you can define
your own.
The (in my case) PhP code generated follows a pattern and uses functions
like CCGetFromGet(), you can NOT change those easily, I would not even
recommend it.
The other answers are valid too, but targeted at encryption and code
encryption.
You make out for yourself if it is the one or the other you are addressing.
Walter
|
|
|
|
Wkempees
|
| Posted: 04/02/2007, 12:45 PM |
|
Shorter answer:
Yes you can by identifying which actual statements you think can
identify the use of CCS.
For instance META generated with CodeCharge Studio......
You can remove that line without any pain to the application.
You can define your own META Tags.
Further identification can be by styles and style names, you can define
your own.
The (in my case) PhP code generated follows a pattern and uses functions
like CCGetFromGet(), you can NOT change those easily, I would not even
recommend it.
The other answers are valid too, but targeted at encryption and code
encryption.
You make out for yourself if it is the one or the other you are addressing.
Walter
|
|
|
|
Benjamin Krajmalnik
|
| Posted: 04/02/2007, 1:32 PM |
|
Well,
I guess it all depends how you value customer relations.
If I am engaged for a custom project, the owner owns the source code. I may
use the work in derived works, but he stil owns the source code.
That way, if I were to go our t of business, or decide to pursue other
avenues, my customer is not screwed.
In some cases this can be done by placing the code in escrow.
Now, this is different when it comes to our commercial products, where they
get a bargain price vis-a-vis the hours invested to develop.
|
|
|
|
JimmyCrackedCorn
Posts: 583
|
| Posted: 04/02/2007, 5:13 PM |
|
Quote Benjamin Krajmalnik:If I am engaged for a custom project, the owner owns the source code. I may use the work in derived works, but he stil owns the source code.
You have to be careful in this case though because if you transfer full ownership to him you cannot use any part of the work unless he grants you a license. In these situations we are always careful to clearly define in the contract which portions he owns and which portions we are licensing to him for his use. That way we can use our libraries in a project without losing rights to them.
_________________
Walter Kempees...you are dearly missed. |
|
|
|
|
