Everything worked fine before I branched my trunk, now this error list shows up in the branch and the trunk. Google search brought up a possible solution in the Nuget blog, which has different error messages than I do.
Asked Jeff Handley via twitter, he responded "nuget.exe update -self"
Works! Strange thing is that it was a complete refresh install of Windows 7 with a new copy of VS2010. And somehow I have Nuget 1.7. Ah well...
C:\Tfs\Products\Development\Project1\.nuget>nuget.exe update -self
Checking for updates from https://nuget.org/api/v2/.
Currently running NuGet.exe 1.7.30402.9028.
Updating NuGet.exe to 2.0.40000.
Update successful.
Related
So today I was updating one of our SPFX extensions to use the latest spfx framework (1.16) with node (16.13) and after finishing my updates I got the following inside my code:
I am not exactly sure why these are not coming in, I suspect the newest version of spfx moves these classes out of sp-application-base, but why? and where is the documentation for it? Because there is this link that is only 6 months old and explains to use this code for the top and bottom headers.
I was expecting this code to remain in sp-application-base, but it appears it isn't in that package.
How did you perform the upgrade? I highly recommend using the Microsoft 365 CLI to upgrade projects, as the developers of that app do thier best to cover every part of the project that needs to change. Learn more at https://pnp.github.io/cli-microsoft365/cmd/spfx/project/project-upgrade/
Here are the commands to run from the root of your project
npm install -g #pnp/cli-microsoft365
m365 spfx project upgrade --output text
This will give a list of npm commands and code update instructions to follow. See the above documentation for other options for output and use whatever works best for you.
It is still there. What version of #microsoft/sp-application-base is in your project? Should be 1.16.1 I believe. I will say that I am new to all of this as well, but I am using the latest framework and VS is not flagging any issues with these.
When i am going to update my STS it's showing the following error:
An error occurred while collecting items to be installed
session context was:(profile=DefaultProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,org.eclipse.epp.mpc.core,1.8.1.v20191107-0507
No repository found containing: osgi.bundle,org.eclipse.epp.mpc.ui,1.8.1.v20191119-1757
No repository found containing: org.eclipse.update.feature,org.eclipse.epp.mpc,1.8.1.v20191119-1757
What Should i do to update ? Does updating STS really necessary?
This problem is usually caused by wrong or stale cache data for the update mechanism. There is a two step process that you can try to solve this:
go to the Preferences -> Install/Update -> Available Update Sites, select the update sites, and hit Reload. Sometimes this helps, but not always.
if the first step doesn't solve the issue, I would suggest to go to the same preference page, select all update sites, and export them into a file (using the Export button). Then delete all of them and restart your IDE. Then import them back from the XML file using the Import button on that preference page.
That usually solves the issue. Whether you should update your IDE install? I would recommend to always update to the latest STS and Eclipse version, but in the end it is your choice.
Martin's second solution worked for me.
Probably it was some caching problem.
I had the same issue while updating from version 4.13.1 to 4.15.2 and the second workaround worked for me as well.
A while ago I've created a offline install layout for VS2017 Professional (Version 15.5) - this is the base for a couple of dev-hosts at work.
Now we want to upgrade to VS2017 - version 15.8 - so I've createad a 1:1 copy of the existing layout and ran
vs_Professional.exe --layout <path_to_layout>
which ran for a while and updated ?all? packages in the layout.
doing a clean install with this updated layout does work well, however - when using this layout to update one of the hosts that have version 15.5 installed the update procedure fails with exit code "1".
sidenote: VS actually states that it's now 15.8.4 - but it exits with an error code .. so ..?
the command I use for install/update is
(drop the "update" for the clean installation)
vs_Professional.exe update --passive --norestart --wait --productkey $productKey --nocache --noUpdateInstaller --noWeb
using collect.exe there is a state.errors.json file which states that a couple of packages are missing on the layout path...
NOTE: I need to have all required packages available in the offline layout - because some of the PCs do not have internet access (despite we've got the requirement that those vs-setups need to be identical...)
I've tried to reach out to Microsoft Support but didn't hear back from the till now. - anyone else having this issue / was able to solve it?
The update process of an MSFT Visual Studio offline layout seems to be rather buggy, yet there is at least 1 way which seems to work consistently:
always, always, always note the exact parameters you've used to create a offline layout! (all packages, included extras, language - the exact command line(s) you've used!
1: create a copy of the existing offline layout
You'll want to do that if you need to be able to keep using the old layout version for new installs, as Sara Liu pointed out in the comments of the original question. (installing a 'older version' of an updated layout is not supported.)
Also, in case something breaks during the update - you don't loose anything ;-)
2: update the duplicated offline layout
vs_Professional.exe --layout <path_to_layout>
after this finished you should be able to install the new VisualStudio version from this updated layout, yet upgrading a older version will probably fail.
To resolve this, MSFT gives you the
vs_Professional.exe --verify
vs_Professional.exe --fix
tools you can throw at your layout - but don't expect it to work - it never figured out what packages have been missing in my scenarios.
if you follow point 3, you'll also be able to upgrade existing installations.
3: create a new layout with the same parameters as the original one and copy the files over the updated layout
it's quite weird I know - but this has given me the missing packages for the upgrade scenario all the time. just don't forget to fix your ChannelManifest.json afterwards.
The feature list, states:
"It has an easy-to-use single-file installer that creates a working installation with just a few clicks, and can update that installation when new packages become available."
Great, but how to do the update? If I run the installer and "manage" my installation, nothing is updated at all.
Ok, the problem was that I used the "[current installation]" option thinking, that this will update, well... my current installation. Which is wrong. It doesn't do anything.
So, you need to select on of the other options and it will download what you have selected.
I am trying to move some code into a bower package, and my code depends on prototypejs. Prototypejs is not in the bower registry (or it wasn't-- actually I just added it incorrectly, so this question is a bit like asking how to avoid spilling milk after it is already running off the table). What is the proper way to go about getting it there?
I thought I could just point the registry to the prototypejs repo on github, but that resulted in a checkout of files which did not include a built prototype.js file, and it seems it can't be built with the latest version of ruby/rake. So, one option would be to create a new github repo with the built version (downloaded from the website) and a bower.json file. Development on prototypejs seems to have stalled (according to github), so it is unlikely the author(s) would be doing that anytime soon.
DISCLAIMER
I'm beating my own drum but this should help
My PrototypeJS repo has updates in it as well as can be built using grunt and has the actual finished build files in it. Please take a look and see if it works for you.
https://github.com/jwestbrook/prototype
I would create a repo with as you suggested for now, but still try to submit a PR on the upstream repo.