FazBrowse GitHub Viewer | Trending | | Home

Tools: [Download Repo ZIP] [Original HTTPS Page]

DotSpatial/Source at master · DotSpatial/DotSpatial · GitHub

Name		Name	Last commit message	Last commit date
parent directory ..
.nuget		.nuget
Core		Core
Documentation		Documentation
DotSpatial.WebControls		DotSpatial.WebControls
Examples		Examples
Extensions		Extensions
Plugins		Plugins
Tests		Tests
packages		packages
.editorconfig		.editorconfig
Compile_BuildTools2019.cmd		Compile_BuildTools2019.cmd
Directory.Build.props		Directory.Build.props
DotSpatial.WebControls.sln		DotSpatial.WebControls.sln
DotSpatial.sln		DotSpatial.sln
Licence.txt		Licence.txt
NuGet.Config		NuGet.Config
Readme.md		Readme.md

Readme.md

DotSpatial

For documentation and code samples see https://github.com/DotSpatial/DotSpatial/wiki For discussions, questions and suggestions use https://github.com/DotSpatial/DotSpatial/discussions

Some sample projects there are at Examples folder. Use DemoMap.exe to see basic functionality of DotSpatial library.

Development agreement

Main namespace for core dlls - DotSpatial.*
Main namespace for plugins - DotSpatial.Plugins.*
Use AnyCPU target for projects always when it's possible.
Plugins which works only in Windows, should have output folder "..\Windows Extensions\PluginFolder".
Plugins which works in Windows and Mono, should have output folder "..\Plugins\PluginFolder".
Every release must be tagged in GIT.
Use branches when adding a lot of changes.
Write unit-tests, when it is possible.
Use resources for message strings. Use language-specific .resx files when needed to localize GUI.

Back | FazBrowse Home | New Git URL