How do I check-in imported Source after I've made module changes?

Easy question as I am new to CSIDE after working with builder for ages. I've imported my source, made my changes and built the project. How to I properly "check-in" the source or otherwise clear out the srcmodule folders in my project so I can start something new? I've mistakenly just tried to delete the items before and I want a clean, fresh project space for the next module.

Thanks,

Bobby Brimm

Find more posts tagged with

Comments

Dave Carpeneto

Hi Bobby - On the "I want a clean, fresh project space for the next module" bit: a few options exists:

Your OScript project can have multiple modules contained in it (right click 'srcmodules' & select 'New' -> 'Module')
You can have multiple OScript projects in the Eclipse workspace (right click the 'OScript Explorer' panel & select 'New' -> 'OScript Project')
You can have multiple Eclipse Workspace (via 'File' -> 'Switch Workspace')

... option #3 would be a bit annoying if you're just wanting to disassociate a new module from prior work (switching workspace == Eclipse needing to be restarted), but I'll list it here for completeness :-)

Note that if you're looking to work with different Content Server installations in this case: option #3 is the one you would need to use (as CSIDE only allows one OTHOME per Eclipse workspace).

Bobby_Brimm

Thanks for your response! I guess I am a little spoiled by the way Visual Studio "checks in" code. I guess CSIDE/Eclipse doesn't really have a "clean-up" function when you're finished with your changes to a module. I guess it would be wise to zip up the old workspace and store it just in case there is something that I forgot to save ( weblingo files ).

Thanks again!

Bobby

John Simon

Bobby,

Agreed with "wise to zip...". I'm not sure you can ever get back to the source if you don't keep it. Sure you can import it again but will you end up with the same source? We have had TONS of problems importing source code (but to be fair we only import from previous versions, not sure we have tried with a brand new module). Also we use option 2 mentioned above so we can treat each module as it's own GIT (and GitHub) repository. Just our approach...

Cheers...