Commit graph

9 commits

Author SHA1 Message Date
Mike Dickson
580ffb5b6a
Feature/project restructure (#88)
Some checks are pending
CodeQL / Analyze (push) Waiting to run
dotnet package / build (8.0.x) (push) Waiting to run
dotnet package / build (9.0.x) (push) Waiting to run
* First pass to allow bulding different build artifact types (libraries, exes, web apps, etc) from the same tree.  Each project is seperated physically and can have a local obj and bin directory wehen building.  We assemble a release using dotnet publish.

This still needs a few changes and  updates for compilation.  I want to get the structural changes made however and committed locally at least.

* Rename some Assembly attribute files to Addin.cs and strip them down to just plugin info so we can use generated Assembly information.    A few additions to csproj dependencies to get things to compile.

* Cleanup Directory.build.props. Make it reflect using the standard directories for output and publish to assemble a release.

* Restructure Projects so they are no longer nested (no need to remove files from compilation) and there can be project types in the solution that use a different SDK.  We need the last bit in order to do ASP.NET in the same solution tree.  Goal is to be able to dotnet publish and get useable output.

* Move OpenSim.sln to OpenSim.Server.RegionServer so the Server instances have similar naming (MoneyServer and RobustServer).

* Added a Data directory for each of the *.Server.* packages and put Server specific configuration here.   Added a rule to csproj to install the configuration into the bin directory on a build.   There are now OpenSim.Server.{RegionServer|RobustServer|MoneyServer} executables and if publish is used a platform specific binary will be built.  Next step from this is Docker files to run each of the server components.

* More changes to get libs to resolve cleanly while we are in transition from mono addins.

* Move projects under Source in solution tree.

* Update nuget packages to address a vulnerability and pick up updates.

* Add metadata to create NuGet Package for EF Core Data Models.

* Include dlls we just carry in bin in the output directory when building.

* Bump version.  Some changes to not publish test components.
2024-10-16 15:19:52 -04:00
Mike Dickson
d64ff145cd
Feature/lsd fix (#83)
Some checks failed
CodeQL / Analyze (csharp) (push) Has been cancelled
dotnet package / build (8.0.x) (push) Has been cancelled
dotnet package / build (9.0.x) (push) Has been cancelled
* Placeholders for AISv3.  EF Core Model code in OpenSim.Data.Models.  Both projects are in the Source directory and not yet included in the solution.  Tests are added back in Tests.  Still need to Add the LinkSet Data tests and activate them in the solution.

* Add PBR Terrain fields to ef core regionsettings table. Add OpenSIm.Data.Models to solution.

* Restructure the LinksetData Deserialize.  We'll also save the size value so it doesnt need to be calculated.  We make the size a required field so we can tell if its not present and fall back to handling the old format as well.  Make the serialized fields writable publically so they can be deserialized successfully. This is a change in dotnet 8.

* Address CodeQL comments. Ternary operator in LinksetData Deserialize and rename some generated code for the Search tables ef core support away from Object which is of course a reserved word.
2024-08-06 11:14:16 -04:00
Mike Dickson
17b1778cd5 Clean up references to runtime classes that are explicitely listed and coming from bin 2024-05-18 11:12:52 -04:00
Mike Dickson
f43ce8f71f Bump to DotNet Core 8.0 to match upstream. They are still disabling dependency generation and checking which disables a big security element of the framework. More on that in Tranquillity. 2024-04-23 17:37:15 -04:00
Mike Dickson
84dad27997 Merge -maint down to develop for testing. We're using the static AssemblyInfo.cs again instead of the generated values. Hopefully this helps to address plugin loading. 2023-01-08 16:10:10 -05:00
Mike Dickson
e5b8f09dde Changes to version strings to rationalize things. The Assembly version follows the stricter Version field used for assembly loading while PackageVersion defines a Human readable version string. 2021-08-15 01:30:21 -04:00
mdicvkson
d174ba5d22 Low hanging fruit. Remove all the AssemblyInfo.cs files for those projects that don't use Mono.Addins. We'll let the build system generate AssemblyInfo.cs from project metadata. 2021-05-16 13:23:22 -04:00
Mike Dickson
ff1c1a700a Put the AssemblyInfo.cs files back for now. The automatic generation in msbuild doesn't coexist nicely with Mono.Addins. We can revisit when/if we make Addins go away. 2021-05-15 20:30:16 -04:00
mdicvkson
c59e9a26e8 First pass changes to move to msbuild format 2021-05-15 12:23:16 -04:00