Visual Studio doesn't discover my unit tests!

I added a unit test class to a project today, and Visual Studio couldn't find my new unit tests. Quick hack: modify your output window to "Show output from:" "Tests." This may help you find the reason why. In my case, it told me pretty directly what the issue was:

UTA001: TestClass attribute defined on non-public class MyTests

My test class wasn't public, which it appears is a requirement for discovery.

Updating include directories after updating Vivado

So, after updating Vivado, I ended up with a number of warnings during compile in the SDK IDE, referring to an old, now missing path. As the paths didn't appear to be modifiable within the project settings, I searched for a way to update them.

That brought me to this post, which has approximately the right stuff:

1. Close the SDK.
2. Delete the .metadata folder in your xyz.sdk folder.
3. Restart the SDK.
4. Import the existing projects. You'll see that only the design folder was automatically imported.

No matching key exchange method found

Ran into this again while trying to ssh into the old battleship:

no matching key exchange method found. Their offer: diffie-hellman-group1-sha1

A solution is to specify the key exchange algorithm on the command line:

ssh -o KexAlgorithms=+diffie-hellman-group1-sha1 root@169.254.8.70

More information can be found on OpenSSH's Legacy Options page.

Vivado does not launch with Windows 10 Fall Creators Update

There's a work-around available from Xilinx AR 69908. Windows 10 Fall Creators Update is not officially supported for Vivado 17.3 or 17.3.1.

Downloading an ISO for Visual Studio 2017

Note to Self

There isn't an ISO image download for VS 2017, you download the web installer, then pass it the commands to construct a disk layout for you. Here's the location of instructions to do so:

    Create an offline installer for Visual Studio 2017

That page includes instructions for:

• Creating an offline installation layout.
• Installing from an offline installation layout (may not be necessary, see the comments on this instruction).
• Customizing the offline installer.
• Updating the offline installer.
• Troubleshooting.

And here's the command line I use:

    vs_Community.exe --layout c:\vs2017-community-en-US-offline --lang en-US