Does screen saver require any manifest file? I'm renaming the .exe to .scr file.
Right now i am not using any manifest file for the screen saver. But if if UAC is enabled, my screen saver crashes. How to by pass this UAC thing ?
It's rather the point that you can't (well, shouldn't be able to, at least).
Presumably, you're accessing some resource that requires elevated privileges, and then not checking whether you successfuly obtained it.
Does UAC actually bring up a dialog?
Related
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?)
I have a scenario,
On a particular machine, I am installing my custom software with MSI installer. MSI installer is created with PerMachine tag, so software is available for all the users of that machine.
Now,
I installed the software on C:\MyApp\ directory.
Then I modified a few configuration files present in C:\MyApp\Config folder to make sure the software connects with my other services.
I started the application, it's working fine.
Now, on the same machine, I logged in with another user.
I started the application.
MSI windows popup with some progress bar for installation.
It vanishes and the application starts but fails to load.
But all the files I have modified are reverted now, I need to again modify those.
Few points:
My installation direcotry is C:\MyApp, not any custom user directory. So modified files should be for all the users.
I think MSI is rolling back changes when I logged in with the new user.
How to stop this?
Please help
Self-Repair: Windows Installer self-repair is the cause of the behavior you see. See the link for an explanation of what happens. See more here - several links with information on self-repair from various angles.
Short Explanation: Essentially the launching of an advertised shortcut triggers an integrity check of the installed files and if a file or registry setting is found to be missing a self-repair ensues. It will put in place missing files and settings. During this process it will sometimes overwrite changed settings files - the problem you describe (due to various file overwrite oddities of Windows Installer - a long answer with various hints).
Fix?: My preferred fix for this is to not install the settings files and update them, but to rather have your application generate them on first launch - either one file per user or a shared one for all users. You can also use a read-only copy of the settings file that you install to copy to a new file that you generate and update. I also recommend you put these files in a writable location in the user profile and not in the main folder. Your setup will never interfere with these generated files. You can also try to set the hosting component for the files "permanent" and "never overwrite". Not very neat. Here is a whole rant on the subject. The very best solution - in my opinion - is to keep settings in databases and get them on launch. This allows good control of all settings. Look out for network and firewall issues.
I hope this answers your question. Are you installing IIS files? I find commercial tool Advanced Installer to have the better feature list for IIS installation - though I lack enough data to conclude. Some videos here: https://www.youtube.com/c/advancedinstaller/search?query=IIS - WiX is also very good, but without the nice GUI of Advanced Installer.
Note: you really should not install to the root of C:\ anything at all. Windows Installer actively tries to make it hard, and side-effects are likely. You can, however, target the IIS folders - wherever they are located.
Update: I found this old answer on how to allow selective update of settings files - I had to resurrect the linked forum answers from Wayback.
Good morning, I have a problem with a Wix installer (it is the first time I use wix) it turns out that when I start everything is fine, and it asks me for administrator permissions, in the "install" button it shows me the icon that I will need those permissions
when I click on Install,
I get the windows to notice to provide the permissions. Until there everything is fine. Then I run the installer again, and it gives me three options, Change - Repair- Remove
I click on remove (which also has the icon that needs Admin Privileges),
but it doesn't ask me for Administrator permissions and it executes the uninstall badly, it doesn't delete registry keys and other things.
I need you to always ask me for the permits. Can someone tell me what's going on?
Thanks
I'm writing an installer for an application. Most of the installer is done and working, but I have on more step outstanding. I need some way to add a setup window to the installer, that will take user input like server address and port, etc. and write these to the relevant files for system start-up. This preferably done through a GUI of sorts inside the installer.
I've tried creating an executable file that runs after installation, but this does not always execute on different systems.
Is there a way to add a GUI to the installer itself that executes after the directory structures and files have been put into place?
Thanks in advance.
In general you should seriously consider doing this as a standalone app that runs when the app first runs and needs configuring. Then it's a program that runs in a user context and can be tested and debugged in the normal way. At least consider what the user is going to do if they want to change the server address or the port - will they need to uninstall your app and reinstall it just to change the server details or the port?
The GUI may not run correctly when started from the install for a number of reasons. It may be initiated with the system account if it's a deferred CA. It wasn't started from the interactive user shell, so it probably won't have any idea of a working directory. It's being run from an msiexec.exe process running in the system directory and maybe with a system account - that's not really the place to be doing your GUI configuration.
I assume you're using WiX, it doesn't say so in your question but it's tagged with WiX.
I would have a read of http://wix.tramontana.co.hu/tutorial/user-interface-revisited (or http://www.dizzymonkeydesign.com/blog/misc/adding-and-customizing-dlgs-in-wix-3/ has a relatively easy to read example), you can add or edit any of the dialogue boxes in the installer, you'll need to download the source to get at the built in dialog, and it does require some "play" to get everything quite right but worth it to get a professional looking installer.
im making a vb.net app and i want to set the icon, how can i do this?
--edit--
turns out i was a bit confused, and it was working. but the answers can still be useful for others.
If I understand the question and issue, your setup/installer might be missing something.
It would seem you did create a shortcut, add it to the Setup project to install to the Desktop (else you wouldnt have one at all)
Select the shortcut in your setup project, open the properties window
Click Target. The list of files you are installing will come up. Select the App.Exe (ie the main executable "MyApp.exe" ususally the primary output). I think Icon is supposed to be set to "Icon" as well.
I think those 2 things combined link the Desktop Shortcut's Icon property to Use the App.Exe's. If there is also a shortcut in the user's programs menu do the same thing (or drag drop a copy).
You are basically doing to the Setup Project's shortcut what you would do to a normal desktop icon to change it or set it. The proj apparently fills in the actual path etc at install.
EDIT
PUBLISH simply compiles everything and produces files for the dev to distribute. It is called PUBLISH because in many cases the output includes a ready to use Setup program for the END USER to install on the PC. (Based on your new Pic, you are trying to reinstall everytime you click the icon or file inside the folder.)
Again, if you do not add a Setup proj to your project, the default one is used and it gives no option for where to install and does not add a shortcut.
Just delete all that junk, Publish again to the default location (VS Studio\...Project name\bin\Publish). Go to that folder and run setup. It will still install to Users\AppData.. but will add a shortcut (to the program) to the start menu.
For a desktop icon, do the "Send To Desktop ..." thing. To INSTALL an icon, you have to add and modify a Setup proj to your Solution.
HTH
'The folder shows the icon for the app, but the icon for the form is different. change the form's icon(in the property grid) to the same as the app and you should see it then.
When you publish it there's 2 files produced that are basically setup files. One relies on the ClickOnce Application Deployment Support Library and the other is a standalone setup app. Since neither one is the actual app you designed, they aren't going to have the icon you want. You'll probably have to investigate other more configurable deployment options.