Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: components installation (Read 1646 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

components installation

Hi

What happens when you download a .fb2k-component file and install into foobar?
Does this file contain the DLL or is the component file the same as the DLL and is the file extension from the component renamed to DLL and the copied  to the folder?

thx
Foobar2000 - It Really Whips ALL Llamas' Ass!

Re: components installation

Reply #1 –
The  .fb2k-component file is just a zip archive with a different extension, which will be extracted to a folder with the name of the file inside of the user-components folder during the installation.

Re: components installation

Reply #2 –
So the extension .fb2k-component is assigned to foobar2000 in windows, so when you double click it , windows runs foobar2000 and foobar2000 unzips it to the correct folder?
Do I understand it correctly?
Foobar2000 - It Really Whips ALL Llamas' Ass!

Re: components installation

Reply #3 –
I also had 2 additional questions about components:

- is there a way to see by looking inside the component zip file which is the minimum foobar2000 required version or can we only see this by looking at the information the developer tells? So can this be seen by looking somewhere in the component downloaded file?

- I'm saving some components I find on the forum here (that are not on the components page) because I like them but worried they maybe go offline some day.
Is it possible a component suddenly won't work anymore in an updated version of foobar2000 when the developer does not update it to latest SDK of foobar2000?
Or will a component keep working no matter what SDK version is currently used in latest foobar2000? (even if the component is not updated for years)

thx
Foobar2000 - It Really Whips ALL Llamas' Ass!

Re: components installation

Reply #4 –
Quote from: jessicaj on
So the extension .fb2k-component is assigned to foobar2000 in windows, so when you double click it , windows runs foobar2000 and foobar2000 unzips it to the correct folder?
Do I understand it correctly?
Yes

Quote from: jessicaj on
- is there a way to see by looking inside the component zip file which is the minimum foobar2000 required version or can we only see this by looking at the information the developer tells? So can this be seen by looking somewhere in the component downloaded file?
Yes. Extract foover.exe and shared.dll from the installer and call foover.exe with full path to component dll you want to examine. Returned errorlevel tells the used API version. You can study SDK to find out which version corresponds to which foobar2000 release.

Quote from: jessicaj on
- I'm saving some components I find on the forum here (that are not on the components page) because I like them but worried they maybe go offline some day.
Is it possible a component suddenly won't work anymore in an updated version of foobar2000 when the developer does not update it to latest SDK of foobar2000?
Yes, if Peter breaks compatibility. Last time it happened was between foobar2000 v0.8 and v0.9.