mirror of
https://github.com/quasar/Quasar.git
synced 2026-04-26 07:45:57 +03:00
[GH-ISSUE #130] Common classes #65
Labels
No labels
bug
bug
cant-reproduce
discussion
duplicate
easy
enhancement
help wanted
improvement
invalid
need more info
pull-request
question
wont-add
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Quasar#65
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tidusjar on GitHub (May 14, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/130
Hi,
I have a question why we are duplicating work?
There seems to be a few 'common' classes in the solution where they are duplicated in both projects. e.g. encryption. Why do we not have a 'Common' Project with these classes in that the other projects just reference?
@MaxXor commented on GitHub (May 14, 2015):
I want the client to have no dependencies except the default ones from the .net framework.
@tidusjar commented on GitHub (May 14, 2015):
Why can't we have a dependency on our own controlled, small library? I'm just thinking it would help out with the project structure and maintainability.
@yankejustin commented on GitHub (May 14, 2015):
@MaxXor I think you may have misunderstood @tidusjar
If I am understanding correctly, tidusjar is suggesting that we move code that is the same for the server and the client (for example: protobuf) to another project and have the server and use the same project so we don't have to make a change to the server or client, then reflect the change to the other project. Doing this would mean we only have to change one and it would be unnecessary to require a duplicate change in the other project.
@tidusjar commented on GitHub (May 14, 2015):
@yankejustin Correct. We would then only make the change in one location and it would be consistent across the server and client. But it would require 1 more .DLL
@MaxXor commented on GitHub (May 14, 2015):
@tidusjar and I don't allow this one more DLL, sorry.
@rabbitsmith commented on GitHub (May 25, 2015):
@MaxXor i think this is feasible.we can use ilmerge to combine the protobuf dll , encryption dll and client.exe after compiling them. simply search in google for ilmerge.exe.
@rabbitsmith commented on GitHub (May 25, 2015):
we can merge mono.cecil with xrat.exe