Geek Answers Handbook

Support for F # IDE scripts for accessing internal types in reference assemblies

Typically, for a C # / F # project without scripting, you can specify the InternalsVisibleTo attribute in the dependency assembly and be able to get intellisense for your internal types in the IDE. But in F # scripts, how do I configure the dependency assembly relative to the IDE that I use to get intellisense for internal types? Of course, for the script to work under fsi , I assume I need something like

 [assembly:InternalsVisibleTo("fsi")]

But in order to get IDE support, should I also list every known IDE in the dependency assembly? It does not scale very well.

I searched the code and found this , where fsc , fsi , compiler assembly and their strong version names, etc. all of them are indicated, apparently, to host the IDE. This is exactly what concerns me, and I do not want the garbage collector of their meetings. Is there a better way?

+7
f # f # -interactive
source share

No one has answered this question yet.

See related questions:

91
Best approach for designing F # libraries for use with both F # and C #
21
How to organize the F # source of a large project (> 300 classes) in Visual Studio?
10
How to create C # compatible .Net 4.0 types using providers like F # 3.0
7
Is there a way to implement support like F # Option in ServiceStack?
4
F # Script API SharePoint 2010 not working
3
How to get the correct F # Type provider permission folder when linking to assemblies via #load?
2
Using app.config from F # script
2
error FS0193: internal error: failed to load type
0
F #: using indexed property F # from C #
0
F # dll in F # script

More articles:


All Articles