Visual Studio 2022

[Bahaa-Sobhy]

I installed Sharpamp, it extracted itself into C:\Program Files (x86)\Sharpamp directory,
but when I opened Visual Studio, there's no templates nor anything called General Winamp Plugin

So I went to the C:\Program Files (x86)\Sharpamp\samples directory and tried opening the solution in Microsoft Visual Studio Enterprise 2022 (64-bit) - Version 17.6.5

As expected - because the solution is made on an old version of vs, Visual Studio asked to convert the solution.

After converting the solution, this was the reports:

then in the solution explorer: the c++ wrapper gen_HelloWorldGUI failed to load:

After all, I built the HelloWorldGUI.dll file, copied and pasted it into the Winamp\plugins directory

I also copied it into the winamp\ direcroty:

Finally when I opened Winamp, the plugin is not listed at all.

More details:

Visual Studio version:

Winamp version:

Windows version:

Am I missing any point?

[akarapatakis]

Hello!

Regarding the Template issue, older vs versions would refresh and detect new templates at startup. In Visual Studio 2012, if i recall it correctly, it was changed, and you now need a command to do it.

But before you do that, you have to copy the template from MyDocuments\Visual Studio 2008\Templates\ProjectTemplates\Visual C# to MyDocuments\Visual Studio 2022\Templates\ProjectTemplates\Visual C#, and then open a visual studio terminal session (found in start menu) and type the following command devenv /updateconfiguration. This command is going to refresh and detect newly added templates.

Now, the reason that the player doesn't detect it, is because you haven't built gen_(YourPluginName), and to do that, Daniel has added a wiki page that can be found here https://github.com/Daniel15/Sharpamp/wiki/Getting-Started

P.S: I recommend checking out WACUP for an alternative as it is has a community with developers that can help you!
https://getwacup.com/

[Daniel15]

As @ChocolateAdventurouz mentioned, you need the gen_[PluginName].dll file too. This is a C++ library that forms a bridge between Winamp (which expects a C++-style DLL) and the C# code you're writing.

But before you do that, you have to copy the template from MyDocuments\Visual Studio 2008\Templates\ProjectTemplates\Visual C# to MyDocuments\Visual Studio 2022\Templates\ProjectTemplates\Visual C#, and then open a visual studio terminal session (found in start menu) and type the following command devenv /updateconfiguration. This command is going to refresh and detect newly added templates.

I should update the installer to do this 😄 You can see here that it only copies the template to Visual Studio 2005, 2008 and 2010: https://github.com/Daniel15/Sharpamp/blob/master/setup.iss#L41-L43. The code is literally 12 years old now so it may need modernization in other ways too.

[Bahaa-Sobhy]

Thank you so much @ChocolateAdventurouz and @Daniel15, I will try your instructions...

I should update the installer to do this 😄 You can see here that it only copies the template to Visual Studio 2005, 2008 and 2010: https://github.com/Daniel15/Sharpamp/blob/master/setup.iss#L41-L43. The code is literally 12 years old now so it may need modernization in other ways too.

Good idea Daniel, from the beginning I expected the installer to do it.

Aside from this - and as you said - the code is 12 years old now, are you planning to reconstruct it from scratch? or add everything a developer may need to deal with making new powerful plugins as if they were made totally in native C++?
what kind of plugins are you planning to make your wrapper able to do? for example DSP plugins that can stream or broadcast to servers? or sound effects plugins? etc...

generally thank you for making such useful library, go ahead... keep the good work!

[akarapatakis]

I had made a port of Sharpamp back in March. Not sure if i still have it though. I am going to check it right now!

[akarapatakis]

And I have it! I am going to push it for reservation purpouses. It is not a complete new build/version, but it seems i will build an unofficial version or something like that before school starts again! 😄

[akarapatakis]

https://github.com/ChocolateAdventurouz/Sharpamp <- it is not completed yet , and as i looked up the code a bit, you'd better stick with the 2009 version for now!

[akarapatakis]

@Bahaa-Sobhy

Aside from this - and as you said - the code is 12 years old now, are you planning to reconstruct it from scratch? or add everything a developer may need to deal with making new powerful plugins as if they were made totally in native C++?
what kind of plugins are you planning to make your wrapper able to do? for example DSP plugins that can stream or broadcast to servers? or sound effects plugins? etc...

Rewriting Sharpamp from scratch is not an easy task, especially when EnvDTE has decepretated lots of methods that Sharpamp used to have in order to function, but I have temporarily linked EnvDTE100 as a legacy alternative until the rewrite process starts. akarapatakis@97cf6e3

I had made an Media Library plugin wrapper which never worked, but I will check it out soon!

Thank you for reminding it.

[Bahaa-Sobhy]

@ChocolateAdventurouz

And I have it! I am going to push it for reservation purpouses. It is not a complete new build/version, but it seems i will build an unofficial version or something like that before school starts again! 😄

Great... 👏

https://github.com/ChocolateAdventurouz/Sharpamp <- it is not completed yet , and as i looked up the code a bit, you'd better stick with the 2009 version for now!

The point is that now I have Windows 11, using VS 2009 on it is not an option anymore, as lot of SDKs and features are missed. 😉

I had made an Media Library plugin wrapper which never worked, but I will check it out soon!

This is the permanent problem that meets developers of such plugins, media and codecs are changing on regular basis, so even if your Media Library plugin wrapper worked in past, it - most likely - won't work nowadays.

Thank you for reminding it.

You're welcome, go ahead.... and good luck! 👍

[akarapatakis]

@Daniel15 @Bahaa-Sobhy,

I am happy to announce that my fork seems to be now properly buildable on Visual Studio 2022! Some work is still needed to be done, but since the required solutions are compiling on .NET Framework 4.8.1 etc, i am more than happy!