nuget pack .csproj with custom .nuspec metadata
up vote
0
down vote
favorite
I would like to pack nuget package using a .csproj file. Following command will be executed:
nuget pack MyProject.csproj -IncludeReferencedProjects
In the project folder I have two nuspec files, one depending to the MyProject.csproj and another wich will be used to make a different package but depending on this project to. Folder structure looks like:
-ProjectFolder
|-MyProject.csproj
|-AdditionalMyProject.nuspec
|-MyProject.nuspec
When calling the nuget pack command, it allways takes the first nuspec file (AdditionalMyProject.nuspec - lower naming) to get metadata for nuget package but the correct nuspec should be MyProject.nuspec (matching the name of project file).
Is there a way to tell nuget pack wich nuspec it should use when packing a csproj?
Something like this:
nuget pack MyProject.csproj -nuspec MyProject.nuspec -IncludeReferencedProjectsenter
c# nuget
asked Nov 8 at 9:24
Mi. Sharp
3921624
add a comment |
up vote
0
down vote
favorite
I would like to pack nuget package using a .csproj file. Following command will be executed:
nuget pack MyProject.csproj -IncludeReferencedProjects
In the project folder I have two nuspec files, one depending to the MyProject.csproj and another wich will be used to make a different package but depending on this project to. Folder structure looks like:
-ProjectFolder
|-MyProject.csproj
|-AdditionalMyProject.nuspec
|-MyProject.nuspec
When calling the nuget pack command, it allways takes the first nuspec file (AdditionalMyProject.nuspec - lower naming) to get metadata for nuget package but the correct nuspec should be MyProject.nuspec (matching the name of project file).
Is there a way to tell nuget pack wich nuspec it should use when packing a csproj?
Something like this:
nuget pack MyProject.csproj -nuspec MyProject.nuspec -IncludeReferencedProjectsenter
c# nuget
asked Nov 8 at 9:24
Mi. Sharp
3921624
I don't understand the purpose of AdditionalMyProject.nuspec. If there's another project that has a dependency on MyProject, I don't see why you would need a special nuspec for MyProject. This might be a case of the XY problem. Why do you want two nuspec files?
– Ziv
Nov 8 at 22:01
@Ziv I would like to provide two packages with different purpose. The AdditionalMyProject.nuspec should provide dependencies to other nuget packages including MyProject.nupkg. MyProject is only base package for a defined purpose.
– Mi. Sharp
Nov 12 at 10:35
if AdditionalMyProject is a meta package, then there's no need for the nuspec to be in the same folder as the csproj, right? move it to its own folder, then there's only 1 nuspec next to the csproj.
– Ziv
Nov 13 at 12:35
That's an answer which makes sense. I tried and it worked, can you post it as answer?
– Mi. Sharp
Nov 14 at 13:44
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I would like to pack nuget package using a .csproj file. Following command will be executed:
nuget pack MyProject.csproj -IncludeReferencedProjects
In the project folder I have two nuspec files, one depending to the MyProject.csproj and another wich will be used to make a different package but depending on this project to. Folder structure looks like:
-ProjectFolder
|-MyProject.csproj
|-AdditionalMyProject.nuspec
|-MyProject.nuspec
When calling the nuget pack command, it allways takes the first nuspec file (AdditionalMyProject.nuspec - lower naming) to get metadata for nuget package but the correct nuspec should be MyProject.nuspec (matching the name of project file).
Is there a way to tell nuget pack wich nuspec it should use when packing a csproj?
Something like this:
nuget pack MyProject.csproj -nuspec MyProject.nuspec -IncludeReferencedProjectsenter
c# nuget
asked Nov 8 at 9:24
Mi. Sharp
3921624
I would like to pack nuget package using a .csproj file. Following command will be executed:
nuget pack MyProject.csproj -IncludeReferencedProjects
In the project folder I have two nuspec files, one depending to the MyProject.csproj and another wich will be used to make a different package but depending on this project to. Folder structure looks like:
-ProjectFolder
|-MyProject.csproj
|-AdditionalMyProject.nuspec
|-MyProject.nuspec
When calling the nuget pack command, it allways takes the first nuspec file (AdditionalMyProject.nuspec - lower naming) to get metadata for nuget package but the correct nuspec should be MyProject.nuspec (matching the name of project file).
Is there a way to tell nuget pack wich nuspec it should use when packing a csproj?
Something like this:
nuget pack MyProject.csproj -nuspec MyProject.nuspec -IncludeReferencedProjectsenter
c# nuget
c# nuget
asked Nov 8 at 9:24
Mi. Sharp
3921624
asked Nov 8 at 9:24
Mi. Sharp
3921624
asked Nov 8 at 9:24
Mi. Sharp
3921624
asked Nov 8 at 9:24
Mi. Sharp
3921624
asked Nov 8 at 9:24
Mi. Sharp
3921624
3921624
I don't understand the purpose of AdditionalMyProject.nuspec. If there's another project that has a dependency on MyProject, I don't see why you would need a special nuspec for MyProject. This might be a case of the XY problem. Why do you want two nuspec files?
– Ziv
Nov 8 at 22:01
@Ziv I would like to provide two packages with different purpose. The AdditionalMyProject.nuspec should provide dependencies to other nuget packages including MyProject.nupkg. MyProject is only base package for a defined purpose.
– Mi. Sharp
Nov 12 at 10:35
if AdditionalMyProject is a meta package, then there's no need for the nuspec to be in the same folder as the csproj, right? move it to its own folder, then there's only 1 nuspec next to the csproj.
– Ziv
Nov 13 at 12:35
That's an answer which makes sense. I tried and it worked, can you post it as answer?
– Mi. Sharp
Nov 14 at 13:44
add a comment |
I don't understand the purpose of AdditionalMyProject.nuspec. If there's another project that has a dependency on MyProject, I don't see why you would need a special nuspec for MyProject. This might be a case of the XY problem. Why do you want two nuspec files?
– Ziv
Nov 8 at 22:01
@Ziv I would like to provide two packages with different purpose. The AdditionalMyProject.nuspec should provide dependencies to other nuget packages including MyProject.nupkg. MyProject is only base package for a defined purpose.
– Mi. Sharp
Nov 12 at 10:35
if AdditionalMyProject is a meta package, then there's no need for the nuspec to be in the same folder as the csproj, right? move it to its own folder, then there's only 1 nuspec next to the csproj.
– Ziv
Nov 13 at 12:35
That's an answer which makes sense. I tried and it worked, can you post it as answer?
– Mi. Sharp
Nov 14 at 13:44
I don't understand the purpose of AdditionalMyProject.nuspec. If there's another project that has a dependency on MyProject, I don't see why you would need a special nuspec for MyProject. This might be a case of the XY problem. Why do you want two nuspec files?
– Ziv
Nov 8 at 22:01
I don't understand the purpose of AdditionalMyProject.nuspec. If there's another project that has a dependency on MyProject, I don't see why you would need a special nuspec for MyProject. This might be a case of the XY problem. Why do you want two nuspec files?
– Ziv
Nov 8 at 22:01
@Ziv I would like to provide two packages with different purpose. The AdditionalMyProject.nuspec should provide dependencies to other nuget packages including MyProject.nupkg. MyProject is only base package for a defined purpose.
– Mi. Sharp
Nov 12 at 10:35
@Ziv I would like to provide two packages with different purpose. The AdditionalMyProject.nuspec should provide dependencies to other nuget packages including MyProject.nupkg. MyProject is only base package for a defined purpose.
– Mi. Sharp
Nov 12 at 10:35
if AdditionalMyProject is a meta package, then there's no need for the nuspec to be in the same folder as the csproj, right? move it to its own folder, then there's only 1 nuspec next to the csproj.
– Ziv
Nov 13 at 12:35
if AdditionalMyProject is a meta package, then there's no need for the nuspec to be in the same folder as the csproj, right? move it to its own folder, then there's only 1 nuspec next to the csproj.
– Ziv
Nov 13 at 12:35
That's an answer which makes sense. I tried and it worked, can you post it as answer?
– Mi. Sharp
Nov 14 at 13:44
That's an answer which makes sense. I tried and it worked, can you post it as answer?
– Mi. Sharp
Nov 14 at 13:44
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
AdditionalMyProject.nuspec is a different project, even if it doesn't have a MSBuild project associated (it is a different .nupkg after all), so you're less likely to have tooling problems if you keep the nuspec in its own directory. Similar to how different csproj files live in different directories, even when one has a dependency on the other, I recommend putting the different .nuspec files in different directories, even if MyProject is a nuget dependency of AdditionalMyProject.
answered Nov 14 at 21:15
Ziv
909616
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
AdditionalMyProject.nuspec is a different project, even if it doesn't have a MSBuild project associated (it is a different .nupkg after all), so you're less likely to have tooling problems if you keep the nuspec in its own directory. Similar to how different csproj files live in different directories, even when one has a dependency on the other, I recommend putting the different .nuspec files in different directories, even if MyProject is a nuget dependency of AdditionalMyProject.
answered Nov 14 at 21:15
Ziv
909616
add a comment |
up vote
0
down vote
accepted
AdditionalMyProject.nuspec is a different project, even if it doesn't have a MSBuild project associated (it is a different .nupkg after all), so you're less likely to have tooling problems if you keep the nuspec in its own directory. Similar to how different csproj files live in different directories, even when one has a dependency on the other, I recommend putting the different .nuspec files in different directories, even if MyProject is a nuget dependency of AdditionalMyProject.
answered Nov 14 at 21:15
Ziv
909616
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
AdditionalMyProject.nuspec is a different project, even if it doesn't have a MSBuild project associated (it is a different .nupkg after all), so you're less likely to have tooling problems if you keep the nuspec in its own directory. Similar to how different csproj files live in different directories, even when one has a dependency on the other, I recommend putting the different .nuspec files in different directories, even if MyProject is a nuget dependency of AdditionalMyProject.
answered Nov 14 at 21:15
Ziv
909616
AdditionalMyProject.nuspec is a different project, even if it doesn't have a MSBuild project associated (it is a different .nupkg after all), so you're less likely to have tooling problems if you keep the nuspec in its own directory. Similar to how different csproj files live in different directories, even when one has a dependency on the other, I recommend putting the different .nuspec files in different directories, even if MyProject is a nuget dependency of AdditionalMyProject.
answered Nov 14 at 21:15
Ziv
909616
answered Nov 14 at 21:15
Ziv
909616
answered Nov 14 at 21:15
Ziv
909616
answered Nov 14 at 21:15
Ziv
909616
909616
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53204764%2fnuget-pack-csproj-with-custom-nuspec-metadata%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I don't understand the purpose of AdditionalMyProject.nuspec. If there's another project that has a dependency on MyProject, I don't see why you would need a special nuspec for MyProject. This might be a case of the XY problem. Why do you want two nuspec files?
– Ziv
Nov 8 at 22:01
@Ziv I would like to provide two packages with different purpose. The AdditionalMyProject.nuspec should provide dependencies to other nuget packages including MyProject.nupkg. MyProject is only base package for a defined purpose.
– Mi. Sharp
Nov 12 at 10:35
if AdditionalMyProject is a meta package, then there's no need for the nuspec to be in the same folder as the csproj, right? move it to its own folder, then there's only 1 nuspec next to the csproj.
– Ziv
Nov 13 at 12:35
That's an answer which makes sense. I tried and it worked, can you post it as answer?
– Mi. Sharp
Nov 14 at 13:44