Tweet
This caused me a day or two of pure headache and high blood pressure.
It's very difficult to take the project and convert it to visual studio .net and make it work in our build environment. It took all morning mucking with linker errors in some obscure mfc garbage to get it to link. But I got that solved.
The next thing that gave me a heart attack is the meat of this post. My plugin would not appear in the list after all that grief of getting my dll in the first place. After much trial and error, it appears that the instructions of where to place vms_desktop.dll are incorrect. It specifies that it has to go in the plugins directory but in reality, it goes in the root winamp directory.
Now I'm not sure if I set something up incorrectly or am unclear on something but I followed the directions to the letter... I am not pissed or anything because this project is light years better than the other sdks I was looking at using but I just wanted to hopefully help someone else who might be having the same problem I was.
It's very difficult to take the project and convert it to visual studio .net and make it work in our build environment. It took all morning mucking with linker errors in some obscure mfc garbage to get it to link. But I got that solved.
The next thing that gave me a heart attack is the meat of this post. My plugin would not appear in the list after all that grief of getting my dll in the first place. After much trial and error, it appears that the instructions of where to place vms_desktop.dll are incorrect. It specifies that it has to go in the plugins directory but in reality, it goes in the root winamp directory.
Now I'm not sure if I set something up incorrectly or am unclear on something but I followed the directions to the letter... I am not pissed or anything because this project is light years better than the other sdks I was looking at using but I just wanted to hopefully help someone else who might be having the same problem I was.
Comment