I'm working on a system with FIPS enabled, disabling is not an option. I was able to get a local build to work following tips to add the FIPS enabled=false flag to the MS build config files and the devenv config files on my build server and local workstation for VS2013 & 2015.
However, I'm still receiving the exception message: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms. Exception stack trace: at System.Security.Cryptography.SHA256Managed..ctor() error.
How do I get past this error for TFS Builds?
I did read that there was an issue with SHA256Managed, is there a way to have it use one of the other two methods that are FIPS compliant?
Related
I'm trying to publish my app on the Microsoft Store. When I run the Windows App Certification Kit I receive for each action an error related with Microsoft.Windows.SoftwareLogo.TestBase.
I'm using Visual Studio 2017 Version 15.9.3
Bytecode generation
Error Found: The bytecode generation test detected the following errors:
System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Windows.SoftwareLogo.Tests.Utility.IsPackageWWA(AppXPackage package) at Microsoft.Windows.SoftwareLogo.Tests.BytecodeGenerationCheck.BytecodeGenerationCheck.ExecuteSharedValidation(String manifestFilePath, String packageFullName) at Microsoft.Windows.SoftwareLogo.TestBase.TestBase.ExecuteTest()
Impact if not fixed: As a performance optimization to accelerate JavaScript execution time, JavaScript files ending in the ".js" extension generate bytecode when the app is deployed. This optimization significantly improves start-up and ongoing execution times for JavaScript.
How to fix: You may need consider one or more of these steps to fix the issue:
- Avoid deploying the app by pressing F5 in Visual Studio, create an app package instead
- Ensure that event logging is enabled
- All JavaScript files are syntactically valid; otherwise exclude the respective files from the package
- Please note that you should uninstall all previous versions of the app before deploying
Otherwise exclude the respective files from the package.
I verified in my Visual Studio Installer and the Windows SDK in installed.
Also, I checked the targeting version of the project:
Target version: 1809 (10.0; Build 17763)
Min version: November Update (10.0; Build 10586)
There is not SDK for this build...
I've been unable to get Visual Studio, running on my development machine, to successfully deploy to a Surface Book on my local network. Error message is included below. On the Surface Book I've installed Remote Tools for Visual Studio, and set up Developer Mode. VS on my development machine shows me the SB, and allows me to select if from a list of deployment targets, including it's Authentication type, but deployment fails.
There is a "pair" option on the SB, which I haven't been able to make work & I'm not sure if it's necessary. In addition, I saw a post saying this option (local network) was no longer supported. Is it still supported, and if so, any idea what I'm doing wrong?
Error Message:
Error DEP6957: Failed to connect to device '10.0.0.179' using Universal Authentication. Please verify the correct remote authentication mode is specified in the project debug settings. COMException - Error HRESULT E_FAIL has been returned from a call to a COM component. [0x80004005]
To remote debug a uwp app, we should install the corresponding version Remote Tools for Visual Studio, before we can deploy the app to the remote device, we should configure the Remote Debugger tool. See the Run UWP apps on a remote machine in Visual Studio for details.
For your this issue, it should be you select the Windows authentication mode in your Visual Studio as the follow image, but you don't have access to the credentials of the signed-in user of the target machine. In your VS, you should use the credentials of the signed-in user of the target machine to deploy your app when the VS popup the permission window. See the Authentication modes to learn the differences.
On the other hand, you can also try to use the None authentication mode to remote deploy your app as the following steps.
Firstly, in the Visual Studio Remote Debugger of the target device, select Tools=> Options to configure the options Window as bellow,
Then in your Visual studio, right click your UWP project=> properties=> Debug to cofigure it as None authentication mode.
The answer from Breeze Liu was very helpful, and got me most of the way to the solution. The final step that I was missing was to add my account to the Remote Debugger's permission list. It's found at Remote Debugger>Tools>Permissions. I had to add my account on the target machine to the list of "permitted" debuggers.
I'm trying to use remote debugging to test an application on a Surface Hub. On my local machine, I'm using VS 2017. Both the local Windows 10 machine and the Surface Hub are running Creator's Update (15063). The Surface Hub and the local machine both have "Developer Mode" enabled.
I've set the authentication to Universal and put the Hub's IP address in as the remote machine name. When I press the Debug button, the Hub puts up a dialog with this:
C:\ProgramData\DeveloperTools\VSRemoteTools\x64\coreclr\CoreCLR.
dll is either not designed to run on Windows or it contains an error. Try
installing the program again using the original installation media or
contact your system adminsitrator or the software vendor for support.
Error status 0xc0000428.
And on my local machine I get this:
DEP0100: Please ensure that target device has
developer mode enabled. Could not obtain a
developer license on 10.10.1.17 due to error
80004005.
Googling around I found that 0xc0000428 is usually a digital signature issue.
I'm aware that I can package up the app and install test certificates and stuff. But I'm hoping there's a way to get VS 2017's debugger to work the way the documentation says it is supposed to.
This is an known bug that got introduced in Visual Studio 15.3 update (CoreCLR did not get signed with certificates required by Surface Hub). It is also tracked here: https://developercommunity.visualstudio.com/content/problem/107166/visual-studio-153-isnt-able-to-remote-deploy-uwp-a.html
It should be fixed in next Visual Studio update.
We are working on Xcode Project connected to our local TFS 2013 (Update 3) Server via TFS Provided Git Repository.
When we use older version of Xcode, we are successfully able to check-in the files and perform all other Git operations. We are also able to perform all Git Operations via command line Git.
The trouble is when we use latest version of Xcode - Version 7.1 (7B91b).
On entering valid credentials, we are getting error saying
Authentication failed because the user name or password was incorrect.
The same credentials / configuration work on older version of Xcode and Git Command Line Options.
To add more to the surprises, we are able to connect to github.com successfully.
We are able to reproduce issue on other systems too. Please provide us the best way to resolve this error.
For us it turned out to be because Xcode 7 does not support Windows Authentication. The solution described here solved it for us:
"This happens because XCode 7 doesn't support Windows Authentication.
I don't know why. It seems to be a common problem amongst users
because there are many posts about it in google.
To make it all work you should enable Basic Authentication in your IIS
TFS website on "tfs" virtual folder.
Be careful though because basic authentication sends your credentials
over network as plain text. You definitely must use SSL in this case."
(source)
I'm using TFS 2010 SP1 Lab Management and a variation on the LapDeployTemplate to execute build workflows and unit tests on a Hyper-V VM, managed via SCVMM (per the ALM Rangers Lab Management Guidance doco on codeplex). After configuring all of this, I've created a Test Plan containing test cases that map to automated unit/integration tests that use Moles. I've used tcm.exe import these test cases and get them into the Microsoft Test Manager.
I'm getting the following error when I try to execute test cases remotely on my VM using the LabDeploy workflow:
"The host type 'Moles' cannot be loaded for the following reason: The key 'Moles' cannot be found."
Normally, I've seen this error on machines where Moles isn't installed, but here's my configuration on the VM currently:
Windows 2008 Server R2
Moles 0.94.51023.0 x64
VS2010 Test Agent\Controller x64
VS2010 Build Agent x64
VS2010 Lab Agent x64
Test Settings file is set to use the Default Host type and to have tests execute in x64 on an x64 machine. This is identical to the development boxes we use and they all execute tests fine.
I've already tried an uninstall/reinstall of Moles as well as the test agent on the machine to no avail. Any ideas? Has anyone else ran into this?
Moving my comment to an answer so that I can mark it as answered - I've opened the Moles MSI in ORCA and it turns out that it has Registry conditions that prevent the Moles host agent from installing on a box without a full VS 2010 devenv install. Thus, I had to spoof that registry key to get Moles to install all bits. Once this was done, I got the agent to execute, but fails with errors dealing with environment config, etc. After looking through all of this and the lack of doco online for this scenario, I'm fairly certain it's not been tested nor is supported. I think that the Lab Agent for 2010 + Moles only configuration just doesn't work