|
|
Rank: Newbie
Groups: Member
Joined: 1/8/2019
Posts: 2
|
I'm using a trial version of eo.webcontrol, a test desktop application was built and is being used since late November (using a 2018.1.x.x revision of the EO.WebCotrol),
today the application behaves very strange (first time used in this year). The login screen is opened, but after entering credentials the application seems to be killed, either by Windows10 or by the application itself.
Is this a EO.WebControl protection? The application runs fine within Visual Studio
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,070
|
No. This should not have anything to do with any protection/license. Can you try the latest build and see if it works for you? Also when you say it runs fine within Visual Studio, do you mean that it runs fine within Visual Studio on the same computer, or on a different computer?
|
|
Rank: Newbie
Groups: Member
Joined: 1/8/2019
Posts: 2
|
quick response, the issue was a kind of silent exception that was killing the application without showing any notification from Windows 10.
Long answer: It runs within VS but it was being killed (now I see it was more a crash) as an stand alone executable on the same PC. Tried the newest revision but was not the problem within the eo.webcontrol.
Thanks for the support.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,070
|
Hi, Please enable EO worker process and see if it resolves the issue for you: https://www.essentialobjects.com/doc/common/eowp.aspxThanks!
|
|