120 lines
6.8 KiB
XML
120 lines
6.8 KiB
XML
<Project Sdk="Microsoft.NET.Sdk.Web">
|
|
|
|
<PropertyGroup>
|
|
<Copyright>Copyright © Nop Solutions, Ltd</Copyright>
|
|
<Company>Nop Solutions, Ltd</Company>
|
|
<Authors>Nop Solutions, Ltd</Authors>
|
|
<Version>4.80</Version>
|
|
<Description>Nop.Web is also an MVC web application project, a presentation layer for public store and admin area.</Description>
|
|
<PackageLicenseUrl>https://www.nopcommerce.com/license</PackageLicenseUrl>
|
|
<PackageProjectUrl>https://www.nopcommerce.com/</PackageProjectUrl>
|
|
<RepositoryUrl>https://github.com/nopSolutions/nopCommerce</RepositoryUrl>
|
|
<!--Starting with the .NET 6 SDK, the [Appname].runtimesettings.dev.json file is no longer generated by default at compile time. If you still want this file to be generated, set the GenerateRuntimeConfigDevFile property to true.-->
|
|
<GenerateRuntimeConfigDevFile>true</GenerateRuntimeConfigDevFile>
|
|
<!--Set this parameter to true to get the dlls copied from the NuGet cache to the output of your project-->
|
|
<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
|
|
<AspNetCoreHostingModel>InProcess</AspNetCoreHostingModel>
|
|
<!--When true, compiles and emits the Razor assembly as part of publishing the project-->
|
|
<RazorCompileOnPublish>false</RazorCompileOnPublish>
|
|
</PropertyGroup>
|
|
|
|
<ItemGroup>
|
|
<ProjectReference Include="..\..\Libraries\Nop.Core\Nop.Core.csproj" />
|
|
<ProjectReference Include="..\..\Libraries\Nop.Data\Nop.Data.csproj" />
|
|
<ProjectReference Include="..\..\Libraries\Nop.Services\Nop.Services.csproj" />
|
|
<ProjectReference Include="..\Nop.Web.Framework\Nop.Web.Framework.csproj" />
|
|
</ItemGroup>
|
|
|
|
<ItemGroup>
|
|
<!-- We copy the entire \App_Data directory. But we ignore JSON files and data protection keys -->
|
|
<Content Include="App_Data\**" CopyToPublishDirectory="PreserveNewest" Exclude="App_Data\*.json" />
|
|
<Content Remove="App_Data\*.json" />
|
|
<Content Update="App_Data\DataProtectionKeys\*.xml" CopyToPublishDirectory="Never" />
|
|
|
|
<Compile Remove="Plugins\**;Themes\**" />
|
|
<Content Remove="Plugins\**;Themes\**" />
|
|
<EmbeddedResource Remove="Plugins\**;Themes\**" />
|
|
<None Remove="Plugins\**;Themes\**" />
|
|
<None Include="Plugins\**" CopyToPublishDirectory="PreserveNewest" Exclude="Plugins\**\runtimes\**;Plugins\**\ref\**;Plugins\**\*.pdb" />
|
|
|
|
<Content Include="Themes\**" CopyToPublishDirectory="PreserveNewest" CopyToOutputDirectory="Never" />
|
|
|
|
<!-- We copy the \Logs directory -->
|
|
<Content Include="Logs\**" CopyToPublishDirectory="PreserveNewest" />
|
|
<Content Remove="appsettings.json" />
|
|
<None Remove="Plugins\Uploaded\placeholder.txt" />
|
|
<Content Include="Plugins\Uploaded\placeholder.txt">
|
|
<ExcludeFromSingleFile>true</ExcludeFromSingleFile>
|
|
<CopyToPublishDirectory>PreserveNewest</CopyToPublishDirectory>
|
|
</Content>
|
|
<None Include="appsettings.json">
|
|
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
|
|
</None>
|
|
<PackageReference Include="DevExpress.AspNetCore.Common" Version="25.1.3" />
|
|
<PackageReference Include="DevExtreme.AspNet.Core" Version="25.1.3" />
|
|
<PackageReference Include="DevExtreme.AspNet.Data" Version="5.1.0" />
|
|
<PackageReference Include="PdfPig" Version="0.1.11" />
|
|
|
|
<None Update="Areas\Admin\sitemap.config">
|
|
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
|
|
</None>
|
|
</ItemGroup>
|
|
|
|
<ItemGroup>
|
|
<!-- This setting fixes the problem caused by this update in the websdk in vs2019
|
|
https://github.com/aspnet/websdk/commit/7e6b193ddcf1eec5c0a88a9748c626775555273e#diff-edf5a48ed0d4aa5a4289cb857bf46a04
|
|
Therefore, we restore the standard configuration behavior (there was no copy to the output directory)
|
|
in order to avoid the "Duplicate dll" error during publication.
|
|
We can also use “ExcludeConfigFilesFromBuildOutput” according to https://github.com/aspnet/AspNetCore/issues/14017 -->
|
|
<Content Update="**\*.config;**\*.json" CopyToOutputDirectory="Never" CopyToPublishDirectory="PreserveNewest" />
|
|
</ItemGroup>
|
|
|
|
<!-- This target execute after "Build" target.
|
|
We use it to clean up folder with plugins from unnecessary and obsolete libraries. -->
|
|
<Target Name="NopTarget" AfterTargets="Build">
|
|
<ItemGroup>
|
|
<!-- Get plugin description files to get plugin paths -->
|
|
<PluginsDescription Include="$(MSBuildProjectDirectory)\Plugins\**\plugin.json;" />
|
|
<!-- Get paths for all plugins -->
|
|
<PluginsFolders Include="@(PluginsDescription->'%(relativedir)')" />
|
|
|
|
<!-- Get paths for ClearPluginAssemblies project -->
|
|
<ClearPluginAssemblies Include="$(MSBuildProjectDirectory)\..\..\Build\ClearPluginAssemblies.proj" />
|
|
|
|
</ItemGroup>
|
|
<PropertyGroup>
|
|
<PluginsFolders>@(PluginsFolders)</PluginsFolders>
|
|
</PropertyGroup>
|
|
<!-- When .NET Core builds a project, it copies all referenced libraries to the output folder.
|
|
For plugins it creates too many unnecessary files that just take up space.
|
|
At the moment you can't disable this behavior. That's why we have to manually delete all unnecessary libraries from plugin output directories. -->
|
|
<MSBuild Projects="@(ClearPluginAssemblies)" Properties="PluginPath=$(PluginsFolders)" Targets="NopClear" />
|
|
|
|
</Target>
|
|
|
|
<PropertyGroup>
|
|
<!--The common language runtime (CLR) supports two types of garbage collection:
|
|
workstation garbage collection, which is available on all systems, and server garbage collection,
|
|
which is available on multiprocessor systems.
|
|
|
|
For single-processor computers, the default workstation garbage collection should be the fastest option.
|
|
Either workstation or server can be used for two-processor computers.
|
|
Server garbage collection should be the fastest option for more than two processors.
|
|
|
|
More details about GC you can see here: https://docs.microsoft.com/en-us/dotnet/standard/garbage-collection/fundamentals-->
|
|
<ServerGarbageCollection>false</ServerGarbageCollection>
|
|
<!--In workstation or server garbage collection, you can enable concurrent garbage collection,
|
|
which enables threads to run concurrently with a dedicated thread that performs the garbage
|
|
collection for most of the duration of the collection.
|
|
|
|
Concurrent garbage collection enables interactive applications to be more responsive by
|
|
minimizing pauses for a collection. Managed threads can continue to run most of the time while
|
|
the concurrent garbage collection thread is running. This results in shorter pauses while
|
|
a garbage collection is occurring.
|
|
|
|
To improve performance when several processes are running, disable concurrent garbage collection.
|
|
|
|
More details here: https://docs.microsoft.com/en-us/dotnet/standard/garbage-collection/fundamentals#concurrent-garbage-collection-->
|
|
<ConcurrentGarbageCollection>false</ConcurrentGarbageCollection>
|
|
</PropertyGroup>
|
|
</Project> |