Group development and source code control

TeeChart for Microsoft Visual Studio .NET, Xamarin Studio (Android, iOS & Forms) & Monodevelop.
Post Reply
glitch
Newbie
Newbie
Posts: 11
Joined: Fri Nov 02, 2007 12:00 am

Group development and source code control

Post by glitch » Wed Mar 19, 2008 9:05 pm

Hi,
I work in a group and my code is checked into source control. Each developer needs to rebuild the project, although, I am the only one to develop using TeeCharts. Reading through the EULA, tutorial (17), and other posts, I'm unclear what exactly needs to be included in source control (TeeChart.dll & licenses.licx?) and whether the other developers can build without a license(?) -- my attempts to simulate this have been unsuccessful. In another post (http://www.teechart.net/support/viewtopic.php?t=7472) a reference is made to a "license installer" on the client download page but I didn't see it there (I'll need it for the build machine, in any case). Please could you point me to the license installer (another name? the binary installer?), let me know what can be checked into source control, and what other developers on this project need so as to compile this project.
Thanks

Marc
Site Admin
Site Admin
Posts: 935
Joined: Thu Oct 16, 2003 4:00 am
Location: Girona
Contact:

Post by Marc » Tue Mar 25, 2008 11:29 am

Hello,

The license installer is available via the customer download page at:

http://www.steema.com/downloads/client_access.html

Look for the 'TeeRegister' tool on the page.

The TeeRegister tool installs the physical machine license to permit compile of TeeChart on the machine concerned. It is intended for groupwork environments where a build machine exists (no modification to code accessing TeeChart). If each developer compiles all the code, thus requiring the presence of the TeeChart machine-key then it would be realistic to permit key installation in those machines to facilitate the smooth running of the development process - always provided that only TeeChart licensed developers modify any TeeChart relevant code. Steema favours the use of a designated build machine and would ask the avoidance of the proliferation of key installs beyond the absolute minimum required. We are studying options to better manage physical licensing to avoid ambiguity in this type of group-work scenario in the future.

Regards,
Marc Meumann
Steema Support

glitch
Newbie
Newbie
Posts: 11
Joined: Fri Nov 02, 2007 12:00 am

Post by glitch » Wed Mar 26, 2008 10:09 pm

Thank you, Marc. That took care of the problem for the build machine and the other developers on the project. Thanks.

Post Reply