I have a solution - for example, called MyCompany.
MyCompany has many projects, for example:
- MyCompany.Common (common class library - doesn't contain references to other MyCompany assemblies)
- MyComapny.Entites (Business objects)
- MyCompany.Data(Data layer)
- MyCompany.Logic(BLL layer)
- MyCompany.Web (web ui)
- MyCompany.SuperWindowsService (a windows service)
- MyCompany.WindowsApp
I am looking for advice on how best to deploy parts of this app - for example-
server1: this is a web server, and requires MyCompany.Web, but it also needs to run MyCompany.SuperWindowsService.
Currently, I've set up an installer project to install the Windows service, for example, to Program Files\MyCompany\ The problem is, that in the directory, it also has:
- MyComapny.Entites.dll
- MyCompany.Data.dll
- MyCompany.Logic.dll
within the directory. Obvioulsy, the Web application's bin directory also has these dll's
Is this "ok"?
I take it, when i deploy my windows app to some other client, it will also contain all these assemblies...?