FUTURE POSTS
- Partial writes, IO_Uring and safety - 15 hours from now
- Configuration values & Escape hatches - 4 days from now
- What happens when a sparse file allocation fails? - 6 days from now
- NTFS has an emergency stash of disk space - 8 days from now
- Challenge: Giving file system developer ulcer - 11 days from now
And 4 more posts are pending...
There are posts all the way to Feb 17, 2025
Comments
Scintilla?
if so - what 'bout Notepad2/Notepad++/Scite language packs?
Sharp Develop, actually
So do you have the "auto-layout diagram" feature yet? :P
Nope,
IIRC, you wanted to do that, right? :-)
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?
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.
Can you add a file?
rhino-tools\rhino-etl\Rhino.ETL\Properties\AssemblyInfo.cs
:)
Jay,
Run msbuild default.build, it will generate the missing files.
@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
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
Comment preview