forked from TrakHound/MTConnect.NET
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathMTConnect.NET-AgentProcessor-Python.csproj
More file actions
68 lines (57 loc) · 2.94 KB
/
Copy pathMTConnect.NET-AgentProcessor-Python.csproj
File metadata and controls
68 lines (57 loc) · 2.94 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup Condition="'$(Configuration)'=='Debug'">
<TargetFrameworks>net8.0</TargetFrameworks>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)'=='Release'">
<TargetFrameworks>net461;net462;net47;net471;net472;net48;netstandard2.0;net6.0;net7.0;net8.0;net9.0</TargetFrameworks>
<DebugSymbols>false</DebugSymbols>
<DebugType>None</DebugType>
<Optimize>true</Optimize>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)'=='Package'">
<TargetFrameworks>net461;net462;net47;net471;net472;net48;netstandard2.0;net6.0;net7.0;net8.0;net9.0</TargetFrameworks>
<Optimize>true</Optimize>
</PropertyGroup>
<PropertyGroup>
<RootNamespace>MTConnect</RootNamespace>
<Configurations>Debug;Release;Package</Configurations>
<Description>MTConnect.NET-AgentProcessor-Python implements using Python scripts for Agent Processing for use with the MTConnectAgentApplication class in the MTConnect.NET-Applications-Agent library. Supports MTConnect versions up to 2.7. Supports .NET Framework 4.6.1 up to .NET 9</Description>
<PackageReadmeFile>README-Nuget.md</PackageReadmeFile>
<!-- Optional: Publish the repository URL in the built .nupkg (in the NuSpec <Repository> element) -->
<PublishRepositoryUrl>true</PublishRepositoryUrl>
<!-- Optional: Embed source files that are not tracked by the source control manager in the PDB -->
<EmbedUntrackedSources>true</EmbedUntrackedSources>
<!-- Optional: Build symbol package (.snupkg) to distribute the PDB containing Source Link -->
<IncludeSymbols>true</IncludeSymbols>
<SymbolPackageFormat>snupkg</SymbolPackageFormat>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)'=='Package'">
<ContinuousIntegrationBuild>true</ContinuousIntegrationBuild>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="IronPython" Version="3.4.2">
<PrivateAssets>all</PrivateAssets>
</PackageReference>
<PackageReference Include="NLog" Version="5.2.7" />
<!--
IronPython's DynamicLanguageRuntime transitive (Microsoft.Scripting.dll)
carries a strong-named reference to System.Configuration.ConfigurationManager
8.0.0.0 even though its net8.0 nuspec drops the dependency (it was only
declared on the netstandard2.0 group). Without an explicit reference here
the assembly is never copied into bin/Debug/net8.0/, and `docfx metadata`
emits `InvalidAssemblyReference` while walking the Python processor DLL's
reference graph. Pinning it on the project that uses IronPython lands
the assembly in the output directory so the docs build stays warning-free.
-->
<PackageReference Include="System.Configuration.ConfigurationManager" Version="8.0.0" />
</ItemGroup>
<ItemGroup>
<ProjectReference Include="..\..\..\libraries\MTConnect.NET-Common\MTConnect.NET-Common.csproj" />
</ItemGroup>
<ItemGroup>
<None Include="README-Nuget.md">
<Pack>True</Pack>
<PackagePath>\</PackagePath>
</None>
</ItemGroup>
</Project>