I know, editing source code or css is really a mess but I strongly recommend to keep all project files in RedDot. If you change your publication target for example (from hoster A to hoster B) or create a new child project which depends on the content classes, all you need to do is publish the whole project, and you are done.
Especially in complex corporate projects, having multple souces of data can really be a mess: A config file gets overwritten, someone forgot to copy a file to somewhere, code changes where only performed on server A (e.g. live environment), not server B (DEV system), and so on. Even with a SCS system, this can easily happen (there is always that ONE guy who manages it to get past it *g*). Same is true if you are working with RedDot LiveServer: Of cause you can edit/develop the dynament code directly in the LiveServer repository, then something happens to the project (files get overwritten, corrupt database, a different code revision gets published, whatever) and you're really screwed. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/RedDot-CMS-Users?hl=en -~----------~----~----~----~------~----~------~--~---
