I have created a symbolssource that is being used for a while already.
If I try to push packages generated in the old VS, it pushes the packages correctly, if I try to push new packages I got this error:
nuget push *.symbols.nupkg 123 -Source http://localhost:3182/NuGet
Empurrando MYPACKAGE para 'http://localhost:3182/NuGet' ... Failed to
process request. 'Package submission failed: Unknown custom metadata
item kind: 6. See http://www.symbolsource.org/Public/Home/Help for
possible reasons. Fiddler may help diagnosing this error if your
client discards attached detailed information.'.
I tried to update the symbolssource with the latest nuget packages, but still I have the same issue.
The problem here was the MSBuild 14 with the pdb metadata. There is a fix for it in this link.
Related
I am having an issue when I try to publish a specific solution.
Related into:
I have been able to publish/deploy about 6 solutions with no issues.
The solution that is giving me issues when I try to Publish runs 100% on my local VS 2019, the issue is publishing
This is my first solution I created from new on VS 2019. All others were created on VS 2017
I can run in browser - https://api.nuget.org/v3/index.json
I did try to Run a NuGet package restore
I did try to implement different solutions I found while researching
If you google search for the error of “The request was aborted: Could not create SSL/TLS secure channel” you will see a lot of articles. I tried the solutions detailed with obviously no luck.
...
1>------ Publish started: Project: HFSPackagesApi, Configuration: Release Any CPU ------
Connecting to C:\deployments\HFSPackagesApi...
Determining projects to restore...
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\NuGet\NuGet.targets(128,5): Error : Unable to load the service index for source https://api.nuget.org/v3/index.json.
An error occurred while sending the request.
The request was aborted: Could not create SSL/TLS secure channel.
C:\Program Files\dotnet\sdk\3.1.402\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(241,5): Error NETSDK1004: Assets file 'F:\source\BitBucket\gmborl\LiveBackup\ReleaseInsightApp\HFSPackagesApi\HFSPackagesApi\obj\publish\win-x64\project.assets.json' not found. Run a NuGet package restore to generate this file.
1>Build failed. Check the Output window for more details.
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========
...
Fixed it in Windows 7 by doing these steps, outlined in Support Article:
Step 1
Add a DWORD registry entry called DefaultSecureProtocols with a value of 0x00000a00 to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp
Note: Second one (in Wow6432Node) is needed only on 64-bit Windows.
Step 2
Created sub keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client
In each of them add a DWORD entry called DisabledByDefault with a value of 0.
Note: You may need to create the TLS 1.x key and also the Client key.
After getting my Window 10 laptop operational with VS 2019 I am able to publish my solution.
This is no longer an issue.
I had the same problem. The OS is windows 7 profession service pack 1. When I published the ASP NET CORE project on IIS, the problem happened.
I solved it with the following steps.
First, I searched the https://api.nuget.org/v3/index.json on browser, it worked.
Second, I followed the solution from user11693, and I solved it.
Using Visual Studio 2019 to publish an update to an existing windows store application. This worked a week ago.
Our solution builds without error. When I go to create the setup package I get an error "Failed to sign 'D:\dev\MeyerMusic\MeyerTablet\TabletDistribution\bin\AnyCPU\Release\MeyerMusicTabletSetup_2.6.6.0_AnyCPU.msix'."
We are distributing the application as a Microsoft Store app under the existing app name.
Last week on this same development computer I built version 2.6.5 as well as many packages before that.
The error number is blank or missing. I do not have a reason for the failure. I only see one fact in the error message and that points to line 4574 in the file: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets
That line is this:
<SignAppxPackage Condition="'$(AppxPackageSigningEnabled)' == 'true'"
AppxPackageToSign="$(AppxMainPackageOutput)"
CertificateThumbprint="$(PackageCertificateThumbprint)"
CertificateFile="$(PackageCertificateKeyFile)"
CertificatePassword="$(PackageCertificatePassword)"
HashAlgorithmId="$(AppxHashAlgorithmId)"
EnableSigningChecks="$(EnableSigningChecks)"
SignAppxPackageExeFullPath="$(SignAppxPackageExeFullPath)"
TempCertificateFilePath="$(TempCertificateFilePath)"
VsTelemetrySession="$(VsTelemetrySession)"
SigningTimestampServerUrl="$(AppxPackageSigningTimestampServerUrl)"
SigningTimestampDigestAlgorithm="$(AppxPackageSigningTimestampDigestAlgorithm)"
/>
Troubleshooting steps:
Attempted to build a side load package. Results in same error
Successfully built a side load package that was not signed
I have restarted Visual Studio
I have rebooted the machine
I have deleted OBJ, BIN for the entire solution
I have looked for errors in the event log but none have been found so far.
After uninstalling KB4535996 the problem was resolved.
I found this via a tip from the following post: https://developercommunity.visualstudio.com/content/problem/934967/uwp-error-failed-to-sign.html
I updated PlasticSCM to the latest version (8.0.16). Now when I start plastic I get that error: the client configuration file "client.conf" contains error: Root element is missing.
Everything worked correctly before updating. I tried reinstalling PlasticSCM and remove client.conf file but it did not help the client still does not start.
The Plastic SCM client.conf file is used by both the GUI and the CLI to store the main user preferences.
I tried reinstalling PlasticSCM and remove client.conf file but it did
not help the client still does not start.
It's ok to remove it, but additionally, you need to reconfigure the Plastic SCM Client. Please run the following command to do it.
plastic --configure
or run the "Client configuration wizard".
If you keep facing the problem I recommend you to open a support ticket -> https://www.plasticscm.com/support. The team will help you to fix the problem.
Having some trouble registering a bower package to a remote repository which should be possible with the version I have (artifactory.version: 4.9.1)
So there is a repo there thats setup and it has a URL of http://mygetserver.domain.com/git which hits the gitolite page for browsing the git repos (which seems odd)
The registry url is pointing at the default of https://bower.herokuapp.com/
With the Bower Settings pointing to Custom and a default URL of {0}/{1}/archive/{2}.{3} - Again that feels weird but I have no idea whats expected in there
So when I try and register a package with
bower register nh-styles git#mygetserver.domain.com:nh-styles.git --verbose
I get an error to say
Error: Unknown error: 404 - Unable to determine coordinates from url git#mygetserver.domain.com:nh-styles.git
If I change that to use ssh:// first then it works
C:\Dev>bower register nh-styles
ssh://git#mygetserver.domain.com/nh-styles.git --verbose bower
nh-styles#* resolve
ssh://git#mygetserver.domain.com/nh-styles.git#* bower nh-styles#*
checkout v0.0.4 bower nh-styles#* old-git It seems you
are using an old version of git, it will be slower and propitious to
errors! bower nh-styles#* invalid-meta nh-styles is missing
"ignore" entry in bower.json bower nh-styles#* resolved
ssh://git#mygetserver.domain.com/nh-styles.git#0.0.4 ? Registering a
package will make it installable via the registry
(http://myart.artifactorydomain.com:8081/artifactory/api/bower/bower-nh-git
? Registering a package will make it installable via the registry
(http://myart.artifactorydomain.com:8081/artifactory/api/bower/bower-nh-git
), continue? Yes bower nh-styles register
ssh://git#mygetserver.domain.com/nh-styles.git
Package nh-styles registered successfully! All valid semver tags on
ssh://git#mygetserver.domain.com/nh-styles.git will be available as
versions. To publish a new version, just release a valid semver tag.
Run bower info nh-styles to list the available versions.
C:\Dev>bower info nh-styles bower nh-styles#* not-cached
art://nh-styles/nh-styles#* bower nh-styles#* resolve
art://nh-styles/nh-styles#* bower EREQUEST
Request to
http://myart.artifactorydomain.com:8081/artifactory/api/bower/bower-nh-git/refs/nh-styles/n
h-styles returned 404 status code.
Additional error details: [object Object]
Yet when I try and Info nothing shows. Every time I resubmit I'm getting a 201 rather than a package exists issue. So basically why is it not being saved? Artifactory logs are showing nothing I can see. Anything else I can look at?
The reason you must include ssh:// is that the bower resolver need to know what protocol it has to use when accessing the specified url, this is also documented here. Also I noticed you used domain.com:nh-styles.git this is not a valid url, because of the : -- it might also work like this without the ssh:// part i'm not sure.
The way registering a package with Artifactory works is that it simply acts as the registry in a sense that it simply keeps a mapping of the package name to the git url you gave it. That's also why registering a package will have no other apparent effect (except for the 201 response).
The behavior is pretty much identical to the bower public registry in this aspect.
The error itself you're getting is because Artifactory can't find the git repo you're referring to in the registered git repository - check that the repo at the url you gave is accessible - you can also turn on debug logs on org.artifactory.addon.bower to see the exact error Artifactory encountered if it's not already printing something to the log about this.
After i figured out how to build the Demo Project "Upsell Management" (project), i'm struggling now with the installation in the sandbox.
I'm running a sandbox with POA 5.5-5562_update06-824 and every time i try to install it i get a Status "Validation Error":
http://i.imgur.com/2v6GEJc.png
So, is there a log file or anything to find out what is the error behind that?
'Validation error' means that package import task has failed, more details on this can be found in Operations->Tasks
If you see a validation error that you did not see while running apsbuild/apslint tool this means that either you or POA have an older version of apstools.
The best way is redeploy sandbox to latest POA version and update APS tools on your build machine (http://doc.apsstandard.org/2.1/tools/cli-tools/#cli-tools)