TEXT TO lchtml TEXTMERGE (flags as needed)
<html>
<body>
ENDTEXT
LOCAL ldDate
ldToday = DATE()
TEXT TO lcHtml ADDITIVE TEXTMERGE (flags as needed)
Today is <<ldDate>>
</body>
</html>
ENDTEXT
Then executed with EXECSCRIPT(lcScript, params as needed) with the results returned to the calling web server (usually aspx.net calling VFP as a multithreaded com dll)
Does XSharp support the EXECSCRIPT command? Or even better, can it serve as the language for razor templates (.xshtml)?
Brian,
Yes, we support ExecScript.
We have not looked at Razor Templates. I suspect that they are for C# only. I don't think they even support Visual Basic.
Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
I am getting this error message when trying to run ExecScript from a XSharp class library called from an ASP.Net razor template. Note that this works fine from an XSharp executable.
"The invoked member is not supported in a dynamic assembly."
Here is my Execscript call:
RETURN ExecScript("RETURN 'Hello World!'")
Brian,
I am not in the office right now, so it is difficult to test and answer this.
I suspect that has to do with some startup code that is not running when you call ExecScript from a non X# appplication.
Normally this code is added to the main app and automatically running when the app is started,
This startup code sets the dialect in the runtime state and some other options, such as the current date/time format and codepage used for string comparisons.
I'll look into this early next week.
Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
I modified the example to be able to run the program as an application. It works as an app, and fails as a library. Note that I had to update System.Memory as well. See attached. In the revised sample, I removed the separate console app. Simply change the project type and startup project to test as a console versus library. A summary of the code changes below:
FUNCTION Start() AS VOID STRICT
? EXECSCRIPT("RETURN 'Hello World!'")
WAIT
RETURN
END FUNCTION
Change Startup project to ExecScriptWeb with Output Type to Console Application and it works. Change it back to Class Library and Startup Project to WebRoot, and it fails as before.
Hi Brian,
if you are relying in some manner on XSharp, then I would strongly recommend support the work of the development team by a FoX subscription.
After all, also Robert and his group needs to eat and to pay their bills, and more money permits them to dedicate more time to the project and/or hire other people to do work on the project.
And FoX membership gives you also access to the newest X# version and a better support from the team and sometimes also some possibility to have some influence on the future developments.
Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Brian,
I have posted my take on missing "base vfp DNA" in other thread here in vfp forum.
Perhaps you should offer a prioritized list of features xSharp must support for your programs.
