Visual studio 2015 没有使用msbuild artifactory插件发布到artifactory的内容

我一直在尝试在我的项目中使用msbuild Artifactory插件。经过一段时间与依赖项的斗争，我成功地使Artifactory项目工作，但尽管我没有收到任何错误，并且构建成功，但没有任何内容发布到Artifactory

这是我的Artifactory.build文件：

管理
XXXXXX
$（已解决\u已启用）
http://192.168.1.25:8081/artifactory
libs发布
$（已部署\u已启用）
http://192.168.1.25:8081/artifactory
libs本地发布
obj\（.+）\（.+）.dll
HystrixExample/$1/$2.dll
假的
假的
真的
假的
假的
$（BD_应用程序_名称）
$（BD_应用程序_版本）
假的
假的
假的
$（构建名称）
$（构建ID）
300
真的
127.0.0.1
8888

我只想发布我的dll，因为我没有ArtifactoryPro，所以我不能发布NUGET，所以我只取消了部署的dll部分的注释

我使用的是visual studio 2015，带有nuget package manager 3.4.4，因此自nuget 2.7以来我不需要.nuget文件夹，但我在项目中创建了一个.nuget文件夹，甚至向其中添加了nuget.exe文件，但这似乎没有帮助。我无法让VisualStudio自动添加它们

有什么我遗漏的吗

---

感谢

问题是我需要将标记更改为true并添加标记，但我发现Artifactory Jenkins插件有一个通用选项来上载这些工件，因此我真的不需要使用de MSBuild Artifactory插件

---

谢谢

如果可能，您可以从文档中获得一些帮助：您好，这是我一直在使用的指南，我发现了需要将标记更改为true并添加标记的问题，但现在我遇到了403错误：(

<!--
  MSBuild Artifactory Plugin
  For more details, please go to the plugin Wiki site - http://www.jfrog.com/confluence/display/RTF/MSBuild+Artifactory+Plugin
-->

<!--Credentials for Artifactory-->
<ArtifactoryUserName>admin</ArtifactoryUserName>
<ArtifactoryPassword>XXXXXX</ArtifactoryPassword>


<!-- Resolution-->

<!--Enable Artifactory plugin to override Nuget "Package Restore" -->
<ResolveEnabled>$(RESOLVED_ENABLED)</ResolveEnabled>
<!--Root URL of the Artifactory server. e.g., http://domain:port/artifactory-->
<ResolveArtifactoryUrl>http://192.168.1.25:8081/artifactory</ResolveArtifactoryUrl>
<!--NuGet repository key to resolve from. Usually remote or virtual repository-->
<ResolveRepository>libs-release</ResolveRepository>
<!--
  To override the user credentials for the resolution process, uncomment the two fields below.
-->
<!--<ResolveArtifactoryUserName>$(ARTIFACTORY_RESOLVE_USER)</ResolveArtifactoryUserName>-->
<!--<ResolveArtifactoryPassword>$(ARTIFACTORY_RESOLVE_PASSWORD)</ResolveArtifactoryPassword>-->


<!-- Deployment-->

<!--Enable Artifactory plugin to publish artifacts -->
<DeployEnabled>$(DEPLOYED_ENABLED)</DeployEnabled>
<!--Root URL of the Artifactory server. e.g., http://domain:port/artifactory-->
<DeployArtifactoryUrl>http://192.168.1.25:8081/artifactory</DeployArtifactoryUrl>

<!--Enable Artifactory plugin to publish Build Info -->
<BuildInfoEnabled>libs-release-local</BuildInfoEnabled>


<!-- 
  Under <Deployments> you can add multiple <Deploy> elements which define the sets of files to deploy to Artifactory. Each <Deploy> element contains the following:

  <InputPattern>
      Here you can supply path to files, that the plugin will collect. The path is relative to the project and to any other projects referenced to him in the solution.
      The usage of Regular Expressions, is not mandatory.
      Regular Expressions must be in format of a Capturing Group (inside Brackets).
      More information about Capturing Group, can be found here: http://www.regular-expressions.info/brackets.html
  <OutputPattern>
      A path inside the Artifactory deployment repository.
      If you used Regular Expressions in the <InputPattern>,  you may use $# symbols in the <OutputPattern> to refer to the Capturing Groups you defined in the <InputPattern>.
      This mechanism enables you to dynamically construct the target path.
  <Properties>
      Artifactory properties that will be attached to every file that the <InputPattren> finds.
      Each Property is defined in a separate <Property> tag.
 -->   

<Deployments>
  <!--Examples-->

  <!--All Nuget files under the bin folder deployed to the root of the deploy repository-->

  <!--<Deploy>
    <InputPattern>bin\(.+).nupkg</InputPattern>
    $1 refers to (.+) capturing group
    <OutputPattern>$1.nupkg</OutputPattern>
  </Deploy>-->


  <!--All DLL files one or more level under the obj folder deployed with custom properties under the 'myproject' folder of the deploy repository.-->

  <Deploy>
    <InputPattern>obj\(.+)\(.+).dll</InputPattern>
    <OutputPattern>HystrixExample/$1/$2.dll</OutputPattern>
    <!--<Properties>
      <Property key="qa" val="ready" />
      <Property key="myprop" val="myval" />
    </Properties>-->
  </Deploy>

</Deployments>

<!-- Environment Variables-->   
<!--
  Environment variables that will be included as part of the published build info.
  Patterns may contain the * and the ? wildcards. Include patterns are applied before any exclude patterns.
 -->
<EnvironmentVariables>
  <Enabled>false</Enabled>
  <IncludePatterns>
    <!--<Pattern key=""/>-->
  </IncludePatterns>
  <ExcludePatterns>
    <Pattern key="*password*"/>
    <Pattern key="*key*"/>
    <Pattern key="*secret*"/>
  </ExcludePatterns>
</EnvironmentVariables>

<!-- License Control-->
<!--
  Enable if you want a license scan to run automatically after the build is complete.
  Only available with Artifactory Pro!
-->
<LicenseControl>
  <Enabled>false</Enabled>
  <LicenseViolationRecipients>
    <Recipient email="ana.franco@ceiba.com.co"/>
  </LicenseViolationRecipients>
  <!--If Nuget package license is not identified by Artifactory, run license discovery inside the package. [RESOURCE INTENSIVE]-->
  <AutomaticLicenseDiscovery>true</AutomaticLicenseDiscovery>
  <IncludePublishedArtifacts>false</IncludePublishedArtifacts>
  <ScopesForLicenseAnalysis>
    <!--<Scope value="Debug"/>-->
  </ScopesForLicenseAnalysis>
</LicenseControl>

<BlackDuckComplianceCheck>
  <Enabled>false</Enabled>
  <CodeCenterApplicationName>$(BD_APPLICATION_NAME)</CodeCenterApplicationName>
  <CodeCenterApplicationVersion>$(BD_APPLICATION_VERSION)</CodeCenterApplicationVersion>
  <ComplianceReportRecipients>
    <!--<Recipient email="address@jfrog.com"/>-->
  </ComplianceReportRecipients>
  <ScopesForLicenseAnalysis>
    <!--<Scope value="Debug"/>-->
  </ScopesForLicenseAnalysis>
  <IncludePublishedArtifacts>false</IncludePublishedArtifacts>
  <AutoCreateMissingComponent>false</AutoCreateMissingComponent>
  <AutoDiscardStaleComponent>false</AutoDiscardStaleComponent>   
</BlackDuckComplianceCheck>

<!--
    If the build is not running under TFS, uncomment the two elements below. 
    The build name and number can be passed as build/environment variables.
-->
<BuildName>$(BUILD_NAME)</BuildName>
<BuildNumber>$(BUILD_ID)</BuildNumber>


<!--Network Configuration-->

<!--Timeout(seconds) for the plugin deployment client-->
<ConnectionTimeout>300</ConnectionTimeout>

<ProxySettings>
  <Bypass>true</Bypass>
  <Host>127.0.0.1</Host>
  <Port>8888</Port>
  <UserName></UserName>
  <Password></Password>
</ProxySettings>

<!--TFS Integration-->

<!--In order to get a full http url address to the TFS build page through the Artifactory Build info , the plugin needs the Team Project name-->
<!--<TEAM_PROJECT>$(TEAM_PROJECT_NAME)</TEAM_PROJECT>-->