I'm considering a plug-in. Need facts, please.

[Blackbeard]

I'd like to look into coding a plug-in, so I kinda need pointers to the stuff I need. I've browsed this part of the forum, but probably missed some stuff. So if someone can provide a short list here, I'd appreciate it.

I've used Visual Studio before, but usually stick with the old VS 6.0 for production stuff. I've used one of the free versions that MS provides at work on my newer XP work computer and tried .NET also. I use a computer running Win 2K here at home, so is this compatible with anything MS offers and is the stripped down free versions of VS OK?

I've found a few links to source for a few plug-ins, but can anyone recommend their views on what might be their favorite link to a good tutorial for Vixen plug-ins?

Is C# necessary, or can C++ be used?

That should do for a starter. Thanks for any help.

steve

[dirknerkle]

Here's a link to the Wiki section about Vixen -- plenty of links there to find all the info you seek.

http://christmasinshirley.com/wiki/index.php?title=Vixen

[djulien]

Is C# necessary, or can C++ be used?

I didn't see this explicitly stated in the wiki, but you can use any language that can call the .NET CLR. C# or VB.NET are probably the easiest or most natural choices since they are tied fairly tightly to .NET. You probably could use C++, but there will be some extra "housekeeping" overhead that you would need to do (or write a thin "wrapper" layer to hide that stuff).

To get sample source code, disassemble an existing plug-in that somewhat resembles what you want to do. RedGate .NET Reflector is a good tool for doing the disassembly, and it will let you choose C# or VB.NET.

don

[JonathonReinhart]

Here's a page with links to my Vixen output plugins. Source is available for one or two of them.

http://lights.onthefive.com/vixen-plugins

They're written in C# which is pretty much the de-facto standard for .NET. If you can do C++, you can do C#.

Feel free to post back with any questions you may have.

[Blackbeard]

Thanks all.

steve

[LabRat]

I've inserted my own personal addendum to Jonathon's statement.


If you can do C++, AND you know how to curse like a sailor on shore leave, then you can do C#.

[Blackbeard]

I didn't see this explicitly stated in the wiki, but you can use any language that can call the .NET CLR. C# or VB.NET are probably the easiest or most natural choices since they are tied fairly tightly to .NET. You probably could use C++, but there will be some extra "housekeeping" overhead that you would need to do (or write a thin "wrapper" layer to hide that stuff).

To get sample source code, disassemble an existing plug-in that somewhat resembles what you want to do. RedGate .NET Reflector is a good tool for doing the disassembly, and it will let you choose C# or VB.NET.

don

I have VS 2005 Express installed, and I don't believe any Express version allows add-ins, so Redgate .Net Reflector is probably a no-go.

steve

[djulien]

I have VS 2005 Express installed, and I don't believe any Express version allows add-ins, so Redgate .Net Reflector is probably a no-go.

I use .NETReflector as a stand-alone tool - drag and drop a Vixen plug-in DLL onto it, then select the Disassemble menu item, then copy and paste the parts of source code I want into a window in the IDE (I've been using #develop but any .NET-capable IDE would work), then edit and compile as needed.

don

[Blackbeard]

I use .NETReflector as a stand-alone tool - drag and drop a Vixen plug-in DLL onto it, then select the Disassemble menu item, then copy and paste the parts of source code I want into a window in the IDE (I've been using #develop but any .NET-capable IDE would work), then edit and compile as needed.

don

Thanks djulien,

Tried that and it works (at least it didn't fail when I used one of your plug-ins). Now to see if I can understand what I'm seeing.

steve

[A Marchini]

Try this thread http://doityourselfchristmas.com/forums/showthread.php?t=6798 There should still be some useful info there and there are two walk through docs in .pdf for setting up a plug in.

Tony M.