Hello Empi,
Didn quite understand u.
Why not to create the custom setup where you set all necessary actions?
---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
E> Hi,
E>
E> I have a project on which I must do some different definitions for
E> each client the installs it (how many channels etc) and lock it from
E> him.
E>
E> What is the best way you recommend?
E>
E> Till current version, I used to send the clients a "signed" ini file
E> with
E> the information and a checksum I created to detect
E> changes in the file.
E> I'm sure there are much better ways of doing it today.
E> Is there any way of doing it as a part of the setup, instead of
E> sending a
E> text file to my client?
E> (whithout rebulding the setup package each time)?
E> Thanks.
E>
Empi - 30 Sep 2007 08:28 GMT
Because it must be set before deploying to the customer.
<Michael Nemtsev>; "MVP" <nemtsev@msn.com> wrote in message
news:3d9fba1a7aeb8c9cdcde04eb670@msnews.microsoft.com...
> Hello Empi,
>
[quoted text clipped - 23 lines]
> E> Thanks.
> E>
Empi - 30 Sep 2007 09:38 GMT
It must be configured for the installing customer, and not by him.
<Michael Nemtsev>; "MVP" <nemtsev@msn.com> wrote in message
news:3d9fba1a7aeb8c9cdcde04eb670@msnews.microsoft.com...
> Hello Empi,
>
[quoted text clipped - 23 lines]
> E> Thanks.
> E>