my application have tray icon. when i uninstall it
i have window with the proposal to close the "my_tray_app.exe" - with text: ("The following application should be closed before continuing the install")
i'm use wix "CloseApplication Element (Util Extension)" to close "my_tray_app.exe" win close app
HOW TO AVOID THIS WINDOW??
i try play with CloseApplication attributes - but don't have result... oO
i'm use wxWidgets and use following method to close my "TrayApp.exe":
<util:CloseApplication Id="CloseApp" CloseMessage="yes" Target="TrayApp.exe" RebootPrompt="no" />
<Custom Action="WixCloseApplications" Before="RemoveFiles" />
but "TrayApp.exe" stay on taskmanager and stay on system tray!
if i try close other tray app (for example "Skype.exe") all work fine and my uninstaller closes "Skype.exe" and remove from system tray.
may be i must add some code to my project?
i try use taskkill.exe - but "TrayApp.exe" removing from taskmanager but stay on system tray until i move the mouse pointer to tray icon.
To close the Trayapp at the time of uninstall you need to write a custom action with taskkill.exe.This custom action will kill the Trayapp and then uninstall the application.
Related
I am trying out Blazor and i do not understand why when changing a component after refreshing the browser page it does not update ? Shouldn't the client update itself similar to how angular does?
It only refreshes when i restart the blazor server.
Index.cshtml
#page "/"
<h1>Hello, world!</h1>
If i change lets say the text inside the <h1> to Hello people , i save the project and i refresh the page ( as i am advised in the Blazor tutorial) shouldn't i see Hello people ?
After Asp.net Core 3.0, Runtime compilation is enabled using the Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation package.
To enable runtime compilation, apps must:
Install the Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation NuGet package.
Update the project's Startup.ConfigureServices method to include a call to AddRazorRuntimeCompilation:
services
.AddControllersWithViews()
.AddRazorRuntimeCompilation();
or
services.AddMvc().AddRazorRuntimeCompilation();
I guess you are running the app with the debugger connected? this prevents the recompilation. You need to:
Press Ctrl-F5 to run the app without the debugger. Running with the debugger (F5) isn't supported at this time.
https://github.com/dotnet/aspnetcore/issues/5456
You should add or enable runtime compilation in razor pages,
Install-Package Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation -Version 3.1.6
After installing set the startup file as ,
services.AddMvc().AddRazorRuntimeCompilation();
do the following:
Install the Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation from NuGet.
Update the ConfigureServices method in the Startup class to look like below:
services.AddControllersWithViews().AddRazorRuntimeCompilation();
You good to go.
If you go into Tools > Options > Keyboard and search in the "Show commands containing" search box search for "BrowserLink". Find the option that says "OtherContextMenus.BrowserLink.RefreshLinkedBrowsers" by default this is set to CTRL+Alt+Enter. Click "Remove" and then select the "Press Shortcut Keys" input and press Ctrl+S. Next (just to the left of the input) change Use new shortcut in "Global" to be "Text Editor". Click "Ok" until the window has closed. Now Visual Studio shares CTRL+S with both Saving files and Refreshing linked browsers.
(This will only work if your text editor .cshtml, .css, .js, etc. files in the edit window are the active selections) WARNING: if you don't set it to something other than global then it will override the shortcut for Save and you won't be able to save your files.
Adding "services.AddMvc().AddRazorRuntimeCompilation();" and installing the Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation package 6.0.5 will fix the problem but it will ruin the "css isolation". The first thing you will notice is that the footer will lose its position
After updating to Pycharm 2017.2.1 I got this Flow Tool panel (although not having flow installed) which pops up and I can not get rid of it.
This appears to be a bug. A workaround is mentioned:
edit .idea/workspace.xml and remove the
<component name="JsFlowSettings">
...
</component>
section
Another workaround which seemed to work for me:
select Flow under [file/settings/languages&frameworks/javascript] as Javascript Language version and untick all flow settings options that then appear.
In my Event Log in Intellij IDEA 2016, I used to see this message:
Unlinked Gradle project?
Import Gradle project, this will also enable Gradle Tool Window.
Don't want to see the message for the project again: press here.
At some point, I clicked on the "press here" link indicating that I don't want to see the message again. Since then, I have decided that I'd like to see it again.
How do I start seeing this Event Log message that I chose to not see again?
You can re-enable notifications balloon popups and logs from the (obviously) Notifications settings window, which you can open in (at least) 2 ways:
1) From the Event log window click on the settings button
2) File -> Settings -> Appearance & behaviour -> Notifications
I just tried the specific notification that has been asked about (Unlinked Gradle Project?). The only way that I found to re-enable the notification was to delete the .idea folder inside the project and re-open the project in Intellij.
Other notifications, such as Maven: non-managed pom.xml work as expected so this bug is specific to the Unlinked Gradle Project? notification.
This appears to be a bug in Intellij Idea as of this build:
IntelliJ IDEA 2016.2.5
Build #IU-162.2228.15, built on October 14, 2016
JRE: 1.8.0_112-release-287-b2 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
I have raised an issue for this : https://youtrack.jetbrains.com/issue/IDEA-162936
Also, I found that these notification settings are not stored in a project specific file. This file, on OSX, is ~/Library/Preferences/IntelliJIdea2016.2/options/notifications.xml, on Windows it would reside in a folder according to this.
These were the contents of the file for me, when I was testing this notification:
<application>
<component name="NotificationConfiguration">
<notification groupId="Gradle Notification Group" shouldReadAloud="true" />
<notification groupId="Maven: non-managed pom.xml" displayType="STICKY_BALLOON" shouldLog="false" />
<notification groupId="Project Startup Tasks Messages" displayType="STICKY_BALLOON" />
</component>
</application>
I noticed that changing the Popup Type for 'Gradle Notification Group' correctly updates ~/Library/Preferences/IntelliJIdea2016.2/options/notifications.xml, however even when the Popup type is 'BALLOON' or 'STICKY_BALLOON', it does not result in Intellij re-notifying the user about the Unlinked gradle project.
I'm in a kind of misery. I got an installer installing and starting a tray icon app (common .exe)
This is working properly, but now i want to stop that app before this UI telling the user to close the app manually comes up, because during the deinstall routine, my tray icon is removed but the process is still running.
I applied this custom action to close the app before uninstall (or even during)
<CustomAction Id="CloseTrayApp" ExeCommand="-exit" FileKey="TrayApp" Execute="immediate" Return="asyncNoWait" />
<InstallExecuteSequence>
<Custom Action="CloseTrayApp" Before="InstallValidate" />
</InstallExecuteSequence>
But the "close all running apps" dialog still pops up, but i thought that this will solve my issue.
I already tried to use the CloseAction but i got into a hurry using it because of error while compiling the stuff. It says that the WixUtils namespace may be missing but i double checked that it is there:
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension"
How can I avoid the dialog window poping up and trigger this custom action to be executed?
You also have to add a reference to WixUtilExtension.dll. If you are using Visual Studio / Votive you just right click add reference and select the DLL from [ProgramFilesFolder]Windows Installer XML v3.5\bin. Otherwise you have to make the extension available to the compiler and linker:
candle.exe yourfile.wxs -ext %full path to WixUtilExtension.dll%'
light.exe yourfile.wixobj -ext %full path to WixUtilExtension.dll% –out yourfile.msi yourfile.wixout'
More information can be found at:
Using Standard Custom Actions
Please note that the CloseApp custom action has a limitation that it won't "terminate" your application. It will only politely send your app a WM_CLOSE message and it's up to your trayapp to receive and process that message with a shutdown.
I'm trying to close a process before uninstallation using Wix. I've confirmed that it works as long as there's a visible window, but if there isn't a visible window (which is the case most of the time with this app since it's a system tray app), the uninstaller just hangs, and eventually continues with the uninstallation, leaving the process running.
According to this forum post, it seems like Wix has had trouble closing minimized apps in the past, so I wonder if this is related?
Any suggestions as to what else I can do to make sure the process gets shut down? Is there any way I can try and capture the message in my app using the Win32 api maybe?
Here's the CloseApplication declaration:
<util:CloseApplication Id="CloseApp" CloseMessage="yes" Target="App.exe" RebootPrompt="yes" />
And here's the custom action:
<Custom Before="InstallInitialize" Action="WixCloseApplications">REMOVE = "ALL"</Custom>
It looks like you are scheduling the WixCloseApplications custom action before the installation transaction. The way the custom action works, is it scheduled a deferred action that actually closes the applications. It can't do that work unless it happens during the transaction (After="InstallInitialize").
The fix is probably pretty easy. Remove the Custom/#Action="WixCloseApplications" element.
At first, don't forget to reference WixUtilExtension.dll assembly.
Also check if Wix element contains definition of UtilExtension namespace:
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:util="http://schemas.microsoft.com/wix/UtilExtension">
I've noticed that you should change your custom action to be executed before InstallInitialize.
<Custom Before="InstallInitialize" Action="WixCloseApplications">REMOVE = "ALL"</Custom>
If you apply those changes and CloseApplications extension doesn't work, try logging installation process using
msiexec /i MyApplication.msi /l*v MyLogFile.txt
I also faced this problem.
Changing the Before attribute to "InstallValidate" worked for me.
<Custom Before="InstallValidate" Action="WixCloseApplications"/>