.Net MVC Core Modular Project Structure and Managing
0
As company, we want to deploy our .net desktop project to MVC Core web application. We have 30 different modules and one of them is developed by different developers. Also one module can be used in another module. How can we achieve it in terms of project structure in Visual Studio? We don't want to build one project including all of modules. Each module will be delivered to different solution for different developer in our company. Basic menu and modules structures is as below:
Main Project : TicariEntegreMenu.WebUI.dll (AnaMenu)
1) Login
2) Session Info
3) Menu / Modules
1. Stok Module (Stok.WebUI)
1.1 İşlemler
1.1.1 Stok Kartı Tanıtımı (Stok.WebUI.Controller.Stok.StokKarti)
1.1.2 Stok Fiyat Güncelleme (Stok.WebUI.Controller.Stok.FiyatGuncelle)
1.1.3 Depo Girişi
1.1.4 Depo Çıkısı
1.2 Raporlar
1.2.1 Stok Kartı Raporu
1.2.2 Stok Envanter Raporu
2. Fatura Modülü (Fatura.WebUI)
2.1 İşlemler
2.1.1 Alış Faturası (Fatura.WebUI.Controller.Fatura.Alis)
2.2.2 Satış Faturası (Fatura.WebUI.Controller.Fatura.Satis)
2.2 Raporlar
....
....
...
Stok.WebUI bir proje Stok.WebUI.dll / Stok.WebUI.Views.dll
Fatura.WebUI bir proje Fatura.WebUI.dll / Fatura.WebUI.Views.dll
c# visual-studio model-view-controller asp.net-core
asked Nov 22 '18 at 5:47
Gökhan AldanmazGökhan Aldanmaz
2115
add a comment |
0
As company, we want to deploy our .net desktop project to MVC Core web application. We have 30 different modules and one of them is developed by different developers. Also one module can be used in another module. How can we achieve it in terms of project structure in Visual Studio? We don't want to build one project including all of modules. Each module will be delivered to different solution for different developer in our company. Basic menu and modules structures is as below:
Main Project : TicariEntegreMenu.WebUI.dll (AnaMenu)
1) Login
2) Session Info
3) Menu / Modules
1. Stok Module (Stok.WebUI)
1.1 İşlemler
1.1.1 Stok Kartı Tanıtımı (Stok.WebUI.Controller.Stok.StokKarti)
1.1.2 Stok Fiyat Güncelleme (Stok.WebUI.Controller.Stok.FiyatGuncelle)
1.1.3 Depo Girişi
1.1.4 Depo Çıkısı
1.2 Raporlar
1.2.1 Stok Kartı Raporu
1.2.2 Stok Envanter Raporu
2. Fatura Modülü (Fatura.WebUI)
2.1 İşlemler
2.1.1 Alış Faturası (Fatura.WebUI.Controller.Fatura.Alis)
2.2.2 Satış Faturası (Fatura.WebUI.Controller.Fatura.Satis)
2.2 Raporlar
....
....
...
Stok.WebUI bir proje Stok.WebUI.dll / Stok.WebUI.Views.dll
Fatura.WebUI bir proje Fatura.WebUI.dll / Fatura.WebUI.Views.dll
c# visual-studio model-view-controller asp.net-core
asked Nov 22 '18 at 5:47
Gökhan AldanmazGökhan Aldanmaz
2115
"one module can be used in another module" - interfaces in a third shared module and dependency injection can help with that, depending on the specifics.
– John
Nov 22 '18 at 5:49
1
You can still create a single solution file with segmented over multiple class libraries. If you really need to separate solution for different developers, then deploy them as nuget packages, and other developers can import them in their project. But line by line debugging will get hit by that.
– Teoman shipahi
Nov 22 '18 at 5:51
Good approach for me. But can you give an example or link for this? Thanks for useful answer. @Teomanshipahi
– Gökhan Aldanmaz
Nov 22 '18 at 5:57
add a comment |
0
0
0
As company, we want to deploy our .net desktop project to MVC Core web application. We have 30 different modules and one of them is developed by different developers. Also one module can be used in another module. How can we achieve it in terms of project structure in Visual Studio? We don't want to build one project including all of modules. Each module will be delivered to different solution for different developer in our company. Basic menu and modules structures is as below:
Main Project : TicariEntegreMenu.WebUI.dll (AnaMenu)
1) Login
2) Session Info
3) Menu / Modules
1. Stok Module (Stok.WebUI)
1.1 İşlemler
1.1.1 Stok Kartı Tanıtımı (Stok.WebUI.Controller.Stok.StokKarti)
1.1.2 Stok Fiyat Güncelleme (Stok.WebUI.Controller.Stok.FiyatGuncelle)
1.1.3 Depo Girişi
1.1.4 Depo Çıkısı
1.2 Raporlar
1.2.1 Stok Kartı Raporu
1.2.2 Stok Envanter Raporu
2. Fatura Modülü (Fatura.WebUI)
2.1 İşlemler
2.1.1 Alış Faturası (Fatura.WebUI.Controller.Fatura.Alis)
2.2.2 Satış Faturası (Fatura.WebUI.Controller.Fatura.Satis)
2.2 Raporlar
....
....
...
Stok.WebUI bir proje Stok.WebUI.dll / Stok.WebUI.Views.dll
Fatura.WebUI bir proje Fatura.WebUI.dll / Fatura.WebUI.Views.dll
c# visual-studio model-view-controller asp.net-core
asked Nov 22 '18 at 5:47
Gökhan AldanmazGökhan Aldanmaz
2115
As company, we want to deploy our .net desktop project to MVC Core web application. We have 30 different modules and one of them is developed by different developers. Also one module can be used in another module. How can we achieve it in terms of project structure in Visual Studio? We don't want to build one project including all of modules. Each module will be delivered to different solution for different developer in our company. Basic menu and modules structures is as below:
Main Project : TicariEntegreMenu.WebUI.dll (AnaMenu)
1) Login
2) Session Info
3) Menu / Modules
1. Stok Module (Stok.WebUI)
1.1 İşlemler
1.1.1 Stok Kartı Tanıtımı (Stok.WebUI.Controller.Stok.StokKarti)
1.1.2 Stok Fiyat Güncelleme (Stok.WebUI.Controller.Stok.FiyatGuncelle)
1.1.3 Depo Girişi
1.1.4 Depo Çıkısı
1.2 Raporlar
1.2.1 Stok Kartı Raporu
1.2.2 Stok Envanter Raporu
2. Fatura Modülü (Fatura.WebUI)
2.1 İşlemler
2.1.1 Alış Faturası (Fatura.WebUI.Controller.Fatura.Alis)
2.2.2 Satış Faturası (Fatura.WebUI.Controller.Fatura.Satis)
2.2 Raporlar
....
....
...
Stok.WebUI bir proje Stok.WebUI.dll / Stok.WebUI.Views.dll
Fatura.WebUI bir proje Fatura.WebUI.dll / Fatura.WebUI.Views.dll
c# visual-studio model-view-controller asp.net-core
c# visual-studio model-view-controller asp.net-core
asked Nov 22 '18 at 5:47
Gökhan AldanmazGökhan Aldanmaz
2115
asked Nov 22 '18 at 5:47
Gökhan AldanmazGökhan Aldanmaz
2115
asked Nov 22 '18 at 5:47
Gökhan AldanmazGökhan Aldanmaz
2115
asked Nov 22 '18 at 5:47
Gökhan AldanmazGökhan Aldanmaz
2115
asked Nov 22 '18 at 5:47
Gökhan AldanmazGökhan Aldanmaz
2115
2115
"one module can be used in another module" - interfaces in a third shared module and dependency injection can help with that, depending on the specifics.
– John
Nov 22 '18 at 5:49
1
You can still create a single solution file with segmented over multiple class libraries. If you really need to separate solution for different developers, then deploy them as nuget packages, and other developers can import them in their project. But line by line debugging will get hit by that.
– Teoman shipahi
Nov 22 '18 at 5:51
Good approach for me. But can you give an example or link for this? Thanks for useful answer. @Teomanshipahi
– Gökhan Aldanmaz
Nov 22 '18 at 5:57
add a comment |
"one module can be used in another module" - interfaces in a third shared module and dependency injection can help with that, depending on the specifics.
– John
Nov 22 '18 at 5:49
1
You can still create a single solution file with segmented over multiple class libraries. If you really need to separate solution for different developers, then deploy them as nuget packages, and other developers can import them in their project. But line by line debugging will get hit by that.
– Teoman shipahi
Nov 22 '18 at 5:51
Good approach for me. But can you give an example or link for this? Thanks for useful answer. @Teomanshipahi
– Gökhan Aldanmaz
Nov 22 '18 at 5:57
"one module can be used in another module" - interfaces in a third shared module and dependency injection can help with that, depending on the specifics.
– John
Nov 22 '18 at 5:49
"one module can be used in another module" - interfaces in a third shared module and dependency injection can help with that, depending on the specifics.
– John
Nov 22 '18 at 5:49
1
1
You can still create a single solution file with segmented over multiple class libraries. If you really need to separate solution for different developers, then deploy them as nuget packages, and other developers can import them in their project. But line by line debugging will get hit by that.
– Teoman shipahi
Nov 22 '18 at 5:51
You can still create a single solution file with segmented over multiple class libraries. If you really need to separate solution for different developers, then deploy them as nuget packages, and other developers can import them in their project. But line by line debugging will get hit by that.
– Teoman shipahi
Nov 22 '18 at 5:51
Good approach for me. But can you give an example or link for this? Thanks for useful answer. @Teomanshipahi
– Gökhan Aldanmaz
Nov 22 '18 at 5:57
Good approach for me. But can you give an example or link for this? Thanks for useful answer. @Teomanshipahi
– Gökhan Aldanmaz
Nov 22 '18 at 5:57
add a comment |
0
active
oldest
votes
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
});
}
});
draft saved
draft discarded
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%2f53424594%2fnet-mvc-core-modular-project-structure-and-managing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f53424594%2fnet-mvc-core-modular-project-structure-and-managing%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
"one module can be used in another module" - interfaces in a third shared module and dependency injection can help with that, depending on the specifics.
– John
Nov 22 '18 at 5:49
1
You can still create a single solution file with segmented over multiple class libraries. If you really need to separate solution for different developers, then deploy them as nuget packages, and other developers can import them in their project. But line by line debugging will get hit by that.
– Teoman shipahi
Nov 22 '18 at 5:51
Good approach for me. But can you give an example or link for this? Thanks for useful answer. @Teomanshipahi
– Gökhan Aldanmaz
Nov 22 '18 at 5:57