0
0

Can VB.NET be used with FMOD ?
I am a very newbie and am very impressed 😀 with the latest release of FMOD. However our project is in VB.NET .
Does anything currently exist ?
Has anyone already done it ?
If not would anyone else be interested on working on a VB.NET interface ?

Regards Chris

  • You must to post comments
0
0

I’m pretty sure you can use the C# interface

  • You must to post comments
0
0

i´m use C# and works fine. I´m sure that work in VB…

  • You must to post comments
0
0

Thanks for the feedback.
The C# code – which I am currently using includes 3 ( I think ) .CS files. I guess these will need to be converted to .vb before I can use VB.NET ?

Chris

  • You must to post comments
0
0

[quote="chris r":1h7if0hf]Thanks for the feedback.
The C# code – which I am currently using includes 3 ( I think ) .CS files. I guess these will need to be converted to .vb before I can use VB.NET ?

Chris[/quote:1h7if0hf]You can compile them and use the classes and namespaces from them in your VB.NET code.

  • You must to post comments
0
0

Thanks Brett – Thats good news. Regards Chris

  • You must to post comments
0
0

I think I have tried what you have suggested but have had problems. If I add a new C# project to the solution I am working with and add the .CS files ( eg fmod.cs, fmod_errors.cs, fmod_dsp.cs ) and then build that project as a Csharp class. I can then reference it in my VB project eg
add a refernce to this new project. Then I use IMPORTS FMOD. I can then appear to access all of the FMOD csharp functions etc. However When I try to execute
Dim system as FMOD.system
result = FMOD.Factory.System_create(system)
I get an error “unable to load dll ../../api/fmodex.dll.
When I try to manually add a reference to the dll is says it is not a valid COM component.

Thanks in advance if you can help.
P.S. I am trying to reproduce something similar to the multispeaker demo but in VB.NET

  • You must to post comments
0
0

DOH!
Just after I submitted the last message I realsied that it may have something to do with the location of the fmodex DLL …. and of course it did. So I changed the reference to the DLL and it worked !
Sorry if 😳 for an inconvienience caused.
Regards Chris

  • You must to post comments
Showing 7 results
Your Answer

Please first to submit.