Michał Ziemski
Michał Ziemski
**Windows:** ``` Starting OmniSharp server at 2017-11-9 14:33:55 Target: f:\code4\c OmniSharp server started Path: C:\Users\gleba\.vscode\extensions\ms-vscode.csharp-1.13.0\.omnisharp\OmniSharp.exe PID: 10752 [info]: OmniSharp.MSBuild.Discovery.MSBuildLocator Located 1 MSBuild instance(s) 1: StandAlone 15.0 - "C:\Users\gleba\.vscode\extensions\ms-vscode.csharp-1.13.0\.omnisharp\msbuild\15.0\Bin" [info]: OmniSharp.MSBuild.Discovery.MSBuildLocator...
Both VS 2017 and build tools (latest ver)
C# and F# installed in both VS2017 and build tools
and MSBuild installed in VS2017
I was finnaly able to resolve on Linux. After installing missing msbuild the assemlby load error was gone and the "GetTargetPath" error was back. I was also missing the fsharp...
The previous log was after everything was installed
Hi! Also a user with hundreds of databases in 2.5 looking to migrate to 4.0 in the future. I think more macros in replication.conf would be a viable solution. Alternatively...
That doesn't seem to be the case. I'm using the official Firebird-4.0.2.2816.amd64 on Linux The journal file is named ```.journal-000000003``` In the config the prefix is per default unspecified (commented...
Same here in omnisharp-vscode. Replacing the ```System.Composition.AttributedModel.dll``` (6.0.0) with the newest 7.0.0 seems to fix the problem
replication.conf: ``` database { journal_directory = /srv/j journal_archive_directory = /srv/ja journal_archive_timeout = 60 } ``` The file is on a local filesystem