Uninstallation of Vista gadget - windows-vista

I have developed a test vista gadget. Zipped it and renamed it to ".gadget". Its a valid installer for the gadget & it works well.
Is there any standard way to un-install the same gadget? What I am looking for is programmatic way to un-install the gadget.

Click the + sign at the top of the sidebar.
Right-click the gadget you want to uninstall in the list of gadgets.
Select Uninstall.

Related

How do you enable Microsoft Terminal Service Client Control in Visual Studio?

I found this article on how to setup and use RDP client for MFC. But where do you get the dialog they show in step 2? Here's the link to RDP Remote Desktop ActiveX Controls
Well, I found one way to do it, open the toolbox window, right-click, "choose items" and it brings up that dialog to choose the various components. I never knew any of that existed.

Using NSIS the Uninstaller shortcut does not show up in the Start Menu

Using NSIS I have created an installer, which works well. It is a user privileged installer which installs in %localAppData%\Programs;
StrCpy $INSTDIR `$LOCALAPPDATA\Programs\MyAppFolder
I create an uninstaller which works perfectly from Control Panel, Programs and Features.
I have created an Uninstaller shortcut using;
CreateShortCut "$SMPROGRAMS\${MUI_PRODUCT}\Uninstall.lnk" "$INSTDIR\Uninstall.exe" "" "$INSTDIR\Uninstall.exe" 0
The ".lnk" file is created in the same place as the application shortcut;
C:\Users\Myuser\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\MyAppFolder
If I browse to this folder and double click the uninstaller link it works fine.
The application shortcut is visible in the start menu, however the Uninstaller is not. I have reviewed a few "solutions," but have been unable to resolve the issue. What kinds of issues should I look for?
The Microsoft guidelines say that you should not create shortcuts to uninstallers nor help files.
Starting with Windows 8, Windows hides those pointless shortcuts from the start menu.

Webbrowser control no longer working after Windows Update

I have a custom project in VB6, which I was working with it since 3-4 years ago, now today suddenly I noticed that Webbrowser controls are not working anymore on my laptop (maybe after a windows automatic update - it's working on my other laptop)
The problem is when I double-click on Webbrowser components there are no default declarations for them and this text shows up in code section:
Private Sub WebBrowser1_SHDocVwCtl(ByVal Text As String)
End Sub
Please help me fix it and get it back to how it was before.
As #JimmySmith suggests, check that Microsoft Internet Controls is checked in your Components list (Project > Components > Controls tab > Microsoft Internet Controls.). If not, check it and hit Apply, then OK.
If it doesn't show up in the list, you can use the Browse button to look for C:\Windows\SysWOW64\ieframe.dll directly.
Other things that I recommend:
Run VB6 IDE as Administrator. Right-click on your Microsoft Visual Basic 6.0 shortcut and check "Run this program as an administrator" in compatibility properties section.
Select Windows XP (Service pack 3) as Compatibility mode.

Visual Studio 2017 - Open in Visual Studio from Explorer - Permission Error

I am using VS 2017 Enterprise.
I have it setup to open/run in Administrator mode which is working for SLN files.
However I'm trying out the new "Open in Visual Studio" feature by right clicking on a folder in Explorer. I'm receiving the following permission error. It's happening for every folder I try.
VS Code has no problem however.
Is there something more I need to enable?
My first guess would be that the VS 2017 application itself (devenv.exe) is configured on that machine to always Run as Administrator see https://technet.microsoft.com/en-us/library/ff431742.aspx on how to change it:
To mark an application to always run as an administrator, do the following:
1. On the Start menu, locate the program that you want to always run as an administrator.
2. Right-click the application’s shortcut, and then click Properties.
3. In the Properties dialog box, click the Compatibility tab.
4. Do one of the following:
- To apply the setting to the currently logged-on user, select the Run This Program As An Administrator check box, and then click OK.
- To apply the setting to all users on the computer and regardless of which shortcut is used to start the application, click Change Setting For All Users to display the Properties dialog box for the application’s .exe file, select the Run This Program As An Administrator check box, and then click OK twice.
See also list of things that you can't do without administrator account https://msdn.microsoft.com/en-us/library/jj662724.aspx. What typically makes Web-developers to make VS always run as administrator is "Deploying a web application to Internet Information Services (IIS) on a local computer." and "Debugging applications that a run under a different user account, such as ASP.NET websites."
For me it has worked as it should, at least this can help you.
First question is how you "setup to open/run in Administrator mode" ?
Using the "Advanced button" of the Visual Studio 2017 shortcut is not enough because methods with the right mouse button don't use this shortcut.
Using the method of the compatibility tab as mentioned already by SergGr
(https://technet.microsoft.com/en-us/library/ff431742.aspx) has worked for me, and I have been able to use it for folders as well as for solution files !
I am logged in as a member of the local admin group and UAC standard setting into Win 8.1 .
Another possibility instead of using the compatibility page would be to inject an own manifest into devenv.exe. Neither of the two is very clean (I am no fan of the whole compat layer, but it helps here a bit).
Have you tried to switch UAC off temporarily for a test? Or how you have configured UAC?
If you have done it the way described, the explorer should come up with a correct UAC message.
This works for me if not for you then refer to (https://marketplace.visualstudio.com/items?itemName=GregTrevellick.OpeninVisualStudio2017Enterprise):
1. open notepad.exe and paste this into it:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\*\shell\VSCode\command]
#="\"C:\\Program Files (x86)\\Microsoft VS Code\\Code.exe\" \"%1\""
here is my registry file exported just incase you need it (you shouldnt):
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\*\shell\VSCode\command]
#=hex(2):22,00,43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,20,\
00,46,00,69,00,6c,00,65,00,73,00,20,00,28,00,78,00,38,00,36,00,29,00,5c,00,\
4d,00,69,00,63,00,72,00,6f,00,73,00,6f,00,66,00,74,00,20,00,56,00,53,00,20,\
00,43,00,6f,00,64,00,65,00,5c,00,43,00,6f,00,64,00,65,00,2e,00,65,00,78,00,\
65,00,22,00,20,00,22,00,25,00,31,00,22,00,00,00
2. save as VSElevated.reg
3. go to where you saved the .reg file and double click, yes to everything and ok.
4. This is how your Registry should look like afterwards:
The reason i think is the %1 is missing in your launch command. This should solve it.

How to prevent InstallShield Limited Edition from making some shortcuts "Run as Administrator"

I am using InstallShield 2015 Limited Edition with Visual Studio 2010 to create an installer for a variety of different files, including executables, some Excel spreadsheets, and html pages. The executable files are created by NetBeans. The installer works fine, except for the following behavior with a created shortcut that I don't understand.
NetBeans creates 2 executables: myapp.exe, which is 32-bit, and myapp64.exe, which is 64-bit. I am creating non-advertised shortcuts for these two files. The shortcut for myapp64.exe is created as a "Run as Administrator" shortcut, where the little shield picture is embedded in the shortcut icon, and double clicking the icon brings up the typical prompt window when trying to run an app as administrator. When looking at the Compatibility tab in the shortcut properties, "Run this program as an administrator" has been checked for all users.
The shortcut for myapp.exe is "normal". It can be run as administrator from the right-click context menu, but it is not forced to do so because "Run this program as an administrator" is not checked on the Compatibility tab.
I would like for both shortcuts to be created as "normal", to avoid the annoying prompt window, but I can't figure out why the shortcut for myapp64.exe is created as a "Run as Administrator" shortcut. I checked myapp64.exe with the MT tool, but there is no manifest, and the properties for myapp64.exe do not require admin privileges anywhere that I can find. I can't find any InstallShield settings that would make the shortcut "Run as administrator". I have deleted and re-created the shortcut in the installer project, but that doesn't solve the problem. If I manually modify the shortcut for myapp64.exe after installation to uncheck "Run this program as an administrator", the app runs fine.
Finally, this behavior doesn't seem to happen all the time. It happens in Windows 7, but does not seem to happen in Windows 10. I am only working with 64-bit operating systems.
Any ideas what is going on, or how to prevent the myapp64.exe shortcut from being created to run as an administrator? Is the Windows Installer seeing something that is causing it to make the shortcut this way?
I posted in the Flexera forum for InstallShield LE, but didn't get a response.
Thanks!

Resources