Mixing
Create a .Net project strictly for composition of NuGet packages
I'd like to create a .Net project (.Net Framework, not Core) that exists strictly for the sake of composing various other NuGet packages.
I have a plugin-based system where all plugins are NuGet packages and the core-system itself is a NuGet package. The core system is useless without the plugins, it is strictly an engine that knows how to run the plugins. Because I do not want to include references to plugins in my core system, I need an entirely separate project which is the composition of both the core system package and the plugins I'd like to use. I'm calling this my "composition" project where I am "composing" all the elements together prior to deploying to our server.
Example of existing projects / packages:
- Core System (NuGet package... should not directly reference plugins)
- Plugins
- Plugin 1 (NuGet package)
- Plugin 2 (NuGet package)
- Etc. (NuGet package)
Hypothetical "composition" project:
- Composition Project
- Reference -> Core System
- Reference -> Plugin 1
- Reference -> Plugin 2
Is there a way to have a project that is nothing more than references to NuGet packages but does not produce its own assembly? Perhaps this could be done with MSBuild trickery.
c# .net msbuild nuget
asked Jan 2 at 17:57
Ryan GriffithRyan Griffith
999831
add a comment |
I'd like to create a .Net project (.Net Framework, not Core) that exists strictly for the sake of composing various other NuGet packages.
I have a plugin-based system where all plugins are NuGet packages and the core-system itself is a NuGet package. The core system is useless without the plugins, it is strictly an engine that knows how to run the plugins. Because I do not want to include references to plugins in my core system, I need an entirely separate project which is the composition of both the core system package and the plugins I'd like to use. I'm calling this my "composition" project where I am "composing" all the elements together prior to deploying to our server.
Example of existing projects / packages:
- Core System (NuGet package... should not directly reference plugins)
- Plugins
- Plugin 1 (NuGet package)
- Plugin 2 (NuGet package)
- Etc. (NuGet package)
Hypothetical "composition" project:
- Composition Project
- Reference -> Core System
- Reference -> Plugin 1
- Reference -> Plugin 2
Is there a way to have a project that is nothing more than references to NuGet packages but does not produce its own assembly? Perhaps this could be done with MSBuild trickery.
c# .net msbuild nuget
asked Jan 2 at 17:57
Ryan GriffithRyan Griffith
999831
NuProj or NuGetizer might be something worth looking at. You should be able to create a composition project and build a meta-package using either of these tools.
– Matt Ward
Jan 2 at 18:31
add a comment |
I'd like to create a .Net project (.Net Framework, not Core) that exists strictly for the sake of composing various other NuGet packages.
I have a plugin-based system where all plugins are NuGet packages and the core-system itself is a NuGet package. The core system is useless without the plugins, it is strictly an engine that knows how to run the plugins. Because I do not want to include references to plugins in my core system, I need an entirely separate project which is the composition of both the core system package and the plugins I'd like to use. I'm calling this my "composition" project where I am "composing" all the elements together prior to deploying to our server.
Example of existing projects / packages:
- Core System (NuGet package... should not directly reference plugins)
- Plugins
- Plugin 1 (NuGet package)
- Plugin 2 (NuGet package)
- Etc. (NuGet package)
Hypothetical "composition" project:
- Composition Project
- Reference -> Core System
- Reference -> Plugin 1
- Reference -> Plugin 2
Is there a way to have a project that is nothing more than references to NuGet packages but does not produce its own assembly? Perhaps this could be done with MSBuild trickery.
c# .net msbuild nuget
asked Jan 2 at 17:57
Ryan GriffithRyan Griffith
999831
I'd like to create a .Net project (.Net Framework, not Core) that exists strictly for the sake of composing various other NuGet packages.
I have a plugin-based system where all plugins are NuGet packages and the core-system itself is a NuGet package. The core system is useless without the plugins, it is strictly an engine that knows how to run the plugins. Because I do not want to include references to plugins in my core system, I need an entirely separate project which is the composition of both the core system package and the plugins I'd like to use. I'm calling this my "composition" project where I am "composing" all the elements together prior to deploying to our server.
Example of existing projects / packages:
- Core System (NuGet package... should not directly reference plugins)
- Plugins
- Plugin 1 (NuGet package)
- Plugin 2 (NuGet package)
- Etc. (NuGet package)
Hypothetical "composition" project:
- Composition Project
- Reference -> Core System
- Reference -> Plugin 1
- Reference -> Plugin 2
Is there a way to have a project that is nothing more than references to NuGet packages but does not produce its own assembly? Perhaps this could be done with MSBuild trickery.
c# .net msbuild nuget
c# .net msbuild nuget
asked Jan 2 at 17:57
Ryan GriffithRyan Griffith
999831
asked Jan 2 at 17:57
Ryan GriffithRyan Griffith
999831
asked Jan 2 at 17:57
Ryan GriffithRyan Griffith
999831
asked Jan 2 at 17:57
Ryan GriffithRyan Griffith
999831
asked Jan 2 at 17:57
Ryan GriffithRyan Griffith
999831
999831
NuProj or NuGetizer might be something worth looking at. You should be able to create a composition project and build a meta-package using either of these tools.
– Matt Ward
Jan 2 at 18:31
add a comment |
NuProj or NuGetizer might be something worth looking at. You should be able to create a composition project and build a meta-package using either of these tools.
– Matt Ward
Jan 2 at 18:31
NuProj or NuGetizer might be something worth looking at. You should be able to create a composition project and build a meta-package using either of these tools.
– Matt Ward
Jan 2 at 18:31
NuProj or NuGetizer might be something worth looking at. You should be able to create a composition project and build a meta-package using either of these tools.
– Matt Ward
Jan 2 at 18:31
add a comment |
1 Answer
1
active
oldest
votes
I don't know of a way that just pulls down nuget packages with an assembly to be attached to.
But that's ok though. We have also done this here at our company. We have a solution and one .csproj file that brings in all the nuget packages that everything (Hundreds of other projects) needs. And of course it produces an associated .DLL. But that is ok, just have a post build step that deletes it.
answered Jan 3 at 16:34
C JohnsonC Johnson
10.9k84364
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f54011001%2fcreate-a-net-project-strictly-for-composition-of-nuget-packages%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I don't know of a way that just pulls down nuget packages with an assembly to be attached to.
But that's ok though. We have also done this here at our company. We have a solution and one .csproj file that brings in all the nuget packages that everything (Hundreds of other projects) needs. And of course it produces an associated .DLL. But that is ok, just have a post build step that deletes it.
answered Jan 3 at 16:34
C JohnsonC Johnson
10.9k84364
add a comment |
I don't know of a way that just pulls down nuget packages with an assembly to be attached to.
But that's ok though. We have also done this here at our company. We have a solution and one .csproj file that brings in all the nuget packages that everything (Hundreds of other projects) needs. And of course it produces an associated .DLL. But that is ok, just have a post build step that deletes it.
answered Jan 3 at 16:34
C JohnsonC Johnson
10.9k84364
add a comment |
I don't know of a way that just pulls down nuget packages with an assembly to be attached to.
But that's ok though. We have also done this here at our company. We have a solution and one .csproj file that brings in all the nuget packages that everything (Hundreds of other projects) needs. And of course it produces an associated .DLL. But that is ok, just have a post build step that deletes it.
answered Jan 3 at 16:34
C JohnsonC Johnson
10.9k84364
I don't know of a way that just pulls down nuget packages with an assembly to be attached to.
But that's ok though. We have also done this here at our company. We have a solution and one .csproj file that brings in all the nuget packages that everything (Hundreds of other projects) needs. And of course it produces an associated .DLL. But that is ok, just have a post build step that deletes it.
answered Jan 3 at 16:34
C JohnsonC Johnson
10.9k84364
answered Jan 3 at 16:34
C JohnsonC Johnson
10.9k84364
answered Jan 3 at 16:34
C JohnsonC Johnson
10.9k84364
answered Jan 3 at 16:34
C JohnsonC Johnson
10.9k84364
10.9k84364
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.
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%2f54011001%2fcreate-a-net-project-strictly-for-composition-of-nuget-packages%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
NuProj or NuGetizer might be something worth looking at. You should be able to create a composition project and build a meta-package using either of these tools.
– Matt Ward
Jan 2 at 18:31