When, in Visual Code with the Pymakr extension, one sets the development mode to automatically synchronize any change in the local files with the device, Pymakr reboots the device every time a file is saved.
How can I prevent this behaviour?
Important: Not looking for a workaround. I do not want the reboot to happen at all.
I have googled for it
I have checked the Pymakr extension settings and the settings.json
PD: I can't undestand why this is not an option in the extension (or, maybe, I did not find it?)
Related
Question is what steps can I take to debug this?
It does very occasionally auto-save itself, but not on change of active window as previously. I can't yet reproduce a specific cause of this (very occasional) autosave.
I have all auto-save options as per default:
I recently did brew upgrade including fswatch. Would I be right in assuming IntelliJ would use its own though, not brew's fswatch if installed?
Another possibility is it's a Mac OS Privacy thing; a Catalina update seems to have broken one program which expected disk access to be available, now it's not; not sure if Intellij has lost some kind of OS permission to do (auto) saves(?), while this doesn't affect a user issued command to save, which works fine.
I have an Installscript installer. When I run it to update the product and parts of the product are running, then a reboot is required. -- This is ok.
It turned out that in case of a reboot all files are copied properly, but a configured self-registration does not take place -- not during installation, and not after the reboot.
I have checked the setup.ilg file and it tells me no news: files are copied, and self-registration appears to have been done.
When I close programs to prevent the necessity of a reboot or when I install the first time everything is ok.
Can you explain why the self-registration does not happen and what I can to to make it happen? Thank you!
Stein asked me to weigh in on this.
Honestly, I haven't touched InstallScript project types since 2003. But I can take a guess at what is happening. I would imagine that the locked file causes MoveFileEx() to use the PendingFileRename operation pattern and that self registration isn't happening because the DLL isn't where it needs to be yet. Something would have to happen after the reboot to call LoadLibrary/DllRegisterServer() after reboot when the file is now in it's final resting place.
Why isn't this happening automatically? I have no idea. I did a quick google search and did find this article:
http://helpnet.installshield.com/installshield19helplib/Subsystems/installshield19langref/helplibrary/LangrefXCopyFile.htm
Unfortunately my corp firewall is blocking me from accessing it. Based on what Google showed me it sounds like you might have a workaround by using XCopy function to handle this.
Honestly though I only do MSI projects any more and you could also take a move out of that playbook by harvesting the COM meta data and applying the registry data yourself so everything lines up after the reboot.
COM Extract at Build: Maybe try to enable COM Extract at Build to eliminate the need for self-registration? Please see this answer: Failed to run script function from Custom Actions. Essentially the option is hidden in the property page for each component.
Is this perhaps an old-style, legacy installer that is not MSI at all?
https://helpnet.flexerasoftware.com/installshield24helplib/helplibrary/IHelpCompRegDynamic.htm
InstallShield communties:
https://community.flexerasoftware.com
http://forum.installsite.net
I use Android Studio 0.8.6 for Android Development, and when I'm editing a file, it will freeze, and I have to restart computer to close it, since System Monitor (I am on Ubuntu 14.04 LTS) won't close it. It's always the same file I'm editing, this never happens with any other file. It shouldn't matter, but the name of the file is sun_vertex_shader.glsl. There's no error, or log output, or anything.
Here's exactly what happens - I'm typing in the file, the cursor freezes, stops blinking, and the mouse pointer is an I-beam, no matter where in the window I move it. The window doesn't close when I press the X, and when I restart my computer and open Android Studio again, I start editing the file and seconds later, it happens again.
I know you probably can't help me without any error logs, but I couldn't find any. If you know where I could find them, I will post them here.
I found out what is causing this: the GLSL plugin I downloaded from here is causing Studio to freeze, as I have read in the comments.
Please check your system Date/Time and correct it, this problem occurred if your system date does not match with current date.
I need to automatically update the software I've included with my WinPE image, but whatever changes I make to the flash drive don't stick after reboot. It updates successfully, but the files that I've copied get deleted and the old ones somehow come back after I reboot, forcing the updater to run again.
What do I have to do to get changes made to x:\ to stick, or is it even possible?
I don't see where this has been asked anywhere else so forgive me if someone has already gotten the answer to this.
What I've done is; instead of making changes to x:\, the software will find the drive's volume number by its name through a batch script, then compare a version.txt on the flash drive with a version.txt on the server. If the version on the server is newer, it downloads an updated boot.wim to the WinPE sources folder and restarts.
I have a VB.NET ClickOnce application that I am trying to install on my computer. Previously, I was able to install and run these apps without issue. Now when I install the application, I can see the flash of a window opening, and then nothing. (There are also no processes left hanging or anything when viewed with the task manager.)
After some digging around I noticed that there are files in my Temporary Internet Files with names like "FusionBindError" and then my application name and different DLL names.
I have done everything I can find on the net to do, reinstall applications, reinstalled the .NET Framework, deleted my Local Settings folder and relogged in.
Does anyone out there have any other ideas for me to try?
I tried the Mage.exe suggestion, but it failed to help. Same with the other installation location suggestion. The application flashes at the bottom of the screen but does not open. I have tried using FUSLOGVW to check the bindings and nothing shows up in there. (Good or bad, there are no binding entries.)
Have you tried using mage.exe? This is a command-line tool that comes with .NET framework. Start up a VS command prompt, and try mage -cc. This will clear your applicaiton cache and will force a new click-once download. This is the first thing I do when my click-once applications fail and it works 99% of the time.
A couple of suggestions:
FusLogVW isn't working for you because you have to enable assembly binding failure logging inside the registry. This MSDN article describes how to do this.
Another thing that comes to mind is, perhaps the ClickOnce app install, or perhaps the whole ClickOnce store is corrupted. Try deleting the ClickOnce app store then reinstalling the application.
It's possible that new prerequisites were added that you don't have on hand. If the URL you are using points directly to "my.application" or whatever your equivalent is, prerequisites won't be processed.
So try pointing to the setup.exe that is created in the same directory as the .application file.
Other than that, it sounds like you're doing all the right stuff...
Also, it could be useful to run the fuslogvw utility on a machine where the application actually works. Or reflector.
And then see if indeed any of its dependencies being loaded surprise you.
Also, for these types of errors, be sure to check if disabling the antivirus resident protection helps. Sometimes it causes problems accessing assemblies' manifests and such.
I uninstalled my Kensington Mouse software, and that resolved my installation errors.
Who knew that mouse software that I never used could cause so much trouble??
Sometimes if your machine is working for days this problem will show up. Try to restart your machine. The same problem happened to me and it disappeared when I restarted my machine.