S
Steve Croff
Guest
We store source only, none of the project settings, but we are very small, not many developers and we let them manage the environments. Another factor, is that we support multiple versions of OE (10.2B and 11.6) This has caused some source control challenges. The source itself has pre-processors to handle the code parts, so we do not have separate trunks by OE version. However, the .assemblies varies between OE version, so that is an example of a file that is not versioned in source control. We do store .resx and .wrx, in source control, but recently found we have .resx problems if a UI is modified in 11.6 then built with 10.2B. No compile errors, but at runtime, you have some problems loading the .resx data. For this reason, we have an informal rule to only modify UI with 10.2B, not 11.6. There might be a better way to handle this?
Continue reading...
Continue reading...