mirror of
https://github.com/quasar/Quasar.git
synced 2026-04-25 15:25:59 +03:00
[GH-ISSUE #128] Upgrade to .NET Framework 3.5 #63
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#63
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 13, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/128
Originally assigned to: @MaxXor on GitHub.
This is a question:
Just wondering why we do not upgrade the .NET version? With 2.0 we cannot make use of any good asynchronous tasks? Multithreading is a lot more difficult and cumbersome in 2.0...
@bitterypaul commented on GitHub (May 13, 2015):
We can safely change the build config to target .NET 4.0 without breaking compatibility with Windows XP
@tidusjar commented on GitHub (May 13, 2015):
@bitterypaul I think it would be a good solution then we can use the more recent things in the .NET framework.
@DragonzMaster commented on GitHub (May 13, 2015):
that's to make the project compatible with most of OS
if we upgrade it to 3.5 (as an example) we won't be sure that it would work on most of Win XP as many of them uses 2.0
@tidusjar commented on GitHub (May 13, 2015):
@DragonzMaster I'm not questioning anyone here but if Microsoft don't support Win XP, should we? I can see a lot of benefit to upgrade the .NET version.
@yankejustin commented on GitHub (May 13, 2015):
@bitterypaul Of course. The .NET framework version has no reason to break compatibility with Windows XP.
@yankejustin commented on GitHub (May 13, 2015):
@DragonzMaster These days, most machines (even the few running Windows XP for some reason) should at least have v3.5
@yankejustin commented on GitHub (May 13, 2015):
I would agree with @tidusjar ... 3.5 is huge enough. Each version has an immense amount of wonderful changes to simplify and improve code.
@DragonzMaster commented on GitHub (May 13, 2015):
i know that win xp is the only one which come with 2.0 instead of 3.5 which came with win vista and newer
anyway you can do what you want
@tidusjar commented on GitHub (May 14, 2015):
@MaxXor what is you opinion on this?
@MaxXor commented on GitHub (May 14, 2015):
I believe it's okay if we change the target framework to 3.5. :)
I will do this later.
@yankejustin commented on GitHub (May 14, 2015):
Wonderful. :)
@yankejustin commented on GitHub (May 18, 2015):
@MaxXor Would you please create a new branch for upgrading the framework to 3.5? There are many places I see that would benefit greatly from the new features offered by v3.5
Also, would you consider changing the following code signature for invoking?:
Invoke((MethodInvoker)delegate { });to something like this:
Invoke(() => { });I just would like to add that the two empty parenthesis can be more clear because it can contain parameters, and empty parenthesis would show others that there are no parameters. :)
@MaxXor commented on GitHub (May 19, 2015):
@yankejustin
Yes, I'll do this. :)
Uhm, I think it's not that important to change the Invokes, or? 😕
@yankejustin commented on GitHub (May 19, 2015):
It is not that important. It is more of a preference. :)
@MaxXor commented on GitHub (May 22, 2015):
Upgrade is done, you can now start using more powerful methods from the .NET Framework 3.5 CP.
If there are any bugs, please report them.