Mongo2Go

Absolute path stays unchanged, relative path will be relative to current executing directory (usually the /bin folder)

Returns and reserves a new port

Returns the if it is verified that it does not contain any mongod argument already defined by Mongo2Go.

mongod arguments defined by Mongo2Go Additional mongod arguments contains at least one mongod argument already defined by Mongo2Go A string with the additional mongod arguments

Starts a new process. Process can be killed

Starts a new process.

Input File: Absolute path stays unchanged, relative path will be relative to current executing directory (usually the /bin folder)

Output File: Absolute path stays unchanged, relative path will be relative to current executing directory (usually the /bin folder)

Structure of a log generated by mongod. Used to deserialize the logs and pass them to an ILogger. See: https://docs.mongodb.com/manual/reference/log-messages/#json-log-output-format Note: "truncated" and "size" are not parsed as we're unsure how to properly parse and use them.

Severity of the logs as defined by MongoDB. Mapped to LogLevel as defined by Microsoft. D1-D2 mapped to Debug level. D3-D5 mapped Trace level.

Intention: port numbers won't be assigned twice to avoid connection problems with integration tests

Returns and reserves a new port

Reads from Output stream to determine if process is ready

Send the mongod process logs to .NET's console and debug outputs.

Parses and redirects mongod logs to ILogger.

saves about 40 keystrokes

Populates the template using the provided arguments and the invariant culture

Populates the template using the provided arguments using the provided formatter

Mongo2Go main entry point

State of the current MongoDB instance

Connections string that should be used to establish a connection the MongoDB instance

Starts Multiple MongoDB instances with each call On dispose: kills them and deletes their data directory

(Optional) If null, mongod logs are wired to .NET's Console and Debug output (provided you haven't added the --quiet additional argument). If not null, mongod logs are parsed and wired to the provided logger. Should be used for integration tests

!!! This method is only used for an internal unit test. Use MongoDbRunner.Start() instead. But if you find it to be useful (eg. to change every aspect on your own) feel free to implement the interfaces on your own!

see https://github.com/Mongo2Go/Mongo2Go/issues/41

Only starts one single MongoDB instance (even on multiple calls), does not kill it, does not delete data

Should be used for local debugging only WARNING: one single instance on one single machine is not a suitable setup for productive environments!!!

!!! This method is only used for an internal unit test. Use MongoDbRunner.StartForDebugging() instead. But if you find it to be useful (eg. to change every aspect on your own) feel free to implement the interfaces on your own!

see https://github.com/Mongo2Go/Mongo2Go/issues/41

Executes Mongoimport on the associated MongoDB Instace

Executes Mongoexport on the associated MongoDB Instace

usage: local debugging

usage: integration tests