Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change plugin projects to netstandard and sdk style csproj's #741

Merged
merged 1 commit into from
Apr 23, 2020
Merged

Change plugin projects to netstandard and sdk style csproj's #741

merged 1 commit into from
Apr 23, 2020

Conversation

Barsonax
Copy link
Member

@Barsonax Barsonax commented Aug 5, 2019

Changes:

  • All pcl projects have been converted to netstandard
  • Updated net framework nuspecs that still were using net45 to net472, I think we forgot to do this in the past.
  • Moved most of the stuff that was in AssemblyInfo.cs to the csproj itself. With net sdk style projects the default is to put things like version and other metadata in the csproj.
  • Updated the nuspecs and also added targetframework groups (this is the same as the default output when you pack a project).

Also solves #743

@Barsonax Barsonax changed the title Feature/netstandard barsonax Change plugin projects to netstandard and skd style csproj's Aug 5, 2019
Copy link
Member Author

@Barsonax Barsonax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some notes to self to clean up this branch a bit

Samples/FlapOrDie/FlapOrDie.csproj Outdated Show resolved Hide resolved
Test/Core/DualityTests.csproj Outdated Show resolved Hide resolved
@Barsonax Barsonax changed the title Change plugin projects to netstandard and skd style csproj's Change plugin projects to netstandard and sdk style csproj's Aug 5, 2019
@Barsonax
Copy link
Member Author

Rebased on latest master, changes are down from 59 to 32 files :)

@ilexp ilexp added this to the C# / .NET Upgrade milestone Aug 10, 2019
Comment on lines 8 to 10
<PropertyGroup>
<DualityPackageExcludeParentElement />
<StartAction>Program</StartAction>
<StartProgram>$(SolutionDir)Build\Output\DualityEditor.exe</StartProgram>
<StartWorkingDirectory>..\</StartWorkingDirectory>
<GenerateAssemblyInfo>false</GenerateAssemblyInfo>
</PropertyGroup>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indentation seems inconsistent in this file, similarly in other csproj files

@@ -230,6 +231,7 @@ public static string CreateNewProject(string projName, string projFolder, Projec
compileElement.AddAfterSelf(newCompileElement);
}
coreProject.Save(SourceCodeProjectCorePluginFile);
*/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just remove this entirely instead of commenting it out?

@ilexp ilexp added DevTool Area: Development tools and environment Task ToDo that's neither a Bug, nor a Feature labels Oct 29, 2019
Barsonax referenced this pull request Apr 21, 2020
…ckage management (#789)

#CHANGE: Removed package manager and new project logic in favor of csproj based package management, bumped version to 4.0.0-alpha
@Barsonax Barsonax requested review from ilexp and SirePi April 22, 2020 09:16
@Barsonax Barsonax self-assigned this Apr 22, 2020
@Barsonax Barsonax merged commit ef3b6b9 into AdamsLair:master Apr 23, 2020
@Barsonax Barsonax deleted the feature/netstandard_barsonax branch April 28, 2020 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DevTool Area: Development tools and environment Task ToDo that's neither a Bug, nor a Feature
Development

Successfully merging this pull request may close these issues.

Duality package structure and nuspec is wrong Switch From PCLs to .NET Standard
4 participants