We Keep Coding

Visual Studio 2022 cannot add apple individual account

I have been trying to connect my paid individual account to Visual Studio 2022
I have entered the keyName, Issuer ID, KEY ID and downloaded the private key exactly as in https://learn.microsoft.com/en-us/dotnet/maui/ios/apple-account-management?view=net-maui-7.0&tabs=vs
but when I click on add button nothing occur and no error message is shown,
I have also visual studio 2019 installed on the same machine but also cannot add the account using the user name and the password
any one has any idea about the reason

Make sure that you go into Tools > Options > Xamarin and add your Apple developer account by using the Apple ID that is affiliated with that account.
When that is complete, you can highlight it, then click on View Details to see your Certificates and Profiles. If none are there, create a Certificate and Download all profiles.

After installing Application it ask me admin credentials

I am a bit confused. I have a C # WPF application. This works as I wish when I run the EXE file.
Now I have set up an installer (Visual Studio Installer project). This installer installs the application as desired and creates a desktop shortcut.
If I start the application now via the desktop icon, then installer is executed again and it is asked for the admin access data. After entering the data, the application starts directly. And that happens every time I click on the desktop icon.
I use in the application project the costura.fody package to bind one executable.
Have someone ideas whats wrong?
I've read the desktop icon from Visual-Studio-Installer-Project check always the application state. I think this is why the installer start every time I click the app icon on the desktop.

Short Answer: This is an MSI self-repair problem.
Work out what component triggers the self-repair. Details below.
Correct the situation by making changes to the setup eliminating the conflict situation.
Self-Repair: This is self-repair, or self-healing or "resiliency" depending on who you ask. I have a description here: Why does the MSI installer reconfigure if I delete a file? Towards the bottom there are three links. I would go for the one saying "how to avoid in your own package".
Understanding: There is a longer explanation of self-repair here. Section "The Primary Causes of Self-Repair" explains 3 main causes, yours being the first one.
Culprit: You should check the event log for clues as to what file / component is triggering the self-repair:
Stefan Kruger's debugging procedure
My own version here (longer) (section "Finding the trigger or culprit for the self-repair").
Once you have worked out what component triggers the repair there are a variety of fixes. But first maybe check the list of common mistakes in your own package.
Previous Answer: Come to think of it there are several previous answers:
Window's pop-up constantly appears when installed application is launched (seems better than the above)
Visual Studio 2015 msi build initiates another installation

How to customize the Setup wizard with custom forms in Visual Studio setup project

I have to create a setup project with custom serial key validation. I have to proceed the installation only after the serial key is authenticated or else we have to skip the installation.
I have tried the sample setup project, and have called the custom form for authenticating serial key in the installer class, merged the installer class from the custom action in the setup project.
But the Serial key validation form comes after the progress form executes.
I need to show it after the welcome page.
I have attached the screenshot of the setup wizard.
How to bring the Setp 5 form (custom form) before Step 2?

This can't be done in Visual Studio setups - the only validation supplied is the serial number template, a masked edit control to verify the basics. This is because Visual Studio setups custom actions all run after the files are installed, and you cannot associate one with a button click to validate the serial number, or in fact anything in the UI.
You might need to use another tool for your setup. VS setups are pretty simple but they don't have many features. Otherwise you could use another tool to build a merge module that you could add. Manually editing the MSI file is a possibility but you'd need to know a lot about the internals of MSI files.

How to skip folder selection form when update installed application via Windows Installer setup project

As the title describes, I am trying to skip the folder selection form when update the installed application via setup project in visual studio(casue the user already selected folder path when they installed the app). I googled online and find a way to disable folder form: http://www.codeproject.com/Tips/437285/Visual-Studio-Deployment-Setup-Disable-Installatio. However, How to know if it is installation or upgrade? If we know it is upgrade, how to get the installation path?
Thanks in advance!
I do not find any approaches to skip that folder form. This should be the reason that many installer tools exist in the market. Since my app is very small, I simply disabled the folder selection dialog. For anyone who are interested, please check this URL: http://www.codeproject.com/Tips/437285/Visual-Studio-Deployment-Setup-Disable-Installatio

If you saved the original install location in the registry, for example by saving [TARGETDIR] in a registry item, then you can retrieve it during an upgrade. You find out you're doing an upgrade because it will set a property called PREVIOUSVERSIONSINSTALLED. The problem is that there is no way to wire it all up in a VS setup project. You want the browse dialog there (not deleted) but you want to skip it if PREVIOUSVERSIONSINSTALLED has been set, and there's no support in VS setup projects for that. You'd need to go into the ControlEvent table in the MSI file and figure out how to skip the browse dialog, as well as have the Back button skip over if necessary, and that's just very difficult.
What's the actual issue? Visual Studio upgrades are complete installs that uninstall the previous product and install the new one wherever the user wants, so why is it necessary to install in the same location as the previous install?

Access to the registry key is denied (ABCPdf)

I am trying out ABCPdf 8.1 and when using the AddImageUrl(...) method I get the following error:
Access to the registry key 'HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl' is denied.
I have looked in the registry and main\featurecontrol does not exist for CURRENT_USER so I cannot change permissions on it.
Has anyone experienced this before, or know of any solutions I could try?
Thanks in advance

Who is the CURRENT_USER? Assuming it's an ASP.NET application identity, have you tried loading its user profile?
Open up IIS Manager and navigate to the application pool for your site. In the Advanced Settings dialog, set Load User Profile to True.

Perhaps it's a problem between IE9 and ABCPDF.If this error comes by using AddHtml() or AddImageHtml() , I suggest you to change the Rendering Engine from MSHtml to Gecko.
theDoc.HtmlOptions.Engine = EngineType.Gecko;
http://www.websupergoo.com/support.htm
In my case, this solution solved my error.

If you know the specific key that ABCPDF is trying to add, and you don't want to change the app pool settings, you can set the appropriate key in HKEY_LOCAL_MACHINE. We had exactly that situation and knew that ABCPDF wanted to add the FEATURE_IVIEWOBJECTDRAW_DMLT9_WITH_GDI key. So we added the entries below to the registry. Note that the second key is specifically for 32-bit applications running on 64-bit Windows.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_IVIEWOBJECTDRAW_DMLT9_WITH_GDI]
"w3wp.exe"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_IVIEWOBJECTDRAW_DMLT9_WITH_GDI]
"w3wp.exe"=dword:00000001

I'm not sure if this is the answer but if you are trying to access this programaticaly your executable should run as administrator while accessing it. If you are in debug mode run visual studio as administrator (right click and select "Run as administrator"