What's new in Web Connection
not released yet
wwDotnetBridge: Improved support for Task Exception Handling When making calls to .NET
Taskmethods, wwDotnetBridge now does a better job of handling exceptions and returning the result in the
OnError()callback. More errors are handled and error messages should be more consistent with the actual error (rather than a generic error and an innerException).
Updated to latest .NET
Newtonsoft.JsonLibrary for Json Serialization
We've updated the .NET JSON parsing library to ensure continued compatibility with the latest .NET versions widely used. It's been a while since the last update, and
v13.0.3has been in circulation now for quite a while and this gets us up to date with the latest performance and parsing improvements of Newtonsoft's JSON library. This is a potentially breaking change: Make sure to update the
wwDotnetBridge.dllin your projects.
UpdateNoComRegistration Module Configuration for bypassing COM Registration on Publish
Added this switch to allow bypassing COM registration when uploading and hotswapping new binaries to the server. This switch can be useful if you're using the same server for multiple Web Connection installs, especially when publishing file based projects that are used in tandem with COM based instances.
wwJsonServiceClient CallService Url Fix up
You can now use a site relative URL when calling
CallService()rather than requiring a fully qualified URL. You can use Urls like
/authenticatewhich makes it easier to switch between different host sites. If the URL does not start with
cServiceBaseUrlis prepended to the URL to create a full URL. This is useful if you switch between different sites for example when running against dev, staging and production servers.
wwJsonServiceClient: Optionally capture Request and Response Data You can now optionally capture all request and response data via the
lSaveRequestDataflag. If set any POSTed JSON data will be capture in
cRequestDataand any result data is capture in
cResponseDataboth of which are useful for debugging.
wwJsonServiceClient is abstracted into its own PRG File
wwJsonServiceClient now has migrated out of the
wwJsonSerializer.prgfile to its own
wwJsonServiceClient.prgfile. This is a minor breaking change - you'll need to make sure
DO wwJsonServiceClientis called explicitly now to ensure the library is loaded along with all dependencies.
Fix: COM Server Publish Servers not Reloading
Fixed issue where COM server uploads and restarts would not work correct
Fix: Stop wwDotnetBridge from Attempting to Serialize Non-FoxPro Objects
wwDotnetBridge now checks for COM objects and components and won't serialize those objects rather than attempting and failing. FoxPro's
AMEMBERS()can't reliably retrieve properties from COM objects so rather than getting an incomplete object, or worse a crash due to non-properties being access, we now serialize
nullfor COM objects.
Breaking Changes in 7.33
- Make sure to update
wwDotnetBridge.dllin your Projects
The two dlls are linked to each other and so they always need to stay in sync in order for JSON serialization to work consistently. Needed if you use JSON deserialization using
wwJsonSerializer, or you're building API Web projects.
April 5th, 2023 • Release Post
GetUrlEncodedKeyCollection() to retrieve all QueryString and ServerVariables
You can use this new method to create collection from a set of Url encoded key value pairs, such as those found in the
.cServerVariablesproperties as well as explicitly Url encoded strings.
wwDotnetBridge COM Array Support for Lists, Dictionaries, Collections
Added support for direct access of all sorts of collections directly in
ComArrayinstances which are returned for collection results from
GetProperty()or when creating lists. You can now access
Dictionary<TKey, TValue>collections directly with ComArray, via
RemoveItem()etc. All methods have been updated to work with
IEnumerablewith support for numeric indexes or key or value lookups.
Auto-Fixup of ComArray for Instance Parameters in all Intrinsic Methods
You can now pass ComArray instances directly as the first
loInstanceparameter for most intrinsic invocation methods like
SetProperty()etc. Thanks to Christof Wollenhaupt for this improvement and bug fix around a regression error related to the new list and dictionary support. wwDotnetBridge #27
ComArray.Add() method to complement AddItem()
There's now a
ComArray.Add()method that performs the same task as
AddItem()but provides better native compatibility with .NET collection syntax (ie.
List.Add(loItem)). This method only supports a single parameter used for Lists and non-dictionary collections. For dictionaries with keys use AddDictionaryItem() to an item with a key.
wwJsonSerializer no longer uses PropertyExclusionList on EMPTY Object
EMPTYobjects, or by association cursors and collections which internally use
PropertyExclusionListis not applied to properties. The list is meant to keep FoxPro default properties from polluting the output JSON, but EMPTY objects do not have any base properties, so the list is not necessary. This allows for creating properties with reserved FoxPro property names like
Fix: wwJsonSerializer::AssumeUtcDates Output still converting to Local
Fixed issue that when this flag was set, it would not convert the inbound date from local to UTC but use the current date as UTC, but it would still convert the date back to local when deserializing. This change now leaves the deserialized date in the original UTC time, but returns it as a local FoxPro time (ie. the date is not adjusted for timezone) which was the original assumption of this flag. This was broken when we switched from FoxPro based parsing to .NET parsing using JSON.NET. This is a potentially breaking change if you used this obscure flag in your code.
October 25th, 2022
Improved Support for .NET Core in wwDotnetBridgeCore
Improved runtime discovery logic for wwDotnetCoreBridge. Fixed
GetDotnetVersion()to show .NET Core version.
wwDotnetBridge: GetwwDotnetCoreBridge() and InitializewwDotnetCoreBridge()
Added these helper functions to load the .NET Core Runtime of wwDotnetBridge and caching the runtime in the same way that the Full Framework versions of these functions do.
wwCookie and Response.AddCookie() Default Changes
Made default cookie handling more secure by adding
HttpOnlyto the default settings. Also added
samesite=strict;to the default when explicitly creating a cookie. The
wwCookie::Init()constructor now can set the name and value ie.:
June 12th, 2022
Added wwJsonSerializer::DefaultEmptyDate Property
1970-1-1which was the previous value set by default and couldn't be overridden.
Fix: wwJsonService UTF-8 Encoding/Decoding
Fixed inconsistencies in UTF-8 encoding by the service client. Now data sent is encoded and data received is decoded. Optional parameters allow disabling this auto en/decoding.
Breaking Changes in 7.28
- wwJsonServiceClient fixes UTF-8 decoding by default
There was a bug that caused
wwJsonServiceClientto not decode UTF-8 content automatically, which would result in extended characters in deserialized values and objects to be misformatted. In 7.27 content now is UTF-8 decoded by default and you can disable the auto-decoding via the
lNoUtfDecoding=.T.to keep the old behavior.
January 18th, 2022 • Release Post • Breaking Changes
JSON Server Status
The Web Connection Handler and Web Connection Web Server now have a dedicated
AdministrationJson.wclink you can use to retrieve server configuration information as JSON. The result includes all the server configuration settings as well as information about the running server similar to the main
Web Connection Web Server now runs on .NET 6.0
Updated the local Web Connection Web Server to run on the newly released .NET 6.0 which improves performance and provides a number of useful enhancements to the local web server operation. .NET 6.0 is an LTS release. This is a breaking change that requires that .NET Core 6.0 is installed.
Add Performance Counters back to Web Connection Server
The .NET Core Web Server now display CPU usage for server instances on the Middleware Administration page. This was previously not working.
Better Error Handling for REST Service Invalid URLs
Invalid REST Routes - ie. referencing a missing method in a REST Service - now returns an HTTP 404 error. The error message now also describes the error better as
Missing endpoint method: MethodName.
Method that allows you to map an individual property name to a new name. This allows you to map names to values that standard FoxPro property serialization would not normally allow for such as property names with spaces or special characters. Similar to
PropertyNameOverridesin behavior but with more control.
Automatically clear wwSql Named Parameters before new command executes
Automatically clear SQL parameters set on the last command, before executing the next command, unless
lNoParameterResetis explicitly set to avoid this. This removes the need to explicitly clear parameters when running multiple commands on a single instance/connection. This was previously implemented but lacked the
lNoParameterResetflag to allow to keep parameters for multiple commands for unusual use cases where the same command is run many times in a row. Note parameters are cleared before the next command runs not when the original command has completed, so you can review parameters and also receive out parameters.
Fix: Issue with Live Reload Requests not Firing on IIS
Fixed issue where hitting a link on IIS/IISEXPRESS occasionally would not work when LiveReload was enabled. Fixed by ensuring the output stream is properly disposed before writing the injected reload script.
Fix wwSftp::OnFtpBufferUpdate() to allow Cancelling Downloads and Uploads
wwSftpso it now works to provide to check for the
lDownloadCancelledflag on a passed in
loSftpinstance when set. Previously this flag was ignored.
Fix: ExpandTemplate with _Layout Pages not reading Base Path correctly
Fixed issue where
wwPageResponse.ExpandTemlate()was not correctly setting the Web site base path resulting in empty layout pages to be rendered. This in turn resulted in empty pages. Fixed.
Breaking Changes in 7.26
NewtonSoft.Json.dll needs to be Updated
We've updated the .NET JSON serializer to the latest version
13.0.1in Web Connection and if you're using the REST API Process classes or using the JSON Serializer in any way make sure to update this DLL in your application folder or
Web Connection Web Server now uses .NET Core 6.0
The optional West Wind Web Connection local Web Server now uses .NET 6.0 to support the latest LTS release of the .NET Core Runtime. To use this local Web Server you'll need to make sure that .NET Core 6.0 SDK or .NET Core 6.0 Hosting Bundle is installed.
October 1st, 2021 • Breaking Changes
Improved wwSmtp Error Reporting (.NET mode)
wwSmtp now reports error information using the base exception rather than the top level exception which provides more info for connection level errors such as socket connect failures or invalid connection information/domain names.
Improved access to HTTP and Serializer functionality in wwJsonServiceClient
wwJsonServiceClientto always create the the
.oSerializerproperties on startup. These objects allow customization of the HTTP request and JSON Serializer respectively. A new
AddHeader()method is a shortcut method to make HTTP Header access more discoverable.
wwEncryption::ComputeHash() BinHexMode parameter
Added a parameter that lets you specify the output format as binHex optionally which is a double character representation of each byte in the result hash. The default format is base64 and the
llUseBinHexflag optionally overrides to let you use binHex. If the parameter is not specificied the global
SetBinHexMode()setting is used instead.
These methods now let you choose the crypto provider (TripleDES and AES), the cipher mode, IV (for various ciphers) and optional key hashing modes. You can also set the binHex mode optionally.
wwUtils: ShowJson() Function
Added a new
ShowJson()function in wwUtils that shows the content of the string in the configured JSON editor (typically VS Code). Also update the ShowHtml, ShowXml methods to output UTF-8 files that are then rendered from disk to avoid garbage characters otherwise shown.
Breaking Changes in 7.25
- NewtonSoft.Json.dll needs to be Updated
We've updated the .NET JSON serializer to the latest version
13.0.1in Web Connection and if you're using the REST API Process classes or using the JSON Serializer in any way make sure to update this DLL in your application folder or
August 6th, 2020
This new method retrieves multiple values (multi-select) for a single key in a query string.
Add support for AES Encryption in wwEncyrption Class
You can now use AES encryption optionally instead of the default TripleDES encryption previously supported for the
DecryptString()methods. You can now also create encrypted content that does not encode the provided encryptionKey with MD5 (as is common) and instead uses the raw encryption key to allow matching encrypted content generated by tools other than this method.
New helper function that wraps
CollectionToCursor()which deserializes into a cursor/table that's already open to provide the data structure to import to.
Local User Credentials for SMTP Emails
Added support for a special
LOCALACCOUNTusername value that can be used to specify to use the logged on user's Windows credentials for SMTP server access. Note this is unusual and typically only works for internal servers running Exchange or other Managed Mail platforms using Windows Domain Accounts for access.
March 16th, 2021
Release Notes • Breaking Changes
Web Connection Web Socket Support
Web Connection now supports basic Web Socket functionality that allows capturing Web Socket requests in an
westwind-websocket.jslibrary for the client and a Web Connection Web Socket message class to create and send messages, as well as a wwProcess class
OnWebSocket()handler method that can be overridden to intercept Web Socket messages in Web Connection FoxPro code.
Consolidated Web Connection Administration Page:
Web Connection now has a single built-in administration that doesn't need to be explicitly distributed with an application. This page consolidates both the core Web Connection Module operations as well as most
wwMaintoperations that operate on the Web Connection server. The single page consolidates all functionality to a more user-friendly single page, and uses a single authentication experience and removes the need for distributing
Admin.aspxor similar page.
Admin Page Updates
Administration.wcadmin page now includes an Edit button when running on the local machine under an Interactive account. If you use IIS Express, or the Web Connection Web Server you can now directly jump into editing the configuration for the appropriate configuration file.
wwDotnetCoreBridge .NET 5.0 Support
We've updated wwDotnetCoreBridge - the version of wwDotnetBridge that works with .NET Core - so that it now works with .NET (Core) 5.0. This is in addition to support for .NET Core 3.1. This update fixes some issues due to framework changes in 5.0 so make sure to update
wwDotnetBridge.dllfor existing installs.
New wwProcess::OnRouting() handler
New routing override hook method that allows you to customize process class routing which usually maps to a method in the process class or a page on disk to render. This mechanism intercepts the routing process before Web Connection's routing runs and lets you check for custom route conditions and call a Process method in response if the route matches. Very useful to allow re-using existing authentication functionality for without having to copy and create new process classes, or for handling static content that needs to be authenticated. The big benefit is that you can re-use a single process class's configuration.
New wwHttp::AddPostFile() Method
Added an explicit method that lets you add File Upload POST data for multi-part form based uploads. This is just a specialized version of the
AddPostKey()method provided to make it explicit when uploading a file as part of form POST operation and to simplify the documentation.
WWC_LOGGING_MAX_CONTENT_SIZE Compilation Flag
This flag allows you to control the max Request and Response size to log when using Full Request or Request and Response logging. This allows you to control the size of the output captured to be limited in case of file up or downloads that may be very large. The default is 50,000.
Fix: Large Number JSON Result Values
Fixed issue with large number rounding errors that would break JSON serialization. Caused by numeric overflows in FoxPro's value to string conversions, fixed by explicitly rounding down numbers to the
Fix: Request.GetCurrentUrl() with Ports and HTTPS
Fix problem with
https://requests that have custom ports not showing the HTTP scheme properly. Fixed.
Breaking Changes in 7.20
- Web Connection Web Server now uses .NET Core 5.0
To provide support for the most current version of .NET the Web Connection local dev server now uses .NET Core 5.0. To use this local Web Server you'll need to make sure that .NET Core 5.0 SDK or .NET Core Runtime and ASP.NET Core Runtime are installed.
August 2nd, 2020 • Release Notes • Breaking Changes
New Log Formats
You can now configure the Web Connection
wwWebRequestLogvia a new
nLogFormatconfiguration setting: 0 - No Logging, 1 - Minimal Request (URL only, no request or response output saved), 2 - Full Request (saves server vars and POST data but not Response), 3 - Request and Response (saves everything). The setting can be set in
Server.oConfig.nLogFormat. This replaces the now obsolete logging compiler flag which allows the log levels to be changed at runtime, without recompilation. The format also removes the
SaveRequestFilessetting which is now equivalent to logging with
Updated Recent Request Viewer
The Last Request Viewer has been updated to use the log information from the
wwRequestLogtable. The viewer has been updated with a new UI that shows the last 35 requests (can be changed). You can now quickly browse through multiple requests and not just the last one as the data is captured in the
wwRequestLogtable and loaded from there. For best log action during development set
LogFormat=3- other formats show a note and recommend to use this format.
Change over to Build.ps1 from Build.bat for Project Packaging Script
Updated the Web Connection packaging build script to use Powershell to create a more generic script that is more portable. The build script packages the EXE, INI, dependent DLLs, a cleaned up Web folder (minus compiled files) and the data folder to provide a single zip file. Requires a 7Zip installation.
To make it easier to generically launch the Web Connection development environment for a project the new project now generates a
Start-FoxPro-IDE-in-Project.ps1Powershell script. This is in addition to the shortcut which also works in the project folder, but breaks if the project is moved. The Powershell script always works as it can use relative paths, rather than the required full paths in the Shortcut. You can just Run with Powershell to launch your project in the FoxPro IDE.
Session Cookies are set with
Session cookies in Web Connection now use
SameSite=Strictpolicy to work around tracking requirements by Web browsers. Using
strictforces the cookie to be confined to the originating site which means it's not shared with external services ensuring that data is kept private and preventing cross site scripting attacks.
wwCookie now defaults to
As with Session Cookies, the default wwCookie class which can be used to create new cookies default to
SameSite=Strictin order to comply with privacy requirements by default. If you need to share cookies with calling sites you can explicitly override the
Server Hot Swapping File Uploads also Upload a DLL file if available
The two hotswapping routines now also upload a DLL file of the
UpdateExefile, if that DLL file exists. This is to support VFP 10 build applications which are made up of a small loader EXE and the natively compiled FoxPro dll.
wwDotnetBridge support for non-Property Indexers in GetPropertyEx()
You can now access Indexed properties (
["name"]) without requiring a property as part of the property name. So you can now do:
Fix: JSON Date Formatting Rounding Issue
Fixed a bug where dates from cursors would not show the exact second/millisecond format with a float rounding error. Reworked the Json conversion function to adjust date explicitly to UTC format and then using
Breaking Changes in 7.15
Must update wwDotnetBridge.dll
wwDotnetBridge has some important fixes and a few additional helpers that are used by some of the libraries - specifically
wwJsonSerializerwhich break when used with the older DLL.
wwRequestLog Structure Changes
wwRequestLoghas a few changes in fields so if you're using FoxPro tables, delete the
wwRequestLogtable and let it recreate. For SQL Server remove the table and use the Console SQL Log Table creation Wizard to let it recreate or use the
Westwind.sqltemplate script on an existing database.
Recommended: Set the
LogFormatproperty is used to control logging. The default format is
1 - Minimal Request. But for local development it's often useful to set this to
3 - Request and Responseso you can easily review requests and the output generated while debugging.
May 29th, 2020
Request.GetServerName() now Returns Port Information
In light of using IIS Express and the Web Connection Web Server which are using local port numbers as part of the URL,
Reqest.GetServerName()has been updated to return domain names with the port if not port 80 or 443. It now returns
localhost:5200for example or
localhost:7000. This also fixes
Request.ResolveServerUrl()when generating URLs for sites that are using port numbers.
Request.IsLinkSecure() now checks the
IsLinkSecure()was checking explicit port numbers, but in recent IIS and ASP.NET Core versions an explicit
HTTPSvariable is available to determine precise status on whether a request is using a secure connection. This also fixes
httpsprefix for URL generated.
Added a new command line execution command that makes it easier to execute external executables using ShellExecute. Simplified syntax to take a single command line as string. Supports OS path resolution also works with Application Protocols
Administration Script Compilation Improvements
Administration.wcadmin page now includes script compilation in the Logging and Server Administration section of the administration page. The script compiler now takes an extension or a comma delimited list of multiple extensions that can be used to recompile scripts in the application.
Added a helper method to reliably return the result from .NET's internal
ToString()tends to be overloaded and so is not directly accessible on most via COM interop. This helper ensures it'll work on all .NET types.
Fix: Console Execution fails when not running out of Web Connection Install Folder
Fix issue with the Console application failing when started from within a project folder rather than the Web Connection root. Updated so that path is changed to the install root so all dependencies are found. This fixes a few odd problems like console files not being found and an errant
wconnect.fxpfile being created.
Fix: Web Connection Web Server Cookie Processing Bug in ASP.NET Core
Work around an ASP.NET Core bug that incorrectly formats the raw cookie string of a request by explicitly rewriting all cookies using the proper format.
April 29th, 2020 • Release Notes
Console Update Project Resources Helper
Added a new
UPDATEPROJECTRESOURCESConsole Command that can be used to update an existing project with the resources from an updated Web Connection installation. This updates the Web Connection Modules, the Web Connection Web Server, Web Connection dependent Dlls (wwDotnetBridge, wwipstuff, json), the stock libraries, the Web Connection support scripts. Also added this to the main Console Form as UI operation that prompts for project path and operations to perform. This should make much easier to update existing project with the latest bits from a Web Connection.
Updated the stock Web Connection page templates to the latest builds of Bootstrap and FontAwesome. Also simplified some dependencies reducing script count.
Feature Parity for .NET Core Web Connection Web Server
The new .NET Core based, standalone Web Connection Web Server is now 99% compatible with the classic ASP.NET handler so these two servers can be used interchangeably without feature differences. For development, the Web Connection server is very light weight and command line driven and can be automated easily.
Linux Support for new Web Connection Web Server
Because the new Web Connection Web Server runs .NET Core, it can also run on Linux which makes it possible to run the Web Connection Web Server on a Linux machine. Note that FoxPro still has to run on Windows but the server interface can run on a Linux box and push message files into a shared file location that both the Linux server and Web Connection Server application can access.
Due to problems with encoding in ASP.NET Core related to Unicode string conversions there's now a new
ProcessHitBinary()method on the server that receives a BLOB as input for request data, and returns BLOB data for output. This leaves all the string decoding and encoding predictably to the FoxPro end and lets the COM server simply process the raw binary data directly. This also removes an extra conversion and should remove some additional memory usage that previously was required for the Unicode string conversion. Both the ASP.NET Handler and .NET Core Middleware now call this method. This is a breaking change that requires that
wwServer.prgare updated in sync as the new method is required..
wwUtils IsDotnetCore() Helper
Support function that checks if .NET Core is installed. Returns the highest version number.
Helper function that checks to see if the given Web Server type is installed and ready for configuration. Use the standard Web Server keys ("IIS","IISEXPRESS","WEBCONNECTIONWEBSERVER", "APACHE") to check if a given Web Server is installed. Internally used by the Console.
wwDotnetBridge Constructor Support for Structs
Fix ability to instantiate .NET
structtypes which now are returned as
wwDotnetBridge Instances can now pass ComValue instances as Parameters
You can now pass
GetProperty()so that you can invoke functionality on objects that are otherwise not accessible in FoxPro. When you pass
loInstanceparameter, wwDotnetBridge automatically uses the
Breaking Changes in v7.12
The new binary transfer functionality in this version is a major breaking change that requires that both the
webconnectionmodule.dlland the Web Connection framework (and more specifically
wwServer::ProcessHitBinary()) are synced. The module now calls this new
wwServerServer interface so this method has to exist and it didn't in older versions. In turn this also adds the method to the COM interface, so make sure to re-register your server when updating applications on your servers.
March 10th, 2020 • Release Notes
Preview: Local .NET Core Development Server
We've added a new local, self-contained, .NET Core based Web server that can be used instead of IIS to develop your Web Connection applications locally and also in production (on IIS). This new server uses .NET Core 3.x and can generically run the Web Server from the command line. Advantages are: Pre-configured for Web Connection, all configuration in one place, non-Admin, runs from the command line, can run any Web Connection application out of a folder. It's now also possible to run the Web Connection Web Server (in File Mode) on Linux or Docker with Web Connection FoxPro Server running on a separate Windows machine.
Support for Non-Admin Console Operations
If you're creating new non-IIS using IIS Express projects or the new Web Connection Web Server, you can now do so without running as Administrator assuming you're installing into a folder where you have permissions to write. You still get an Admin request warning, but you now can continue to install.
Update Module/Middleware Administration Page
Number of cleanups on the Module/Middleware Administration pages for Web Connection with easier updates to items and a cleaner view of which mode (COM or File) is active. Also additional system information and updates are provided to make it easier to see relevant data all in one place.
Add wwCookie Class for Response.AddCookie() improvements
Added a new
wwCookieclass to make it cleaner to add cookies with all of the available HTTP Cookie features that are available. Rather than passing a ton of parameters to
Response.AddCookie()you now can pass an object with simple properties set.
Windows Authentication for Web Connection Server Requests
Previously Web Connection server requests using the built-in Windows based authentication used only Basic Authentication. We've now enabled Windows Authentication so you can use either Windows or Basic or both. This also means you can now run with only Windows Authentication enabled in your Web Site as both the ASP.NET requests and Web Connection requests can authenticate with it.
Simplify Live Reload Configuration
Added new WebConnectionModule that handles
.htmlLiveReload script injection when LiveReload is enabled. This removes the need to explicitly enable an extra handler for these extensions. The module automatically detects whether live reload is enabled and only injects content into HTML files when enabled. This simplifies configuration to the single
web.config. The WebConnectionModule is automatically configured for new projects.
Add Live Reload Retry
When sitting on a page and shutting down the Web Server the Web Socket disconnects and after that the page previously would no longer refresh on changes. This update continues pinging for a Web Socket every few seconds after failure to try and reconnect to the server. This allows for server updates/shutdowns and reconnecting after the server comes back.
Fix: Live Reload Socket for Https Requests
Fix issue where Live Reload was failing in the browser when running on an HTTPS page. Page would work but browser would console log an error in the WebSocket Live Reload script. Fixed and you can now use https.
New wwDotnetBridge.InvokeTaskMethodAsync() to call Async .NET Methods
Added a new method to make it easier to call
async.NET methods that return
Task<T>results. This method takes a callback handler object reference that is called on completion or failure of the method call. Similar to
InvokeMethodAsync()which calls non-async methods asynchronously but natively intercepts the
Taskresult and fires events on completion.
Added a new
IsDirectoryproperty to the SftpFile object returned in the
sftp::FtpListFiles()method to simplify figuring out whether an entry is a file or directory.
Log Server User Account
We now log the server user account in Web Connection FoxPro server requests in the request log. This can be useful to ensure you can see which account your FoxPro server is running under.
Fix: Perf Counter Permissions
Trap errors in Web Connection Module Server list related to PerfCounter access - if access is not allowed, perf-counters are turned off.
Breaking Changes in v7.10
LiveReload Configuration Change for
If using LiveReload you will need to change the configuration to use the new
WebConnectionModule. Using the new module removes the need to add/remove the old handler when switching modes - it now works off the
LiveReloadEnabledflag internally so you only have to set one setting.
Remove old Handler:
<handlers> <add name=".LiveReload_StaticHtml_wconnect-module" path="*.htm*" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" /> ... leave additional handlers </handlers>
**Add new Handler**: ```xml <modules> <add name="WebConnectionModule" type="Westwind.WebConnection.WebConnectionModule,WebConnectionModule"/> </modules>
- wwRequestLog has Structure Changes
Please make sure you delete the request log (
wwRequestLog.dbfby default) or add an
account v(15)field to the table. Latest version detects if the field is missing and automatically deletes the table and creates a new one otherwise.
October 22nd, 2019
Preview: Local .NET Core Web Server Support
We've added a self contained .NET Core Web server that can run standalone without a Web Server installed, or as a backend service inside of IIS. The server can be run from the command line and has a number of options, including automatic support for Live Reloading of content. You do need to have .NET Core 3.0 installed. This is currently in preview and there's no explicit configuration support and all info on how to use this new server both for development and behind IIS is described in the documentation topic.
Preview: .NET Core 3.0 Support with
wwDotnetBridge allows interop with .NET and now there's basic support for .NET Core. r
wwDotnetCoreBridgeallows loading and executing of .NET Core components. As with the full framework version, wwDotnetCoreBridge hosts its own copy of the .NET Core runtime and then proxies into it create types and values that make it possible to access most .NET Core features from Visual FoxPro.
Add Edit Button to Web Connection Status Form
Added an edit button that makes it easy to open the site in an editor. There's a new
CodeEditorCommandLinethat can be used to launch an editor in the Web Site or the full project so you can quickly jump to editing the site. The default editor assumes VS Code (
Fix: Error Message Code Display
Fixed error message code display to be properly HTML encoded. If the code contained HTML to generate the error display would render the HTML. Fixed with proper HTML encoding so the code displays properly as code.
Fix: wwDotnetBridge Guid Results and Properties
Changed behavior of wwDotnetBridge methods that return Guid values or accss Guid Properties. Guids are value types and fixed up by wwDotnetBridge, but previously used the obsolete
ComGuidtype. This has been changed to use the standard
ComValuetype and the
GetGuid()method. So a method that returns a Guid returns a
ComValue, as does a Guid property accessed with
Breaking Changes in 7.09
- ComGuid Class Retired for Guid Handling
Any wwDotnetBridge code that previously access Guid values, now uses the ComValue helper, which includes
NewGuid()helper methods. This is a breaking change, but provides better compatibility with all other special handling types which also use the
September 3rd, 2019
Simplified Live Reload Configuration
Refactored the way that Live Reload is hooked up to a 2 step process: Set the
EnableLiveReloadswitch and - for optional HTML file processing - enable the LiveReload Html Handler that intercepts requests to any
.htmfiles. This simplifies the configuration process which previously required adding a custom module and setting
runManagedModulesForAllRequestswhich had performance implications. See docs for more info on the new configuration features.
Visual Studio 2019 Addin Async Loading Enabled
Updated the Visual Studio addin to support async loading so the addin no longer shows load warnings on startup.
Fix JSON Handling for Large Strings and JSON Buffers
JSON size is limited by the FoxPro 16 meg limit, but due to the inefficiencies of JSON generation presizing a buffer the JSON string parser uses an overly pessimistic pre-sized buffer to hold JSON text that is passed to internal APIs. Changed the logic to maximize the buffer size at FoxPro's Max string size and handle errors if the buffer is overrun more gracefully. This will allow JSON string parsing up to the FoxPro 16 meg limit now where as before it was of the potential max buffer size.
Fix AppPool Creation Bug in New Installations
Fix bug where application pools in IIS weren't properly attached to the newly created sample site on first creation.
Cleanup Startup Launch.prg Handling
After setup and new project Launching now clearly shows what it's doing with messages to the desktop, so you new users can effectively re-run the application without having to look in the docs.
DO LAUNCHalways shows options now.
May 25th, 2019
Release Notes Blog Post • Breaking Changes
Server Live Reload for Server Code Changes
7.0 introduces updated Live Reload functionality without using Browser Sync. Rather there's now native support for live reloading in the Web Connection .NET Module. Live reload detects changes in Web client pages as well as server source code files. On the client changes are detected and immediately refresh the browser when saved. On the server changes are detected causing the Web Connection server to be shut down and restarted plus refreshing the browser. Note: This feature requires Windows 10 or Server 2012R2+ to work
Consolidated Launch.prg Behavior
Combined various Launch and Environment setup options into a single launcher that can launch your Web Connection applications in a variety of ways. Modes include: IIS, IISEXPRESS,SERVER,NONE. You can simply launch any of the modes with
DO LAUNCHfor the defaults.
Simple helper function that strips the Ole Dispatch error prefix from the front of a COM error message leaving just the actual error message text.
You can create a new
Launch.prgfor existing projects by generating a new project,copying
Launch.prginto your project and changing the configuration variables at the top of the file (usually the project name and virtual). The rest of the file is generic and portable.
Breaking Changes in 7.06
Due to the changes in Live Reload functionality and for consistency the
lLiveReloadServerflag naming has changed. This flag was introduced in
7.05and generated in the
MyAppMain.prgmain program file of new projects.
Make sure to update WebConnectionModule.dll and Microsoft.WebSockets.dll
The new Live Reload functionality is implemented inside of the WebConnection .NET Module in
webconnectionmodule.dllso to use this new feature you need to update that file in all your Web projects. Also a new DLL,
Microsoft.WebSockets.dllhas been introduced to enable the Live Reload functionality.
May 7th, 2019
Release Blog Post • No Breaking Changes • Update Notes
wwHttp now supports String Downloads > 16mb
You can now download data larger than 16mb into strings. FoxPro has a 16mb string limit but with careful usage you can access strings much larger than 16mb as long as the strings are not updated. wwHttp has always supported downloading larger files directly to file and this is just another option that works by default.
wwHttp large File Download Speed Improvement
Changed the wwHttp buffer sizing behavior to dynamically size the buffer depending on the download size. Larger buffers drastically improve download performance of large HTTP payloads easily improving 5 fold for megabyte sized downloads.
Add Option to not Allow Html in Markdown Parser and Function
MarkdownParserclass now have options to disallow HTML markup inside of any Markdown parsed. This can be useful to cut down on possible XSS attack vectors that go beyond the XSS prevention already built into the Markdown parsing process.
wwSFTP Client now fails if renci.ssh.dll is missing
wwSFTP now immediately fails if the SSH library used for the SFTP connection cannot be found on startup. Previously this resulted
Undefined COM Erroron sending - you now get a specific warning that points at the missing assembly.
Updated Weblog Sample Comment Management
Comments are now moderated with an email sent when a new comment arrives, and authenticated users can remove comments in a post or in the main comment list. This fixes a serious SPAM targeting issue with un-moderated spam.
Performance Improvements For Request Processing
Optimized a number of API calls commonly used by reusing API declarations for a number of common operations. Removing repeated
DECLAREcalls on API calls for many often reused functions should trim a little overhead in request processing times inside of the Fox server.
Fix: DLL Naming Problems in New Project Wizard
Fixed bug with New Project Wizard that failed to copy multi-segment named DLLs into the new project folder correctly. Specifically,
renci.sshnet.dllwere truncated to (
renci.dll). Fixed. Please update your project folders with updated DLLs from this release.
No Breaking Changes in 7.05
- There are no breaking changes in 7.05 but as always you'll want to upgdate your DLLs in your projects to the latest from the Web Connection folders. Update the Deploy folder DLLs and the
March 6th, 2019
No Breaking Changes • Update Notes
wwApi ZipFolder() and UnzipFolder()
.NET based folder zip functions that work of source and target folders on disk. Basic zipping and unzipping features only but handles special files and long file names better than the old
Add support for Binary Data to wwXml::XmlToObject/ObjectToXml
wwXML can now serialize and deserialize binary data (of type
Q) to and from XML using base64 serialization.
Allows you to set the SQL Connection timeout globally before a connection is made.
Added a property to control the authentication timeout for the session cookie set for authentication.
GetFileName() and GetDirectoryName() wwUtils Helpers
These methods are similar to
JUSTPATH()except they preserve the case of the input path.
Refactored Server Error Handling
The wwServer class has some updates that simplify how errors are handled, displayed, logged and emailed with dedicated methods that handle these tasks. New methods in include
wwServer::ErrorMsg()that is used to display an error page.
New Project Wizard now copies DLLs to Deploy Folder
When you create a new project, the Wizard now automatically copies all Web Connection dependent DLLs to the Deploy folder, so that running standalone without the IDE and the generated
config.fpwdoesn't cause errors due to missing DLL dependencies. It also makes it clearer that those DLLs have to present for deployed applications.
Fixes to the
Fixed a number of small issues related to how
Launch.prgis generated and started initially when a new project is generated.
January 24th, 2019
Release Blog Post • Breaking Changes • Update Notes
New wwDynamic Class
Added a new dynamic object class that allows for creating or extending objects with dynamic properties that are created as you reference them. Ideal in scenarios where you need to return 'tuple' like object results from methods or where you dynamically need to build up object structures in user code.
Add Launch.prg to Project Template and Samples
New projects now have a
Launch.prggenerated that makes it super easy to start up a Web Connection application from FoxPro. The file supports launching either IIS or IISExpress (if not running it will launch it) and navigate to a default page that you can change. It'll set up default paths, bring up the Web connection server, open the start page for the project. The PRG can be customized for your specific environment and it's a great way to have an easy way to start running your application for the first time.
Setup and New Project Wizard Improvements
Both the Setup and New Project Wizard now show detailed information about how to launch your applications in the FoxPro desktop. Instructions show how to launch your server (via the new
Launch.prg) and what URL to navigate to. Paths are automatically configured. Setup automatically launches the sample application now, the New Project Wizard displays a message on the desktop.
Setup now Prompts for IIS Installation
The Setup wizard now explicitly asks to make sure that you have IIS or IIS Express installed and if not takes you to the documentation with installation instructions. This hopefully prevents people from installing Web Connection when the Web Server is not installed yet.
WebLog Example converted to MVC Style Scripts and Templates
The Sample Weblog Application that ships with Web Connection has been re-written to work as an MVC style application from the original Web Control Framework application. Most of the UI remains the same, but the underlying framework has been switched to use MVC style Models and Scripts to present that Web UI. There have also been a few enhancements including support for Markdown comments, a new Comment editor, and an integrated mechanism to delete comments and posts through the main interface rather than in a separate admin screen. This application is shipped in the Web Connection
wwHttp::AddPostKey() tcExtraHeaders Parameter
AddPostKey()that allows specify extra HTTP headers for multi-part form values posted.
wwHttp .Get(), .Post(), .Put(), .Delete() Methods
Added wrapper methods for specific Http Verb operations for clarity.
HttpGet()was always a misnomer for non
GEToperations and these functions are meant purely for code clarity. They have the same parameters as the
You can now get a list of TLS certificates installed on the local machine to potentially pass to requests.
wwHttp::lDecodeUtf8 to automatically decode UTF-8 Content
Added a new wwHttp::lDecodeUtf8 property that is
.t.by default to decode UTF-8 content based on the
wwCollectionto allow for finding elements by their value. You can now search any type of element including objects. New
Set()property allows setting a value if it exists or add a new one if it doesn't. A new
RequiresUniqueItemsproperty allows collections that can't have duplicate values. The
Item()method fixes a few scenarios where non-matched items would fail and now return null.
wwUtils GetRelativePath() Function
Added a new function that returns a relative path. Unlike
SYS(2014)this function returns the path in proper case.
wwUtils SaveFileDialog() and OpenFileDialog() Functions
Save and Open file dialogs that unlike
GETFILE()return the filename and path in proper case so files can be saved and retrieved by their actual on disk filenames.
Rounds out routines to write out Json values as string in addition to
All Web Connection DLLs and EXEs are now digitally signed
Web Connection is now built with a proper build process that builds the entire product in an automated fashion. Previously some parts were using this automated process but it has now been fully automated. As part of that process all West Wind DLLs and EXEs and Setup files are signed with a digital signature to allow verifying authenticity. This will also make it less 'scary' to run the installer for the first time if Windows SmartScreen is is enabled.
Breaking Changes in 7.02
- wwResponseFile.prg and wwResponseString.prg Consolidated into wwResponse.prg
Consolidated the legacy response object classes into the single
wwResponseclass file which now contains all three of these classes. This removes two additional files from a base install. These objects are now only used as pass through objects proxying for
wwPageResponsethat's used for all actual Request object operations.
To update: You'll get compilation errors for missing files - just choose remove when prompted to remove them from the project.
November 16th, 2018
Release Blog Post • Breaking Changes
Template Updates to BootStrap 4 and Upated Support Libraries
Overhauled the default project templates to use Bootstrap 4 and FontAwesome 5 and updated overall styling to be more up to date. Updated related components like the date
HtmlDateTextBox()to use tempusdominus-bootstrap-4 date picker control. Helpers support both Bootstrap 3 and 4, via a compiler switch
BOOSTRAP_VERSION 4. There have been many tweaks and updates to the styles for cleaner rendering and a number of new support styles have been added.
Fix: Remove hardcoded Content Page Paths from Scripts
Changed the generated PRG output for content pages so that the content page path is no longer hardcoded into the page code. This fixes issues where if a compiled FXP was moved to a new location it would fail due to an invalid template path. Updated code provides the content page path up the call stack and persists it into the layout page.
Updated Visual Studio Templates and Intellisense Snippets
We've created 20 or so Intellisense snippets (Ctrl-k-x -> My Html Snippets -> Web Connection) that let you quickly inject common Web Connection and Bootstrap controls/components into the page with minimal effort. We also provide Visual Studio Code Page Snippet templates for Layout, Content and Standalone pages.
Visual Studio Code Web Connection Code Snippets
We've added a number of helpful code snippets for Visual Studio Code for inserting blocks of code for common Web Connection components in scripts and templates are available. Type
wc-in the editor to see the VS Code snippets.
Generic Markdown Page Rendering
New projects now include the ability to render any Markdown page with an
.mdextension and render it into HTML. You can simply drop a Markdown file into a folder add any dependent images and have that page rendered. A custom
Markdown_Template.wcstemplate can be customized to provide custom page layout for site chrome to match your site's identity.
<% %>Scripting inside of
You can also use script and expression tags inside of Markdown blocks to effectively script Markdown text.
Updated Markdown Island Support in Scripts and Templates
Web Connection has support
<markdown></markdown>tag islands into which you can put Markdown text that is rendered as HTML for a while. Previously you had to left align the Markdown content. With this release Markdown content no longer has to be left aligned, rather the parser detects the common space before all lines and strips it.
New Projects automatically create local Git Repository
If Git is installed locally, the New Project wizard now automatically creates a Git repository in the new project and creates a first commit. You can easily continue committing and always roll back to the initial install. If you don't like the git repo - remove the
.gitfolder and it's gone.
All authentication releated Process properties -
cAuthenticatedUserName- now explicitly call
OnCheckForAuthentication()if it wasn't previously called, ensuring that authentication is always checked when accessing these properties. Previously you had to explicitly call
OnCheckForAuthentication()which is no longer necessary. A new internal flag ensures that authentication is checked only once on repeated accesses as it accesses the session store to check or retrieve the auth token.
Updated wwUserSecurity logic to automatically create
.oUserSecurityand .oUser` objects on each requests. When accessing these objects Web Connection checks to see if they already exist and if not they are created. If a user is not logged in, an empty oUser record is created and you can check for an empty user with oUserSecurity.IsEmpty().
wwUserSecurity Password Encryption Improvements
wwUserSecurity will now automatically encrypt a password that's not already encrypted if
cPasswordEncryptionKeyis set to encrypt passwords. You can now add a non-encrypted password into the file, and next time the user is authenticated the password will be encrypted and written into the database in encrypted form.
wwUtils.SanitizeHtml() to sanitize HTML strings Added a new SanitizeHtml() function to wwUtils to strip scriptable code out of HTML text. Useful for cleaning up user captured HTML or Markdown text to prevent XSS attacks from user input. Requires .NET.
Response.ExpandScriptAsString() and Response.ExpandTemplateAsString()
These two functions can now be called to parse a script or template and return the output result as a string rather than writing output into the Response stream as complete pages. Render pages or partials into HTML and use them from process class code directly. Although we recommend using scripts and templates along with Partials to do embed external templates, it can sometimes be useful to 'call' a partial component directly from code. For example a Login Partial component might be rendered into non-script pages and can just be embedded as a string. These functions are mere wrappers around
tlReturnAsStringparameter - they are provided for easier syntax and better discoverability.
Update Project Template and Add HelloScript Request
Add a new script page to the default template that demonstrates running a request using MVC style development by using the a script page with code behind. The script page renders the current request list, displays a message alert box and describes several aspects of the MVC process.
Add BrowserSync.prg to new Project Template
New projects now get a
Added a method that can produce HTML output from an RSS Feed. The method is customizable with a
HtmlRssFeedConfigthat allows control over number of items retrieved and a number of formatting options for the feed.
New File Upload Samples
Removed the overly complex plUpload component from Web Connection and instead provided simpler pure AJAX examples as well as a simpler and much more modern uploader called Uppy. There are simple file upload samples, and an example of uploads displaying in an image carousel.
wwPdfPrinterDriver PDF Printer for wwPDF
Added a generic PDF driver that can be used with any printer driver that outputs to PDF including the built-in Microsoft Print to PDF driver in Windows 10 and Windows Server 2016 and later. This driver handles report printing, capturing and waiting for the output file from the print spooler and dealing with unattended mode issues when running in COM modes.
wwDotnetBridge - Automatically unblock DLL
Added logic to automatically unblock
wwDotnetBridge.dll. This should help with many common loader error issues.
Improved Error Message for wwDotnetBridge Load Errors
wwDotnetBridge has a few rules required in order to run it - specifically related to Internet downloaded-loaded DLLs and loading from a network. Updated the loader error message with common causes and link to documentation.
wwDotnetBridge Fixup for List
Added additional support for
List<T>return values to
GetProperty()results, which returns these values as a ComArray now.
wwDotnetBridge Support for Creating Generic Types
You can now create generic .NET types like
Dictionary<t,t1>. A new method on
ComValue::SetValueFromCreateGenericInstance()allows you to create a generic type on the
ComValuestructure. Since generic types are not directly accessible from FoxPro (no support for COM interfaces on generic types) interfacing with these types always goes through ComValue and indirect ac
Added method hook that is called after a user is logged out. This is useful for removing additional application specific state that might be saved in session or other application data stores.
wwProcess::InitSession(): New llSecure parameter
You can now specify that the Session cookie created can only be used under HTTPS via the
llSecureparameter. This translates to the
Secureflag of the cookie created.
wwUtils GetFullPath() Function
Function that resolves a relative path to a full path but also matches the proper case of the file on disk if it exists.
Breaking changes in 7.0
Bootstrap 4 and FontAwesome 5
Web Connection switches default templates to Bootstrap 4 and FontAwesome 5 (free). Bootstrap and Fontawesome syntax have changed somewhat for these new frameworks. These changes don't affect any existing applications, except for: the
HtmlErrorDislay()which are affected by the changes. If you need to use the old version of Bootstrap use the
wconnect_override.h. If you decide to upgrade applications to Bootstrap 4, most bootstrap concepts work, but there are number of differences you have to account for. The list is long but in Web Connection's own templates only very few things were affected mainly panels (cards now) and wells (also cards).
wwSql and wwXml Classes now are PRG classes
We've switched wwSql and wwXml to run as PRG classes in order to simplify distribution and compilation. You will need to update your project references to the PRG files and any declarations from
SET CLASSLIB TOto
SET PROCEDURE TO. You should just be able to do Replace in Files in your Favorite editor or explicitly use GoFish to find and fix up any references to wwSql or wwXml.
wwBusinessObject replaces wwBusiness as a PRG class
wwBusiness.vcxwith a PRG based version called
wwBusinessObject.prg. Unlike the wwSql and wwXml classes, we've explicitly renamed the PRG and class to
wwBusinessObject. The old version will still be available in the
OldClassesfolder for those that need visual classes but any new development will be made only on
wwBusinessObject. To replace search for any references to
SET CLASSLIB TO wwBusinessand replace with
SET PROCEDURE TO wwBusinessObject. Find any class references to
AS wwBusinessand replace with
AS wwBusinessObject. If you are using a VCX based subclasses of
wwBusinessyou have to continue using old wwBusiness.vcx unless you explicitly migrate the visual class to a code class - you can do that easily with the VFP Class Browser export feature. I suspect the same is true for most applications.
Comment or report problem with topic