Unfortunately, express won't work: it doesn't support addins.
On 5/31/07, Evan Worley <[EMAIL PROTECTED]> wrote:
Great work Shane, While I have yet to see the steaming coffee, I am sure I will be very pleased :) Do you know if the nmaven addin to VS2005 would work for Visual C# Express? I don't have a VS license so Visual C# express works great for me. Also since SharpDevelop/Mono is put into the background, I won't have a way to experiment with the latest unless I acquire VS2005. Thanks, Evan On 5/31/07, Shane Isbell <[EMAIL PROTECTED]> wrote: > > Just to keep everyone in the loop, I have finished up all the loose ends > on > the first stable version of the Visual Studio 2005 addin. To make Evan > happy, I even changed the smiley face icon on the addin to a steaming cup > of > coffee, which I think is an appropriate icon for a MS IDE. I am going to > start work on: IDE-1: Browse Maven Repository and add/delete dependencies, > which I expect will take about a 3-4 week iteration. This iteration will > include: > > http://jira.codehaus.org/browse/NMAVEN-39 > http://jira.codehaus.org/browse/NMAVEN-59 > http://jira.codehaus.org/browse/NMAVEN-3 > > The next 3-4 week iteration will include: > Configuration of Remote Services through the IDE: > http://jira.codehaus.org/browse/NMAVEN-41 > Archetype Generation: http://jira.codehaus.org/browse/NMAVEN-18 > > At least through July, the Mono/SharpDevelop support is going to suffer a > bit. The primary IDE focus is on Visual Studio (as I don't have time to do > both IDEs now). NMaven support with Mono is suffering due to a bug in > Mono: > http://jira.codehaus.org/browse/NMAVEN-67 This means that Maven plugins > written in .NET are not supported with Mono, thus limiting the use of key > plugins, like solution generation, to MS WIndows only. > > Regards, > Shane >
