How do I work with a Flash project in Visual Basic.NET?

Question

1.00/5 (1 vote)

See more:

I have a flash SWF file that I would like to include in my Visual Studio (VB.NET) project. I've already looked up how to include the actual OCX and that is working fine but nothing is said on how to exactly include the SWF and manipulate the SWF from within VB.NET. For example, I want to be able to press a button on a VB.NET WinForm and send a command/data to that SWF to run a function within that SWF's ActionScript. (Example I push a button in VB.NET, I want the VB.NET code to send to the SWF a word and pass that word to a function within the Flash player.)

People are recommending "SendKeys" or to use XML, etc but not much is being said as to what specific coding is needed to do such a thing.

Posted 19-Nov-15 0:24am

thedonedeal

Add a Solution

Comments

Sergey Alexandrovich Kryukov 19-Nov-15 12:06pm

SendKeys would be the worst thing, and "use XML" means just nothing certain. I would do my best to get rid of SWF. Even though ActionScript is a nice, decent language, all this stuff is proprietary; software world works hard to phase it out altogether. If you manage not to mess with it at all, it would give you a way to fill your life with something which has some prospects. As to the useful functionality you may have in Flash, it can be implemented in many other ways.
—SA

thedonedeal 20-Nov-15 6:44am

I guess to WPF it is then. I was hoping on avoiding using it since it's still new to me but eh.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)