You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
added simple .cmds for debugging test.fsx script from either the IDE or the command line
added diagnostic lines
appended todo / bug / done / fixed / notes sections. Just a simple in-file co-ordination mechanism.
added basic .gitignore
letuser= args.[1]:?> string|>fun s ->if String.IsNullOrEmpty(s)then"anonymous"else s // TODO.1
124
+
letpwd=args.[2]:?> string|>fun s ->if String.IsNullOrEmpty(s)then"[email protected]"else s
98
125
createTypes(typeName, site, user, pwd)))
99
126
this.AddNamespace(nameSpace,[topType])
100
127
101
128
[<assembly:TypeProviderAssembly>]
102
-
do()
129
+
do()
130
+
131
+
// TODO
132
+
// ----
133
+
134
+
// TODO.1: pick up FTP courtesy details from environment variables?
135
+
// TODO.2: add progress updates via intellisense? ie. | | and |**** underneath for a text based left to right gauge
136
+
// TODO.3: return `notfound or exception on error
137
+
// TODO.4: consider having a verbose and diagnostic modes to std out? ie. consider actually keeping them after testing is complete
138
+
// TODO.5: allow this to be set through type provider instantiation param <>
139
+
// TODO.6: add diag info to intellisense to cover command line + also IDE support (ie. so that it's transparent irrespective of usage style)
140
+
141
+
// BUG
142
+
// ---
143
+
// BUG.1: file identifiers are never defined. Is this because of an error in the quotation? Why?
144
+
145
+
// DONE
146
+
// ----
147
+
148
+
// FIXED
149
+
// -----
150
+
151
+
// NOTES
152
+
// -----
153
+
// NB. possibly the original example Don translated to F# live? https://msdn.microsoft.com/en-us/library/ms229711%28v=vs.110%29.aspx?f=255&MSPPError=-2147217396
@REM it's better to load .fsx files in a different process, because when you are in a compile->test->compile loop, it's easier to kill off any references
2
+
@REM the VS IDE might make on your behalf just by having the .fsx file open. Saves you getting caught out asking intermittantly, 'why isn't it copying after compiling okay?'
@fsc will compile and run test.fsx (ie. emulate fsi / VS Intellisense "interpreting" the dotted-into sub phrases)
2
+
@This way there are no side effects for the VS IDE. It's a cleaner way to test, because the process will die after being run and release any .dll file locks it may have so that you can compile again afterwards.
0 commit comments