When deploying an application with Payara in a browser via Applications --> Deploy, the Status box is always checked by default, so it's Enabled. Is it possible to change this behavior so that the box can be set to be disabled by default instead? It's very easy to miss and not uncheck it when manually deploying applications; and in some scenarios this can cause me problems as a result when I need an application to be deployed, but not enabled.
The closest thing I can find is a setting to disable this for auto-deploying applications (Domain --> Applications Domain --> Auto Deploy), but this is for files placed in a certain folder on the file system, not deployed with the web UI.
Related
I have a WPF application that will deployed using InnoSetup (and so presumably will not be a ClickOnce application) that stores user settings with the built-in settings under Properties in the Visual Studio project. I need that the user settings are preserved after each update.
However I have found that if the assembly version changes then the app overwrites the user settings.
In this article (https://msdn.microsoft.com/en-us/library/ms228995.aspx?f=255&MSPPError=-2147217396) it explains for non-clickOnce applications the user settings are stored in the 'Documents and Settings' folder (which is OK), however this is not the case for my project - Is there a setting somewhere in the project so I can declare it a 'non-ClickOnce' application and so therefore get the settings to appear somewhere accessible?
Secondly, I would like that the settings are updated according to that article linked above, will this happen for non-ClickOnce applications?
I am trying to create a couple of resident instances on a google app engine app hosted on appspot.com. I moved the idle instances slider from Auto down to 2. My understanding is that this will then create two "resident" instances and I should see those marked as Resident instead of Dynamic in the instances screen. But it isn't working, I am still only seeing 1 dynamic instance (this is a test with no traffic).
When I made and saved the idle instances change, I noticed what to me was a new option underneath that section, as follow :
Performance Settings Migration for Modules
Before you can modify performance settings across Modules, your
settings must be migrated. After the migration, performance settings
will be managed at the Module level, and changes must be made through
your app.yaml (Python) or appengine-web.xml (Java). Copy the settings
clause below to the appropriate file to preserve your performance
settings during the next update.
There is a button under this new section called Migrate Settings. When I click this the main screen just blanks, with the admin console menu options still available on the side. All very peculiar!
It also gives some setting for python and java to do the idle instances down to 2 change at the module config level. I stuck this into my appengine-web.xml and re-deployed but I am still only getting one dynamic instance.
Has anyone any experience of this "migrate settings" option?
I have a C#/WPF app that uses ClickOnce for deployment. There is a scenario where the app needs to restart (the user changes a database). I do it by:
System.Diagnostics.Process.Start(System.Windows.Application.ResourceAssembly.Location);
System.Windows.Application.Current.Shutdown();
After restart, it seems that the app has issues:
The version becomes 1.0.0.0.
The current database setting is set to default (it is in the application's Properties.Settings).
I don't know that I fully understand the question, but I do know there is an issue with the method you are using to restart the application if it is a ClickOnce application. When you restart the application this way, ApplicationDeployment.IsNetworkDeployed will be false. See this post for a full explanation: http://bit.ly/RKoVBz.
I haven't verified the proper way to restart the application yet, but I'll update this a soon as I do.
The Coded UI Test Builder fails to recognize Silverlight controls when the application (XAP) source is a different domain
I placed XAP at two different locations
http:\Domain1\MyApp\MyApp.XAP
http:\Domain2\MyApp\MyApp.XAP
My WebPage is at http:\Domain1\HomePage.html
If the Silverlight object's source is set to 1st one (same domain) it works fine and CUIT builder recognizes, records and playbacks properly. But, when I set the source to 2nd one (i.e. different domain), the CUIT builder fails to recognize Silverlight app.
The application itself work fine when hosted at Domain1 or Domain2. The recording is also successful when web page at DomainX refers to app at same DomainX. It fails to record when web page at DomainX refers to the same app at DomainY. What do I need to make it work?
Thanks
PS: Please note that the Silverlight application itself works fine no matter from which domain I am using - I have appropriate crossdomain policy file available and enableHtmlAccess set to true.
I have also verified presence of automation helper dll in XAP at both places (infact same XAP has been placed
I had logged this bug on MSDN connect - Coded UI Test builder fails to recognize Silverlight controls in cross domain XAP
This has been marked as "Won't Fix":
"We have investigated this scenario and determined that cross-domain XAPs cannot be supported by Coded UI Test. We use CreateFromXAML apis to enable the UI Testing component for Silverlight and
this API is failing for cross domain XAPs. Unfortunately, we have not been able to identify a workaround either. Closing the bug as Won't fix"
We have a requirement to start a WPF application with specific parameters from a link in a browser.
We are wondering if this is possible?
As an alternative could we embed the web application in a WPF browser control, and read the values out of the html web page?
Several possibilities :
if you control the browser (i.e. if you are in an intranet scenario, and have the opportunity to deploy applications), you can :
create an activex or plugin that runs the application
register a new uri scheme to interpret the url of kind "yourapplication://yourarguments"
(complex): deploy a listening app ran under the user session, and from the webapplication, ask this listening app to run the target application
reduce the security of the browser (not recommended)
if you don't control the browser:
create a clickonce application... this involves a setup, but which does not require admin privilege
Moving to Silverlight also might be an option, depending on your needs. SilverLigth V5 (still in beta) notably adds the ability for an admin to control the rights of the application via a GPO
Note: My feelings is the later option (Silverlight) is far more preferable because it's a lot more cleaner and less security hole factor. However, it can only be done if your requirements fits into the SL features
It is not possible to call client app from a browser, previously it was possible from activex controls but for that you need to have a signed library, in wpf you can make browser based application but you cant embed your web app in it.
So partially you are correct if you used wpf app you will be able to launch application on client side but with browser it seems difficult until unless you make activex control
but still i am not 100% sure that with activex control you will be able to launch the app or not