Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Using a WiseJ web application csproj file rather than the one generated for a WinForms app
  • Using a WiseJ startup code file rather than the one generated for Winforms
  • Adding appropriate Deploying a few supporting files to the folder (default.html, default.json, web.configs) using a user batch command 
  • A number of tweaks to the code to address places where WiseJ conventions differ from WinForms

For the this first test, I simply used the gmPL post editor -editting commands make the changesreplacements.  (see “Quick and Dirty” rules below)

In an actual upgrade solution, I would create a generalized WiseJ upgrade configuration that could be used with many different VBPs and forms code files and also develop a set of rules files to deal with third-party controls.  In a project context, we would further customize this the rules so that various customer-specific requirements are automated including such as other WiseJ/.NET standards.

...