Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Target Framework to .NET 4.5
See original GitHub issueFeature proposal
DotSpatial currently targets .NET 4 CP. I just want to put in the proposal to switch to .NET 4.5 for the upcoming 2.0 version since that seems like a good time to do so.
The reason is mostly that the newer .NET 4.5 offers the async/await pattern that could to leveraged in the IO-heavy components of DotSpatial. I am thinking especially about DotSpatial.Data.
Adding *Async functions there will improve the usability of DotSpatial, especially when used inside a UI.
Issue Analytics
- State:
- Created 7 years ago
- Comments:16 (16 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I know that. But .NET Core makes it extremely easy to support multiple targets because the IDE tells you what functions are available and what functions are not. Also it allows very easy switching of the current target framework during development.
btw, we can build assemblies\nuget packages for various .net targets without using .net core. Simply use msbuild scripts fro that.