mirror of
https://github.com/quasar/Quasar.git
synced 2026-04-26 07:45:57 +03:00
[GH-ISSUE #522] Some changes work in DEBUG but not RELEASE #287
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#287
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 @Powershell-coder on GitHub (Sep 3, 2016).
Original GitHub issue: https://github.com/quasar/Quasar/issues/522
Hello
I added one feature.
When i test it in Debug mode it works correctly.
But when i use it in Release mode it doesnt work.
I also added this feature in assembly to be True or False.
What is problem ?
@MaxXor commented on GitHub (Sep 3, 2016):
I can only guess. Show me the code.
@0xE232FE commented on GitHub (Sep 7, 2016):
Same for File-Explorer feature. When I use the Release Version of Quasar Server I don't get Directory Listing in the ListView of the File-Explorer Window. When i click the Refresh button the Client Disconnects.
If I use the Debug Version of Quasar Server the File-Explorer works without any problems!
@d3agle commented on GitHub (Sep 7, 2016):
I noticed this as well, happens when running
release mode configuration in IDE. Some features will not work correctly, others will.@MaxXor commented on GitHub (Sep 7, 2016):
The release configuration is not meant to be used in the IDE, debugging won't work too. Only use the release configuration when you also want to build your client via the in-built builder, otherwise use the debug configuration.
@ghost commented on GitHub (Sep 7, 2016):
If live-debugging isn't working in Visual Studio, how are you debugging your client ?
@MaxXor commented on GitHub (Sep 7, 2016):
Use debug configuration.
@MaxXor commented on GitHub (Sep 15, 2016):
@0xE232FE @d3agle What exactly do you mean? I've built the client & server both in release and debug mode and everything works flawlessly, even tested to connect the debug client to the release server. The File Manager worked in all cases. Can you tell me the steps to reproduce the issue?
@ghost commented on GitHub (Sep 15, 2016):
I have encountered issues while playing with the code.
If client/server packets are differents, the Serializers (client/Server side) will be differents.
=> The TypeMapping will be different too, so if you send an GetAuthentication() packet from the client, the server will understand it as a DoClientUninstall().
Use step-by-step debugging & check if Serializer() (both client/server side) have the same number of registered/mapped packets.
It was the solution for me.
@MaxXor commented on GitHub (Sep 15, 2016):
@Perturabo Yes, that's intended as NetSerializer provides no versioning of the types but is therefore faster and has a smaller footprint. Every change to the packets will break the communication with the old server.
I provided a small step-by-step tutorial on how to avoid losing clients by making such changes: https://github.com/quasar/QuasarRAT/wiki/Updating-a-Client
But that's a different topic as the others stated that features don't work in release mode, but in debug mode. Maybe it's associated, idk.
@ghost commented on GitHub (Sep 15, 2016):
Imo the system is fine.
Back to the original problem, you should first check differences between DEBUG & RELEASE mode.
Try finding all occurences in Visual Studio of 'DEBUG'.
Code like "#if DEBUG [...]" might change the behaviour of your app in debug/release mode.