where to store sound file

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi, All,
The app retrieve sound.wav file from my loacal C drive, is there anyway the
sound file can be stored in the app? then when building, it goes with app
rather than sending sound file seperate with app when deploying the app.
Thanks
 
martin1 said:
The app retrieve sound.wav file from my loacal C drive, is there anyway
the
sound file can be stored in the app? then when building, it goes with app
rather than sending sound file seperate with app when deploying the app.
Click to expand...

In VB 2005 select "My Project" -> "Resources" and add the file as a
resource. In VB.NET 2002/2003 add the file to the project and set its
'Build Action' property to 'Embedded Resource' in the properties window.
 
when I go to solution explorer in VB NET 2005, then double click My Project,
it open and then click Resources in left menu and add resource, it add just
source name, it is not stored sound.wav file. Also go to application folder
in C drive and open My Project folder and cannot find Resources folder, need
manually add the resources folder? So my 2 questions is where to find
Resources Folder? and where to store sound file? Thanks
 
martin1 said:
when I go to solution explorer in VB NET 2005, then double click My
Project,
it open and then click Resources in left menu and add resource, it add
just
source name, it is not stored sound.wav file. Also go to application
folder
in C drive and open My Project folder and cannot find Resources folder,
need
manually add the resources folder?
Click to expand...

IIRC the resource is stored inside a ResX file.
 
Herfried said:
In VB 2005 select "My Project" -> "Resources" and add the file as a
resource. In VB.NET 2002/2003 add the file to the project and set its
'Build Action' property to 'Embedded Resource' in the properties
window.
Click to expand...

Just out of curiosity, are there any advantages to the VB2005 method you've
described above?

I'm using VB2005, but I still embed resources in the same way as you
describe for VB2002/2003. This works very nicely IMO, as I can structure the
resources into a directory hierarchy, check them in and out of SourceSafe
from within the Solution Explorer, and also include resources such as To Do
lists that I want to be able to access but which don't get compiled into my
project (by setting the Build Action to None).

It seems to me that the "new" way of doing this would lose all of these
features. Is there something else that I'm missing?

TIA,
 
In the by you described situation

it seems to me that you should better create a subdirectory in the
application path were you can put in the sound file
for deployment you can now create a setup ( installer )

advantage

Footprint of your app is smaller , easy to load , easier to extend


regards

Michel Posseth [MCP]
 
Thank you, Everyone.

The discussion answer my question.

Martin

Michel Posseth said:
In the by you described situation

it seems to me that you should better create a subdirectory in the
application path were you can put in the sound file
for deployment you can now create a setup ( installer )

advantage

Footprint of your app is smaller , easy to load , easier to extend


regards

Michel Posseth [MCP]


martin1 said:
Hi, All,
The app retrieve sound.wav file from my loacal C drive, is there anyway
the
sound file can be stored in the app? then when building, it goes with app
rather than sending sound file seperate with app when deploying the app.
Thanks
Click to expand...
Click to expand...
 
Back
Top