flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Tynjala <joshtynj...@gmail.com>
Subject Re: SWF Debugging in Visual Studio Code
Date Mon, 20 Mar 2017 15:50:29 GMT
Version 0.3.0 of asconfigc was still perfectly capable of compiling an
application. That version just doesn't have some of the new features in
0.4.0, like copying asset files to your output folder or populating an AIR
application descriptor's content field.

I should also point out that the fact that asconfigc's and the VSCode
extension's version numbers are both 0.4.0 is a coincidence. They are
separate projects and their version numbers are not required to match in
order to work.

I see from your screenshot that NPM is indeed installing 0.3.0, for some
reason. I don't know why it would do that when there's a new version. Maybe
you can try the following command to force it to install the correct

npm install -g asconfigc@0.4.0

- Josh

On Mon, Mar 20, 2017 at 8:26 AM, OK <post@olafkrueger.net> wrote:

> Forgot to mention:
> The example is working after fixing the typo.... but using version 0.3.0?!
> Olaf
> --
> View this message in context: http://apache-flex-users.
> 2333346.n4.nabble.com/SWF-Debugging-in-Visual-Studio-
> Code-tp14853p14897.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message