Where can I find the NuGet packages for Sitecore 9.1? [duplicate]
up vote
7
down vote
favorite
This question already has an answer here:
How do I reference Sitecore binaries from NuGet?
2 answers
Sitecore 9.1 has been released, but I can't see the 9.1 packages in my normal NuGet feed. Are they not released yet, or has something changed?
nuget
asked Nov 29 at 15:35
Mark Cassidy♦
16.4k43179
marked as duplicate by Mark Cassidy♦ Nov 29 at 16:07
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
up vote
7
down vote
favorite
This question already has an answer here:
How do I reference Sitecore binaries from NuGet?
2 answers
Sitecore 9.1 has been released, but I can't see the 9.1 packages in my normal NuGet feed. Are they not released yet, or has something changed?
nuget
asked Nov 29 at 15:35
Mark Cassidy♦
16.4k43179
marked as duplicate by Mark Cassidy♦ Nov 29 at 16:07
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
up vote
7
down vote
favorite
up vote
7
down vote
favorite
This question already has an answer here:
How do I reference Sitecore binaries from NuGet?
2 answers
Sitecore 9.1 has been released, but I can't see the 9.1 packages in my normal NuGet feed. Are they not released yet, or has something changed?
nuget
asked Nov 29 at 15:35
Mark Cassidy♦
16.4k43179
This question already has an answer here:
How do I reference Sitecore binaries from NuGet?
2 answers
Sitecore 9.1 has been released, but I can't see the 9.1 packages in my normal NuGet feed. Are they not released yet, or has something changed?
This question already has an answer here:
How do I reference Sitecore binaries from NuGet?
2 answers
nuget
nuget
asked Nov 29 at 15:35
Mark Cassidy♦
16.4k43179
asked Nov 29 at 15:35
Mark Cassidy♦
16.4k43179
asked Nov 29 at 15:35
Mark Cassidy♦
16.4k43179
asked Nov 29 at 15:35
Mark Cassidy♦
16.4k43179
asked Nov 29 at 15:35
Mark Cassidy♦
16.4k43179
16.4k43179
marked as duplicate by Mark Cassidy♦ Nov 29 at 16:07
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by Mark Cassidy♦ Nov 29 at 16:07
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
12
down vote
accepted
You can find the 9.1 feed here.
https://sitecore.myget.org/gallery/sc-platform-9-1
Going forward, Sitecore is going to release a feed for each release. So it will no longer be consolidated like it has in the past.
Also be aware that Sitecore no longer ships NoReferences versions of their packages.
edited Nov 29 at 15:59
Mark Cassidy♦
16.4k43179
answered Nov 29 at 15:37
Chris Auer
7,02711142
Is there a document that details this / why they decided to drop NoReferences support?
– James Skemp
Nov 29 at 16:17
1
The NoReferences public NuGet builds had a lot of complexity around it. And with Sitecore wanting to deploy the release as a whole, it became more important not to separate the dlls into NoRef dlls. This way, we are using the same deployment strategy that Sitecore uses internally.
– Chris Auer
Nov 29 at 16:20
1
Also start thinking about PackageReference and not traditional NuGet packages.config. It will make the move to 9.1 (No NoRefs) much easier. waitingimpatiently.com/package-reference-nuget
– Chris Auer
Nov 29 at 16:22
Thanks. Had actually looked intoPackageReferencetwo months ago but some of the limitations were showstoppers (at the time). Is there public documentation about this somewhere, or is it just in Slack?
– James Skemp
Nov 29 at 16:32
1
Just Slack and Symposium, which is where I heard about it.
– Chris Auer
Nov 29 at 17:10
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
12
down vote
accepted
You can find the 9.1 feed here.
https://sitecore.myget.org/gallery/sc-platform-9-1
Going forward, Sitecore is going to release a feed for each release. So it will no longer be consolidated like it has in the past.
Also be aware that Sitecore no longer ships NoReferences versions of their packages.
edited Nov 29 at 15:59
Mark Cassidy♦
16.4k43179
answered Nov 29 at 15:37
Chris Auer
7,02711142
Is there a document that details this / why they decided to drop NoReferences support?
– James Skemp
Nov 29 at 16:17
1
The NoReferences public NuGet builds had a lot of complexity around it. And with Sitecore wanting to deploy the release as a whole, it became more important not to separate the dlls into NoRef dlls. This way, we are using the same deployment strategy that Sitecore uses internally.
– Chris Auer
Nov 29 at 16:20
1
Also start thinking about PackageReference and not traditional NuGet packages.config. It will make the move to 9.1 (No NoRefs) much easier. waitingimpatiently.com/package-reference-nuget
– Chris Auer
Nov 29 at 16:22
Thanks. Had actually looked intoPackageReferencetwo months ago but some of the limitations were showstoppers (at the time). Is there public documentation about this somewhere, or is it just in Slack?
– James Skemp
Nov 29 at 16:32
1
Just Slack and Symposium, which is where I heard about it.
– Chris Auer
Nov 29 at 17:10
add a comment |
up vote
12
down vote
accepted
You can find the 9.1 feed here.
https://sitecore.myget.org/gallery/sc-platform-9-1
Going forward, Sitecore is going to release a feed for each release. So it will no longer be consolidated like it has in the past.
Also be aware that Sitecore no longer ships NoReferences versions of their packages.
edited Nov 29 at 15:59
Mark Cassidy♦
16.4k43179
answered Nov 29 at 15:37
Chris Auer
7,02711142
Is there a document that details this / why they decided to drop NoReferences support?
– James Skemp
Nov 29 at 16:17
1
The NoReferences public NuGet builds had a lot of complexity around it. And with Sitecore wanting to deploy the release as a whole, it became more important not to separate the dlls into NoRef dlls. This way, we are using the same deployment strategy that Sitecore uses internally.
– Chris Auer
Nov 29 at 16:20
1
Also start thinking about PackageReference and not traditional NuGet packages.config. It will make the move to 9.1 (No NoRefs) much easier. waitingimpatiently.com/package-reference-nuget
– Chris Auer
Nov 29 at 16:22
Thanks. Had actually looked intoPackageReferencetwo months ago but some of the limitations were showstoppers (at the time). Is there public documentation about this somewhere, or is it just in Slack?
– James Skemp
Nov 29 at 16:32
1
Just Slack and Symposium, which is where I heard about it.
– Chris Auer
Nov 29 at 17:10
add a comment |
up vote
12
down vote
accepted
up vote
12
down vote
accepted
You can find the 9.1 feed here.
https://sitecore.myget.org/gallery/sc-platform-9-1
Going forward, Sitecore is going to release a feed for each release. So it will no longer be consolidated like it has in the past.
Also be aware that Sitecore no longer ships NoReferences versions of their packages.
edited Nov 29 at 15:59
Mark Cassidy♦
16.4k43179
answered Nov 29 at 15:37
Chris Auer
7,02711142
You can find the 9.1 feed here.
https://sitecore.myget.org/gallery/sc-platform-9-1
Going forward, Sitecore is going to release a feed for each release. So it will no longer be consolidated like it has in the past.
Also be aware that Sitecore no longer ships NoReferences versions of their packages.
edited Nov 29 at 15:59
Mark Cassidy♦
16.4k43179
answered Nov 29 at 15:37
Chris Auer
7,02711142
edited Nov 29 at 15:59
Mark Cassidy♦
16.4k43179
edited Nov 29 at 15:59
Mark Cassidy♦
16.4k43179
edited Nov 29 at 15:59
Mark Cassidy♦
16.4k43179
16.4k43179
answered Nov 29 at 15:37
Chris Auer
7,02711142
answered Nov 29 at 15:37
Chris Auer
7,02711142
answered Nov 29 at 15:37
Chris Auer
7,02711142
7,02711142
Is there a document that details this / why they decided to drop NoReferences support?
– James Skemp
Nov 29 at 16:17
1
The NoReferences public NuGet builds had a lot of complexity around it. And with Sitecore wanting to deploy the release as a whole, it became more important not to separate the dlls into NoRef dlls. This way, we are using the same deployment strategy that Sitecore uses internally.
– Chris Auer
Nov 29 at 16:20
1
Also start thinking about PackageReference and not traditional NuGet packages.config. It will make the move to 9.1 (No NoRefs) much easier. waitingimpatiently.com/package-reference-nuget
– Chris Auer
Nov 29 at 16:22
Thanks. Had actually looked intoPackageReferencetwo months ago but some of the limitations were showstoppers (at the time). Is there public documentation about this somewhere, or is it just in Slack?
– James Skemp
Nov 29 at 16:32
1
Just Slack and Symposium, which is where I heard about it.
– Chris Auer
Nov 29 at 17:10
add a comment |
Is there a document that details this / why they decided to drop NoReferences support?
– James Skemp
Nov 29 at 16:17
1
The NoReferences public NuGet builds had a lot of complexity around it. And with Sitecore wanting to deploy the release as a whole, it became more important not to separate the dlls into NoRef dlls. This way, we are using the same deployment strategy that Sitecore uses internally.
– Chris Auer
Nov 29 at 16:20
1
Also start thinking about PackageReference and not traditional NuGet packages.config. It will make the move to 9.1 (No NoRefs) much easier. waitingimpatiently.com/package-reference-nuget
– Chris Auer
Nov 29 at 16:22
Thanks. Had actually looked intoPackageReferencetwo months ago but some of the limitations were showstoppers (at the time). Is there public documentation about this somewhere, or is it just in Slack?
– James Skemp
Nov 29 at 16:32
1
Just Slack and Symposium, which is where I heard about it.
– Chris Auer
Nov 29 at 17:10
Is there a document that details this / why they decided to drop NoReferences support?
– James Skemp
Nov 29 at 16:17
Is there a document that details this / why they decided to drop NoReferences support?
– James Skemp
Nov 29 at 16:17
1
1
The NoReferences public NuGet builds had a lot of complexity around it. And with Sitecore wanting to deploy the release as a whole, it became more important not to separate the dlls into NoRef dlls. This way, we are using the same deployment strategy that Sitecore uses internally.
– Chris Auer
Nov 29 at 16:20
The NoReferences public NuGet builds had a lot of complexity around it. And with Sitecore wanting to deploy the release as a whole, it became more important not to separate the dlls into NoRef dlls. This way, we are using the same deployment strategy that Sitecore uses internally.
– Chris Auer
Nov 29 at 16:20
1
1
Also start thinking about PackageReference and not traditional NuGet packages.config. It will make the move to 9.1 (No NoRefs) much easier. waitingimpatiently.com/package-reference-nuget
– Chris Auer
Nov 29 at 16:22
Also start thinking about PackageReference and not traditional NuGet packages.config. It will make the move to 9.1 (No NoRefs) much easier. waitingimpatiently.com/package-reference-nuget
– Chris Auer
Nov 29 at 16:22
Thanks. Had actually looked into
PackageReference two months ago but some of the limitations were showstoppers (at the time). Is there public documentation about this somewhere, or is it just in Slack?– James Skemp
Nov 29 at 16:32
Thanks. Had actually looked into
PackageReference two months ago but some of the limitations were showstoppers (at the time). Is there public documentation about this somewhere, or is it just in Slack?– James Skemp
Nov 29 at 16:32
1
1
Just Slack and Symposium, which is where I heard about it.
– Chris Auer
Nov 29 at 17:10
Just Slack and Symposium, which is where I heard about it.
– Chris Auer
Nov 29 at 17:10
add a comment |
