@Sean and Servoy,
Thanks for the webinar about the migration today.
I just followed up by starting the migration of a ng client to ng2 titanium following the guide (Migrating to NG Titanium - Servoy Guides).
I do not have table view or lists so the changes were to the styles for custom servoy theme and the main style file.
Set the preferences as per the guide.
All packages and latest servoy release (2022.03.3742).
The project cleans and builds correctly.
Try to run the Ng client form the IDE - get a 404:
The requested resource [/solution/myProject/index.html] is not available
those logs don’t say anything
if you want to see if Titanium NGClient builds correctly then you need to look at your Console View
and that has now an extra Console page (Titanium NG Build Console) there you see everything the TiNG outputs when building
that needs to have at the end something like this:
Generating index html…
√ Index html generation complete.
So that sounds like a borked npm install, but that is very weird, we ship it and we don’t use anything of the system (as far as i know) and it should just find that npm we start…
what you can try is to exit developer
then delete:
No npm or node when try in command prompt.
The directory listing for the modules does not have semver - see the listing file atached.
I am guessing it is a partial module download.
Maybe that happened when I tried to update the Servoy version and it failed or partially worked?
I will try your suggestion of deleting that directory and rebuild.
that seems an half way install
maybe you exit a developer at the time he was unzipping that in that dir…
and come to think of it, that maybe can happen quite easily
because when you update your developer, you get all the new plugins
then after restart you get another update (for application_server) that also says restart once more
that is often quite fast… So if you directly do restart and it was in the middle of unzipping maybe that will result in a half unzipped npm
The rebuild after deleting the directory took a long time (see attached).
But still got errors and will not launch the client.
Perhaps I should abandon the whole upgrade and download latest Servoy release again …all over again…
I downloaded the latest Servoy release to a new folder and selected the same workspace for my app.
This time that directory does show up.
The Titanium build console is attached and still gives errors.
I am guessing that some of the Servoy modules that are not Titanium upgraded might be causing the issues.
In the package manager these are the module/packages versions not prefixed by 2022.03.x
Servoy Ng Grid Services
Block UI
SvyLookup
SvyNavigation
SvyPopupFilter
SvySearch
SvySecurity
SvySecurityUx
SvyUtils
Drive Z is a network drive. That is where the workspace exists. It is fine for older NG.
I run the Servoy developer from drive K: (local SSD).
I changed the ini to the sample as you suggested but got same errors.
Got error message (-4094 from npm) as per attached.
Looks like it cannot create the symlink.
Looking at the log file there seems to be a reference to 2021.12.0 (line 34) - but this is 2022.03.0 - is there a mix up in directories someplace?
Maybe I should clear the npm cache and retry?..Nope same error.
For my next experiment I exported the app (.servoy).
Then created a new workspace.
Imported the .servoy.
Changed the preferences to run ng client as titanium.
After waiting for he titanium build to complete (with various errors/warnings) I ran the ng client (debug) and it works now.
I conclude that having the workspace on a drive that is a network drive breaks the npm in some manner (maybe permissions?).
Got error message (-4094 from npm) as per attached.
Looks like it cannot create the symlink.
Looking at the log file there seems to be a reference to 2021.12.0 (line 34) - but this is 2022.03.0 - is there a mix up in directories someplace?
Maybe I should clear the npm cache and retry?..Nope same error.
Don’t think this has anything todo with npm cache or something
this has everything todo with npm wanting to create symbolic links (called Junctions in windows) and on that drive the OS/network doesn’t allow that
We depend on this that npm can do this.
pitc:
For my next experiment I exported the app (.servoy).
Then created a new workspace.
Imported the .servoy.
Changed the preferences to run ng client as titanium.
After waiting for he titanium build to complete (with various errors/warnings) I ran the ng client (debug) and it works now.
I conclude that having the workspace on a drive that is a network drive breaks the npm in some manner (maybe permissions?).
what kind of errors do you still get?
what does the console output still look like?
Also what i don’t get is if you use this:
-Dservoy.ng2.target.folder=c:/temp/target
(point to a normal ntfs filesystem drive on your local machine)
that it then still doesn’t work, that should work fine, where the workspace is shouldn’t be a problem i think, its where that target dir is
So what is the output you get when you have that system property set?
I deleted all sub-folders below c:\temp\target because of a previous attempt (otherwise it will not re-build).
With the ```
-Dservoy.ng2.target.folder=c:/temp/target
See attached log file.
Without that line, it attempts to use Drive Z and fails.
I can try with a different drive (e.g. K: where the servoy release is located.
[ti_build_console_5.zip|attachment](upload://q2K6cM0B9XGvjTtRFNi0vZppTvP.zip) (23 KB)
