avivanoff
avivanoff
In MSTest V1 TestContext.TestResultsDirectory is different for every test. For instance: TestMethod1 -> …\Deploy_1 2018-10-17 13_00_29\In\b3ce33a5-5c66-422e-960e-3cc97e6f7f13\MYMACHINE TestMethod2 -> …\Deploy_1 2018-10-17 13_00_29\In\7f4f9ba7-9081-479b-9f49-7d1e020604ff\MYMACHINE After convertsion to MSTest V2: TestMethod1 -> …\Deploy_1 2018-10-17...
I am building quite a few projects, some of them are dependent on other projects. Because it is a mix of managed and native projects, i cannot always use project...
1. Extract the attached archive. 2. Navigate to "TraversalWithPack\build" folder. 3. Run the followin command, build succeeds: `msbuild /flp:v=diag /t:pack build-all.proj` 4. Run the followin command, build fails: `msbuild /m...
We have a solution that consists of 100+ projects, both managed and native. The source code and various package caches are located on the DevDrive. When building the solution, both...
The tool produces incorrect results on the binaries built with Visual Studio 2022. 1. Build [Project1.zip](https://github.com/trailofbits/winchecksec/files/10355780/Project1.zip) in Release|Win32 configuration. 2. Run winchecksec on the resultant binary. At a minimum `SafeSEH`...
signtool.exe has a set of options for producing/signing/ingesting digests. It would be beneficial to have the same support for advanced singing workflows. Moved from https://github.com/vcsjones/AzureSignTool/issues/216.
signtool.exe has a set of options for producing/signing/ingesting digests. It is imperative AzureSignTool has the same support for advanced singing workflows.
Original request: > When building on Windows it would be nice to have the ability to specify version info. When an Azure SDK package is built as a shared binary...
We have the following structure in some of our test projects: ``` [TestClass] public abstract class TestBase { public TestContext TestContext { get; set; } [TestInitialize] public void RunTestSetup() {...