Colleagues,
That "Installation Blues" continues. This time it's inability to let the User select the location whereHe wants to put the application on Her/His system (and that's just for starters).
Here's the picture ("sensitive info" redacted ):
the problem I have is that I can't set the destination disk to, say, D:\, or E:\, let alone to a specified dir on these drives because my WS has them not.
And if I try to enter to Installation Folder URL something like .\MyProgramName\ I get this error message:
And, Ladies and Gentlemen, how can I know what system configuration my potential consumer has?!
IOW, I dunno how to let the User select the installation target location.
Moreover: when I copied the installation files into the server box (from where a Client's Sys Admin would want to install it on WSs) and ran Setup.EXE, I got an error message with the following line:
"You cannot start application OD_Tools_2022 from location file:///D:/Program%20Files/Ceridian/OD_Tools_2022/OD_Tools_2022.application it is already installed from location file:///Z:/Ilya_Docs/Projects_and_Programs/VS_2019_Projects/ODS/OD_Tools_2022/bin/Release/OD_Tools_2022.application. You can start it from location file:///Z:/Ilya_Docs/Projects_and_Programs/VS_2019_Projects/ODS/OD_Tools_2022/bin/Release/OD_Tools_2022.application or you can uninstall it and reinstall it from location file:///D:/Program%20Files/[CompanyName]/OD_Tools_2022/OD_Tools_2022.application. If you reinstall the application, be aware that you might lose any customizations that you made to the application."
(FYI, drive Z: above is my WS's C: drive.)
Is there anything in the VS 2019 VB.NET Publishing thingy that allows the Developer to get around this roadblock?
Please advise!
Regards,
Ilya
That "Installation Blues" continues. This time it's inability to let the User select the location where
Here's the picture ("sensitive info" redacted ):
the problem I have is that I can't set the destination disk to, say, D:\, or E:\, let alone to a specified dir on these drives because my WS has them not.
And if I try to enter to Installation Folder URL something like .\MyProgramName\ I get this error message:
And, Ladies and Gentlemen, how can I know what system configuration my potential consumer has?!
IOW, I dunno how to let the User select the installation target location.
Moreover: when I copied the installation files into the server box (from where a Client's Sys Admin would want to install it on WSs) and ran Setup.EXE, I got an error message with the following line:
"You cannot start application OD_Tools_2022 from location file:///D:/Program%20Files/Ceridian/OD_Tools_2022/OD_Tools_2022.application it is already installed from location file:///Z:/Ilya_Docs/Projects_and_Programs/VS_2019_Projects/ODS/OD_Tools_2022/bin/Release/OD_Tools_2022.application. You can start it from location file:///Z:/Ilya_Docs/Projects_and_Programs/VS_2019_Projects/ODS/OD_Tools_2022/bin/Release/OD_Tools_2022.application or you can uninstall it and reinstall it from location file:///D:/Program%20Files/[CompanyName]/OD_Tools_2022/OD_Tools_2022.application. If you reinstall the application, be aware that you might lose any customizations that you made to the application."
(FYI, drive Z: above is my WS's C: drive.)
Is there anything in the VS 2019 VB.NET Publishing thingy that allows the Developer to get around this roadblock?
Please advise!
Regards,
Ilya