Age | Commit message (Collapse) | Author |
|
* HtmlGenerator: Load converters lazily
This is a workaround so that .NET 6 apps can use the .NET FW
build of monodoc.dll without worrying about TypeInitializationExceptions
for converters they don't use.
* Fix netstandard2.0 compatibility
* Replace SharpZipLib submodule with package reference
Remove mdoc/packages.config as well.
* Bump Lucene.Net.Light to latest version to support NetStandard
* monodoc: Change to SDK-style project
* monodoc: Move to netstandard2.0
* Replace all packages.config with PackageReference
Bump mdoc.Test.FSharp.fsproj to .NET 4.7.1 to fix issues using
System.ValueTuple.
* Adjust to mdoc.Test.FSharp.fsproj bump to v4.7.1
* mdoc.Test.FSharp.fsproj: Convert to SDK-style
Fixes errors building in VS2022.
* mdoc.Test.csproj: Update to SDK-style too
* mdoc.Test.csproj no longer needs a direct FSharp.Core reference
* mdoc.Test.FSharp.fsproj: Fix FSharp.Core reference
https://github.com/dotnet/fsharp/blob/main/docs/fsharp-core-notes.md#how-to-explicitly-reference-fsharpcore
* mdoc.Test.csproj: Restore manual WPF reference
* Use AppendTargetFrameworkToOutputPath to avoid touching Makefiles
* Update en.expected-fsharp/index.xml
|
|
|
|
|
|
|
|
They don't build on VSTS mac CI agents
|
|
Resolves #116
|
|
Closes #132
|
|
Added F# signatures and usage formatter
Added unit and integration tests
Closes #108
|
|
Previously, mdoc simply used the compiler-generated method names for operators, such as `op_Multiply`, instead
of `operator *`. This releases fixes that for all unary, binary, comparison, and conversion operators.
Closes #82
|
|
|
|
Resolves #49. Additionally, enabled optimizations in release mode.
|
|
You can `make prepare all check` to compile and run unit tests.
Additionally, you can open `apidoctools.sln` in Visual Studio to develop and debug.
_Please Note:_ You will have to `make prepare all CONFIGURATION=Debug` for VS to work, as this
compiles external dependencies, and copies them to the `bin/Debug` folder, where VS will be expecting them.
|