小编Rob*_*ert的帖子

在尝试验证令牌时,我得到以下异常的原因是什么？

TokenValidationParameters validationParameters = new TokenValidationParameters();

validationParameters.ValidIssuers = new List<string>() { "http://www.company.com" };

validationParameters.IssuerSigningToken = new RsaSecurityToken(
  (System.Security.Cryptography.RSACryptoServiceProvider) Certificate.Get().PublicKey.Key);

SecurityToken securityToken = null;

var claimsPrincipal = 
    (FederatedAuthentication
      .FederationConfiguration
      .IdentityConfiguration
      .SecurityTokenHandlers
      .First() as JwtSecurityTokenHandler)
      .ValidateToken(tokenString, validationParameters, out securityToken);

错误:

IDX10500: Signature validation failed. Unable to resolve SecurityKeyIdentifier: 
          'SecurityKeyIdentifier
    (
      IsReadOnly = False,
      Count = 2,
      Clause[0] = X509ThumbprintKeyIdentifierClause(
                    Hash = 0x6B7ACC520305BFDB4F7252DAEB2177CC091FAAE1),
    Clause[1] = System.IdentityModel.Tokens.NamedKeySecurityKeyIdentifierClause
    )
', 
token: '{"typ":"JWT","alg":"RS256","

在Visual Studio 2012和TFS中,如何在未将"删除csproj文件"添加到挂起的更改列表的情况下从解决方案中删除项目.我只想删除此解决方案中的引用,但该项目应该仍然存在,因为它在其他解决方案中使用.如果我只是从解决方案中删除它然后提交更改,那么它将删除csproj文件!

在没有TFS删除csproj文件的情况下从解决方案中删除项目的正确方法是什么？

刚刚安装了Visual Studio 2017和wix扩展,在尝试构建使用Wix的解决方案时,我收到以下错误:

Error       The WiX Toolset v3.11 (or newer) build tools must be installed to build this project. Could not find wix.targets at 'C:\Program Files (x86)\MSBuild\Microsoft\WiX\v3.x\'. To download WiX Toolset v3.11 (or newer), see http://wixtoolset.org/releases/ Installer   C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\WiX\v3.x\Wix.targets 10  

在文件夹"C:\ Program Files(x86)\ MSBuild\Microsoft\WiX\v3.x \"中我有以下文件

2017-11-29  15:12    <DIR>          .
2017-11-29  15:12    <DIR>          ..
2017-05-01  07:34           293 705 difxapp_x64.wixlib
2017-05-01  07:34           203 950 difxapp_x86.wixlib
2017-02-27  23:52             3 369 LICENSE.TXT
2017-02-27  23:52             4 233 lux.targets
2017-03-28  02:20             9 067 …

将 VS2013 升级到 VS2017 后，我们有很多（3000+）个错误，因为缺少程序集引用。但是它们都是错误的，引用仍然存在，并且在我们构建项目并运行它时它可以工作。

所有这些虚假错误的问题是当我们有一个实际错误时，很难检测到它，因为项目中到处都是红色错误。

从项目中删除引用并重新添加它，直到 VS 重新启动。

在输出控制台中，我们只看到“真实”错误。

我们试图清理和重建没有任何区别。

我试图按照本指南自定义tfs中的构建过程:

http://msdn.microsoft.com/en-us/library/dd647551.aspx

但在下载.xaml文件并尝试在Visul studio 2013中打开它后,我收到一个错误:

System.Xaml.XamlException: 'The type ‘InArgument(mtbco:BuildParameter[])’ of property ‘AutomatedTests’ could not be resolved.' Line number '5' and line position '39'.
at System.Activities.XamlIntegration.DynamicActivityXamlReader.BufferedPropertyList.ActivityPropertyHolder..ctor(DynamicActivityXamlReader parent, XamlReader reader)
at System.Activities.XamlIntegration.DynamicActivityXamlReader.BufferedPropertyList.BufferDefinitions(DynamicActivityXamlReader parent)
at System.Activities.XamlIntegration.DynamicActivityXamlReader.ProcessCurrentNode()
at System.Activities.XamlIntegration.DynamicActivityXamlReader.Read()
at Microsoft.Activities.Presentation.Xaml.ActivityTemplateFactoryBuilderReader.Read()
at Microsoft.Activities.Presentation.Xaml.ViewStateXamlHelper.StripViewStateElement(XamlReader inputReader, Dictionary`2& viewStateInfo, Dictionary`2& viewStateSourceLocationMap)
at Microsoft.Activities.Presentation.Xaml.ViewStateXamlHelper.ConvertViewStateToAttachedProperties(XamlReader inputReader, ViewStateIdManager idManager, Dictionary`2& viewStateSourceLocationMap)
at Microsoft.Activities.Presentation.Xaml.WorkflowDesignerXamlHelper.DeserializeString(String text, DeserializationMode mode, IList`1& loadErrors, Dictionary`2& sourceLocations)
at Microsoft.Activities.Presentation.Xaml.WorkflowDesignerXamlHelper.DeserializeString(String text, IList`1& loadErrors, Dictionary`2& sourceLocations)
at System.Activities.Presentation.WorkflowDesigner.Load()

这是.xaml文件的开头:

<Activity x:Class="TfsBuild.Process" xmlns="http://schemas.microsoft.com/netfx/2009/xaml/activities" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:mt="clr-namespace:Microsoft.TeamFoundation;assembly=Microsoft.TeamFoundation.Common" xmlns:mtbc="clr-namespace:Microsoft.TeamFoundation.Build.Client;assembly=Microsoft.TeamFoundation.Build.Client" xmlns:mtbco="clr-namespace:Microsoft.TeamFoundation.Build.Common;assembly=Microsoft.TeamFoundation.Build.Common" xmlns:mtbw="clr-namespace:Microsoft.TeamFoundation.Build.Workflow;assembly=Microsoft.TeamFoundation.Build.Workflow" xmlns:mtbwa="clr-namespace:Microsoft.TeamFoundation.Build.Workflow.Activities;assembly=Microsoft.TeamFoundation.Build.Workflow" xmlns:mtba="clr-namespace:Microsoft.TeamFoundation.Build.Activities;assembly=Microsoft.TeamFoundation.Build.Activities" …