To replicate this I created a Windows Console Project, C# .NET Framework 4.7.1 in Visual Studio Community 2017 Version 15.9.7.
I created a small example project based on the above steps (example_minbleic_d_2) into a fresh .NET Framework Console project. I ran into two issues:
- The methods at the end of the post aren't defined!
- After commenting out the lines below, I get the same AssemblyInfo.cs errors.
I now see what the problem is. If I make a new C# project and include all the AlgLib files (incl.
alglib_info.cs) in a C# project, Visual Studio defines its own assembly info in
Properties⇒AssemblyInfo.cs. That clashes with
alglib_info.cs. I think this would be avoided if AlgLib distributed the C# with a VS project, or mentioned this in the documentation.
I've attached the project (without some autogenerated stuff that should regenerate if you open the solution in Visual Studio) in a 7zip (had to to get it below 1MB) in case you want to refer to it.Code:
alglib.minbleicoptguardsmoothness(state);
alglib.minbleicoptguardgradient(state, 0.001);
...
Code:
alglib.optguardreport ogrep;
alglib.minbleicoptguardresults(state, out ogrep);
System.Console.WriteLine("{0}", ogrep.badgradsuspected); // EXPECTED: false
System.Console.WriteLine("{0}", ogrep.nonc0suspected); // EXPECTED: false
System.Console.WriteLine("{0}", ogrep.nonc1suspected); // EXPECTED: false
Login
Register
FAQ
Search
