Mono in VS2003 is a piece of cake, because there is an installer, and a community of users who have shaved all the problems away.
Sadly Mono in VS2005 is not that simple, and has given me considerable aggrevation, but I've now finally got a running add-in in VS2005. Following is an bullet point list of what I did to achieve this milestone:
- Have mono installed, thanks P@ 😉
- Download vsAddin2005 from http://anonsvn.mono-project.com/viewcvs/trunk/wintools/vsAddIn2005/ (Rob found this library)
- Open the solution in VS2005
- Open monoaddin.Addin and change the path in <Assembly> to the path you are using
- Build everything
- Copy all files from BinAndLib to the folder where your assembly is. (The code checks if they arein that folder. This surely most be a bug, because it would be enough to have them in the path.)
- You need all files from the folders BinAndLib and reflib somewhere in your path, e.g. system32. (Could also add the folders to the path)
- Start VS2005
- Go to Tools->option, under environment->Add-in/Macros security add the folder which has monoaddin.Addin
- Go to Tools->Addin manager…
- tick all the options of the monoaddin
- Open a solution and you can celebrate :o)
Unfortunately it doesn't seem to like VB.Net at all…
For those who are feeling particularly mentally challenged, please note that you also have to have mono installed on your machine. Otherwise, you might wonder why the addin doesn't work until you realise. Not that I forgot I had uninstalled it, of course, oh no…
Additional info:
VB.Net works as well. Unfortunately System.deployment is not fully implemented in Mono yet, and as VB.Net standard windows solution adds it by default mono can't compile, hence the not running solution above.
Interesting… a quick test app I just did includes system.deployment but it runs just fine (a little slower than in .NET but nothing to grumble about really) – however, I create a deployment unit (crashes)
I guess one of us must have a strange VS install?
There seems to be an easier way, which I overlooked the first time around.
Paco has already included the addin in the latest gtk# win32 installer at http://developer.novell.com/wiki/index.php/Gtk_sharp_Win32_Installer_for_Microsoft_.NET_Framework_1.1_SDK
I somehow overlooked that this isn't part of official mono/gtk# installer, and has to be installed after mono.
Yes – the easier way works!
My confusion arose due to the wording on Novell's download pages. The mono download does not include GTK# for .NET only GTK# for mono, hence to get the visual studio assemblies installed developers also need to install the GTK# for .NET.
yes it works very thanks
how to download from http://anonsvn.mono-project.com/viewcvs/trunk/wintools/vsAddIn2005/