Rhino ETL - IDE previous: Rhino Mocks 3.2 next: Google searches I am ashamed of... Hush, it is a secret... Comments 08/14/2007 08:40 AM by Ken Egozi Scintilla? if so - what 'bout Notepad2/Notepad++/Scite language packs? 08/14/2007 08:43 AM by Ayende Rahien Sharp Develop, actually 08/14/2007 09:40 AM by Avish So do you have the "auto-layout diagram" feature yet? :P 08/14/2007 10:10 AM by Ayende Rahien Nope, IIRC, you wanted to do that, right? :-) 08/14/2007 02:23 PM by Simon Have you considered using the new VS2008 Shell (see http://msdn2.microsoft.com/en-us/vstudio/bb510103.aspx)? MS looks like it's taking a page out of the Eclipse notebook and working on turning their excellent IDE into a more generic platform for tools vendors. Thoughts? 08/14/2007 03:00 PM by Ayende Rahien No, from experience with the past, extending VS is a PITA of COM and unknown errors. And I know how to extend #D, and that is easy to do. 08/14/2007 08:00 PM by Jay R. Wren Can you add a file? rhino-tools\rhino-etl\Rhino.ETL\Properties\AssemblyInfo.cs :) 08/14/2007 08:16 PM by Ayende Rahien Jay, Run msbuild default.build, it will generate the missing files. 08/14/2007 08:57 PM by Stuart Carnie @Ayende Actually, the managed package framework for VS 2005 was very good for creating extensions in managed code. There were times you had to drop back for very low level stuff; however we were quite successful prototyping some designers. The VS SDK team have contined to wrap more of the COM API in managed objects, so I'm sure it's looking very good now. Cheers, Stuart 08/14/2007 09:06 PM by Ayende Rahien Stuart, I had basic code formatting support & line indenting in about two hours, most of them were spent exploring #D. I would be interested in showing a sample that shows how this is possible in VS Shell Comments have been closed on this topic.