Best practice to split a project
Best practice to split a project
I have a large parent project and would like to take a LOT of topics, snippets, etc. and make them their own project (not linked at all to the parent project). I don't think I want to use the import feature to create the new project because of the links. I can probably create a duplicate project then remove all the unwanted topics, etc., but I am sure there is an easier way. Any suggestions before I create a mess that I have to clean up? I am using Flare 11 - I have Flare 12, but due to the issue with equations, I have to remain on ver11.
=============================
I will finish what I sta
=============================
I will finish what I sta
=============================
Re: Best practice to split a project
What "easier way" had you hoped for?
There's a few approaches, here's two:
(A) If it's easier to delete what you don't need, then just duplicate the project and start cutting it down. If the project was in source control, then make sure that you unbind the copy of the project, so that it's not bound to source control.
(B) If it's easier to choose what to keep, then mark all files you want to keep with a condition. Then create a new project, and set up a project import to import only files with that condition. To set up this import:
- Include files: All files (*.*)
- Set Import Conditions to Include your condition (e.g. include[Your.Condition]).
- Select Auto-Exclude Non-Tagged files (i.e. don't import files that don't have this condition).
Once your happy that the import works, you can remove it if you want. You can use this method to make multiple projects like this, and also to re-import updated files from the original project.
There's a few approaches, here's two:
(A) If it's easier to delete what you don't need, then just duplicate the project and start cutting it down. If the project was in source control, then make sure that you unbind the copy of the project, so that it's not bound to source control.
(B) If it's easier to choose what to keep, then mark all files you want to keep with a condition. Then create a new project, and set up a project import to import only files with that condition. To set up this import:
- Include files: All files (*.*)
- Set Import Conditions to Include your condition (e.g. include[Your.Condition]).
- Select Auto-Exclude Non-Tagged files (i.e. don't import files that don't have this condition).
Once your happy that the import works, you can remove it if you want. You can use this method to make multiple projects like this, and also to re-import updated files from the original project.
Re: Best practice to split a project
Thank you, Dave. I was just 'hoping' for a solution with less work 
I would rather ask to see if there was a simpler solution, rather than go about it the hard way and later find out there was an easier way..... Oh well, I guesss I know what I'll be doing today....
I would rather ask to see if there was a simpler solution, rather than go about it the hard way and later find out there was an easier way..... Oh well, I guesss I know what I'll be doing today....=============================
I will finish what I sta
=============================
I will finish what I sta
=============================