search

xxtbg / fseye

Automatically exported from code.google.com/p/fseye
Apache License 2.0
0 stars 0 forks source link

Embed window in Visual Studio #18

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
It would be good if FsEye could be downloaded through the Visual Studio 
Extension Manager and embed itself within Visual Studio.

Original issue reported on code.google.com by stephen....@gmail.com on 24 Jan 2012 at 4:51

GoogleCodeExporter commented 9 years ago 
In trunk I was able to easily enough create a visual studio addin project that 
creates the FsEye WatchPanel as a dockable, etc. tool window. But the tricky 
part, I think, is going to be how to integrate it with FSI, considering 
deployment (ideally published in the Gallery and available through the 
Extension Manger).

Aside: documentation is not great for VS addin SDK.

Found a link that might help: 
http://riouxsvn.com/svn/vsprojectrename/VisualStudioProjectRenamer/VSPRExtension
/

Original comment by stephen....@gmail.com on 26 Jan 2012 at 4:31

GoogleCodeExporter commented 9 years ago 
looking around registry, i found the entry 

HKEY_USERS\S-1-5-21-4245615636-1313791888-3155049987-1001\Software\Microsoft\Vis
ualStudio\10.0\DialogPage\Microsoft.VisualStudio.FSharp.Interactive.FsiPropertyP
age

with value name FsiCommandLineArgs which we might be able to use for 
installation, e.g. --optimize --load:"C:\FsEye\FsEye.fsx"

Original comment by stephen....@gmail.com on 29 Jan 2012 at 4:58

GoogleCodeExporter commented 9 years ago 
I was messing around with the the old add-in framework, but really should have 
been looking at the new extensiblity framework: 
http://msdn.microsoft.com/en-us/vstudio/ff718165.aspx

Original comment by stephen....@gmail.com on 29 Jan 2012 at 5:07

GoogleCodeExporter commented 9 years ago 
Instructions on how to create a tool window with the extensibility api: 
http://msdn.microsoft.com/en-us/library/bb165051.aspx

Original comment by stephen....@gmail.com on 29 Jan 2012 at 5:30

GoogleCodeExporter commented 9 years ago 
If we can remove the job of creating WatchModel instances entirely from any of 
the WinForm controls and delegate that job to the Eye instance, then we should 
be able to marshal by ref across process boundaries (i.e. the add-in and FSI) 
fairly easily.

Original comment by stephen....@gmail.com on 7 May 2012 at 5:55

GoogleCodeExporter commented 9 years ago 
I vote for this feature :) The flying separate window eats too much space on 
the monitor. Its perfect place, I think, is as close as possible to to the FSI 
window.

Original comment by vas...@gmail.com on 24 Nov 2013 at 6:40