Migrate from v1

FlexCompiler has been rewritten from v2, due to its incompatibility with v1, you'll need to remove the v1 package prior to importing the v2 one.

Since version 2, FlexCompiler is located within the "Packages" folder instead of "Assets" for a more streamlined management process.

To convert your legacy project from v1:

1. Delete the Assets/FlexCompiler folder.

2. Import the v2 package.

3. Open FlexCompiler project window, switch to the Extensions tab. Ensure that Legacy Project Importer is checked under Editor Extensions. This allows you to import legacy projects (in binary format).

   

4. Switch back to the Sources tab, click on Import Project and choose your legacy project with ".fpj" file extension. You'll see a warning dialog. Click "Continue" to proceed.

   

5. Resolve any missing scripts in the Sources tab. Switch to the Options tab and based on your legacy project settings, you may see something similar:

   

6. If there are no user defined symbols in the previous editor, uncheck Custom Symbols to allow FlexCompiler to resolve symbols automatically. The same applies to Custom References (if no external DLLs were manually referenced in v1 editor).

7. Note that legacy obfuscation does not offer you a full option and if obfuscation was enabled in the legacy editor, the imported project will use a basic obfuscation setting. You may modify it to suit your needs.

8. Ensure Sources, Options and Extensions are all well-set before exporting the imported project to new project format. Unlike the legacy project file which is in binary format, the new project file (with ".fcxml" extension) is XML-based allowing you to modify without opening the editor window.

9. If your old projects target mcs/gmcs/csc compilers with custom compiler arguments, they won't be automatically converted. You'll have to resolve them manually in options. Some advanced and rare arguments may require writing a custom extension. Refer to Options and Extensions for more details.