When I was an independent consultant, doing ASP, I really had no choice.
However, it was my philosophy that since I was hired to write it, ostensibly
my programming skills were better than my clients. I did make sure that I
had a contract which specified that I was the owner of the copyright.
However, I would also specify that the client was licensed to make any
changes they deemed fit, and to use the code for any purposes they deemed
fit, with the condition that support for my code ended when they touched it.
Some would continue to use me, and paid for additional work. Some took over,
and I ended up doing paid work for them to fix up THEIR code. In any case,
everyone was happy.
Now that I am not an independent consultant, of course, I don't have to
worry about this. However, the fact that ASP.Net can be compiled into a DLL
would probably lead me to NOT share my source code with the client.
--
Kevin Spencer
Microsoft MVP
..Net Developer
Ambiguity has a certain quality to it.
"Sergio Fernandez" <> wrote in message
news:h28ne.271596$...
> I've always given clients the source code.
> They paid for it, they should have access to it.
>
> Sergio Fernandez
>
>
> "VB Programmer" <> wrote in message
> news:...
>> Typically, when you are done with a client's website, do you give them
>> all
>> of the source code, if they ask for it? Do you, as the developer,
>> legally
>> own it, or do they, because they paid you to create the ASP.NET website?
> (I
>> live in Florida)
>>
>> Thanks...
>>
>>
>
>
|