What is involved in deploying a vb.net 2003 application with the Microsoft Media Player component What files must be part of the build
thanks,
Fred
Deploying Windows Media Player
Hot Topic
- making an api call error 126 (findWindow)
- Real Time Data Monitoring
- mpeg streaming
- Equivalent for a \n new line character in Visual Basic
- DataSource desapeard
- Question about setting bits.
- ssh connection to a telecomSwitch (like telnet <ip> ...)
- Convert each record in an ArrayList to an array of strings
- version conflict adding interop reference to VB.NET project - I have almost the same probem guys
- VisualBasic6
Visual Basic
- opening a text file
- Could not read state file
- Simple question on variables.
- checking properties of folders
- Split a read-in string into more variables or read individual characters
- Debug or Release Problem
- Problem with VB6 SQL Server Express and Stored Procedures
- Problems Adding Fields to DVDs Table in MovieCollection Template
- ** Integration With Excel Via ...**
- Upgrading Studio 2003 to 2005
Deploying Windows Media Player
sunnydhiman
Some of the references I am checking are refering to AXMicrosoft.MediaPlayer.Interop, what is this
Fred
daking
I'm not sure it's a wise idea to start distributing components from Windows Media Player, for a couple of reasons:
1. I'm pretty sure you aren't allowed to.
2. What happens if an older version (or newer!) is installed and you blast away one of the components required for media player to run properly
3. If you don't blast it away, what happens to your program if a newer version is installed (say, version 15)
I would recommend having Windows Media Player a prerequisite for your application.
Vibhore
Under COM in your references:
Windir/System32/wmp.dll
This can be added to your tool box as a normal contro,if your like via Tools|Choose Toolbox items|Com| Windows Media Player
If you are serious about programming this, I recommend that you read the documentation on mcisendstring.
Good Luck
SwissToni
Vb6 worked on a COM model the Component Object Model. This was unmanaged code and was also machine specific. But the com model was really a specification describing an interface not designed for multiple platforms. Objects run in windows environment and interop is an interface that allows you to execute and talk to these objects.