UPDATE(June 12, 2011): Added installation location description for MAC.
UPDATE(June 11, 2011): Added FAQ and one question/answer at the end of post.
UPDATE(May 11, 2011): Some last minute errors sneaked in template settings so MonoDevelop didn't load addin. Fixed version (0.81) is at new download link.
As the title says, here are some file templates for Unity, written in C#. It is initial version, I'm new to Unity and I didn't use all functions in practice, so this is some kind of... newbie template set :) If you have suggestions on how to improve them, or better yet you make some useful templates, feel free to share.
To install templates, extract package to "\MonoDevelop\Addins" folder and restart MonoDevelop (if it is already running).
To install templates, extract templates package and copy extracted folder to "Contents\MacOS\lib\monodevelop\AddIns" in MonoDevelop application package. Restart MonoDevelop (if it is already running).
To check if templates successfully loaded, go to New File dialog:
Here you should have few templates under QQ\Unity\C#:
If for some reason addin didn't successfully load on startup, go to Add-in Manager:
And try to Disable and Enable add-in, forcing it to reload:
Download here. Version 0.81
Reference on creating MonoDevelop file templates:
Monodevelop: Howto add a WinForm project and file template
Writing an Add-In - MonoDevelop
Extension Tree Reference - MonoDevelop
Unity Forum thread
I used your package to develop my own template system, but, the package don't come in file menu, even when I disable/enable it. what's the problem?
I made some tests and here are some conclusions.
On restart of MonoDevelop, if your .addin.xml has some errors or is not well formed xml file, MonoDevelop will not load it (if it has a cached working version of previous .addin.xml it will load that one).
Using enable/disable will not reload .addin.xml, only .xft.xml files. So if you make changes in .addin.xml and want to see them, you should restart MonoDevelop.
To know if changed .addin.xml has errors, you could change its 'name' and if you don't see in Add-in Manager a new name, but an old one, you know it didn't load because of errors, so previous cached file was loaded.
If some of .xtf.xml files didn't load, you can see in Message Log that there was a problem (Menu: View->Pads->Message Log). You will not see .addin.xml errors in Message Log.
If you can't find out what could be wrong with your .addin.xml you can contact me by email on my blog.