It sounds like asconfigc may have been defaulting to your FLEX_HOME environment variable when compiling the project. If you're not careful, the value that you set for FLEX_HOME isn't necessarily the same as the value that you set for the nextgenas.sdk.editor setting in VSCode.
There are two good ways to avoid this conflict: 1) Let both asconfigc and VSCode fall back to the FLEX_HOME environment variable. Don't set the --flexHome option for asconfigc and don't set the nextgenas.sdk.editor setting in VSCode. Both will default to FLEX_HOME, if it's set to a valid SDK. 2) Set the --flexHome option for asconfigc to the same value as the nextgenas.sdk.editor setting. Basically, either let both tools automatically detect the SDK from FLEX_HOME or explicitly set the SDK in both tools. - Josh On Wed, May 3, 2017 at 12:41 PM, PKumar <[email protected]> wrote: > Josh, > > This issue has been resolved via setting same SDK for editor & FLEX_HOME. > Big Thanks. > > Regards, > Prashant > > > > ----- > Regards, > Prashant > -- > View this message in context: http://apache-flex-users. > 2333346.n4.nabble.com/FlexJS-js-Table-Issue-tp15145p15161.html > Sent from the Apache Flex Users mailing list archive at Nabble.com. >
