I am bringing a WPF to the Windows store using a "Windows application packaging project" since 2 years. Until I freshly installed my development system, everything was fine (as usual). When I open the project in VS2019 and start to build the app-package in the publish section, all processes run through but it stops at package signing with "Error signing ....appx".
After checking the EventLog at "Applications and Services/Microsoft/Windows/AppxPackagingOM" there always are 4 warnings in a row with all the same ID 216 saying "app manifest validation warning declared http://schemas.microsoft.com/developer/appx/2015/build-Namespace is inapplicable"
I have never experienced signing errors especially because I am not using any self signed certificate or sth like that.
Any ideas?
This should be a known issue, the specific discussion is here
You can resolve this issue by uninstalling the KB4535996 patch update.
Related
I upgraded a Windows Server 2016 to Windows Server 2022.
The upgrade defaulted to a fresh install in which no setting, programs and customizations were retained.
After the upgrade I pointed IIS's Default Website to the directory that was originally the IIS root on Win 2016.
Modules were not carried forward in the upgrade. When I attempt to Add Managed Module it returns the following error:
There was an error while performing this operation.
Details:
Cannot execute a program. The command being executed was 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\csc.exe' /noconfig /fullpaths
#"C:Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\<number>\<number>.cmdline".
On the original computer (which was backed up) IIS's managed modules do not return an error. I also add that I can access the original computer if there is a need.
Is there a way I can reset this functionality or correct this error?
--------------- Update
At the Server level the options works well. The problem only appears to be at the website level.
--------------- Update
The error is thrown when I add a C# program in a directory under the website.
As a POC I added a simple "Hello World" program and the Add Managed Module returns the error I shared.
I can confirm that csc.exe is present in the directory.
Any ideas how to resolve this issue? It seems (not sure) that the problem is happening because the code is failing to compile.
Any ideas on how to resolve this would be appreciated.
I am working on a project to make an Autocad addon for our engineering department. The project is nearly finished, but when I build the project and send the dll to my colleagues for them to add in autocad, it is not working for them. I can not seem to find a solution on the internet.
- I am using Visual studio 2019
- Autocad 2020
- I make the dll's by releasing it on a x64 platform
- They "netload" it in autocad and the commands that work on my device do not work on theirs
I hope somebody can help me, I am a self thought vb.net engineer for autocad, so I am not that experienced with the basics.
The signing thing should not be required - it works okay here.
Some things to check:
in VS2019, did you set Copy -> false for the DLLs that are referenced ?
when the receiver of your DLL does a right-click on the DLL (in the file explorer), is there an option to unlock the file ? If so, unlock it
Use AnyCPU
I always distribute the Debug version, maybe give that a try ?
is there an error message that you can share ?
It's trusted on your device but unless it's signed it won't be trusted on other machines. That is a security requirement to stop unsigned assemblies from running unknown script.
You can use a self signing certificate for your own machine but unless it comes from an known certification authority it may kick up a stink. You could attempt to add it to their Global Assemby Caches or to see some security is blocking it.
I have created an installation bundle using Wix3.5. Within a Bundle I created a Chain element to install prerequisites (VC Runtime and another inhouse application's installer) before installing the main application. The other inhouse application's installer was created with Installaware. Now the main installation fails after the Installaware installer finishes with this error message in the installer window:
0x80070064 - Cannot create another system semaphore
Excerpt from the installer log:
[2750:1D60][2019-02-28T16:08:58]e000: Error 0x80070064: Process returned error: 0x64
[2750:1D60][2019-02-28T16:08:58]e000: Error 0x80070064: Failed to configure per-user EXE package.
[2750:1D60][2019-02-28T16:08:58]i319: Applied execute package: CEInstaller, result: 0x80070064, restart: None
[2750:1D60][2019-02-28T16:08:58]e000: Error 0x80070064: Failed to execute EXE package.
However, it seems that the bundled application is installed correctly and can be run as well.
After trying to bundle some other installers instead for testing, it seems that this error only occurs with our Installaware inhouse applications but not with other third party installers. I went through the corresponding Installaware logs but did not find anything suspicious (As these are huge I refrained from posting them here for now).
I am pretty much stuck with this issue (also I am quite new working with Windows installer frameworks). Searching online did not deliver any helpful results so far, so I am grateful for any hints how to solve or further investigate this issue.
I'm struggling to get a ClickOnce setup working successfully with a bootstrapper. I'm building a VSTO add-in, and all worked well with a self-signed cert for development, but now we're setting up a proper certificate and it's failing in interestingly challenging ways.
The deployment uses a separate bootstrapper .exe, which is set as a dependency, to prompt for a few settings. Again, all this worked with a self-signed cert.
So the add-in builds okay, with a few post-build steps on the main component, as per:
"mage.exe" -update "$(TargetDir)$(TargetFileName).manifest" -CertFile "E:\COMODOCodeSign.pfx" -Password _pass_
"mage.exe" -update "$(TargetDir)$(TargetName).vsto" -appmanifest "$(TargetDir)$(TargetFileName).manifest" -CertFile "E:\COMODOCodeSign.pfx" -Password _pass_
The build works, the publish works, all looks good.
However, running the setup starts with the bootstrapper's EULA, and after acceptance, then I get the message:
Setup has detected that the file somewheretemp\bootstrapper.exe has either changed since it was published or may be corrupt.
Now, I am not "publishing" the bootstrapper. In the directory where it's stored as a dependency, there's no manifests, and I'm not signing it at all. So I can't see how/where it has decided that's changed.
And although there are answers on the web, they all involve poking through manifests to find differences, and there aren't any manifests for the bootstrapper, and there are no traceable references to the bootstrapper in the signed VSTO manifest. At least, not that I can find with a grep on the published output.
So to the questions:
Any ideas how to proceed?
Should I sign the bootstrapper? (manifests and/or assemblies) -- I did attempt this but it didn't seem to make any difference.
The issue appears to be in Publish > Prerequisites... in the project properties. I'd set it to have an installation folder URL, but I'd not (yet) copied the files there, this was me attempting to test the installer before I got to that point.
As soon as I removed a URL from this field, all worked okay, and the bootstrapper application started correctly. So there might still be a challenge getting web install directories right, but this particular issue is resolved.
Hopefully this is placed in the right area, but I seem to be having an issue with a registered dll.
Our main application is written with Power Builder Version 11, and through various objects, we are able to call registered C# .dll's
The C# .dll is created in Visual Studio 2008 and is installed via an installer that someone else in the building made. When a user runs the installer, they are given the option to register it for everyone or 'Just Me'
The .dll is installed successfully and the user that did the install is able to run the Power Builder application and call the functions inside the .dll.
The issue that arises is that any other user that runs the Power Builder application is greeted with a message box that says: Unable to connect to: [my dll].
I tried to re-register the .dll (using Regasm) but that doesn't work. I have confirmed that the folder is in the PATH System Variable.
The only solution I found was to uninstall the .dll from the Control Panel and re-install it from scratch. But, the same issue arise after the install.
What could the issue be? I'm starting to think that it has to be a rights issue but I can't be 100% positive.