Symbol analysis not working against solution

[phmonte]

Symbol analysis not working against solution

[kentcb]

And literally the second thing I tried worked. First I tried using latest Buildalyzer (same behavior), then I tried making my executing project a netcore console app instead of a netfx one. That worked.

[josephwoodward]

I don't suppose you have a repo where I could try replicate this, or any replication steps?

[kentcb]

@josephwoodward hmm, that will be tricky. I'm using the netstandard branch of my open source PCLMock project, but I am running it against proprietary code. Chances are if you do the same thing against your own SDK-style/netstandard solution you'll see the same problem.

Steps:

1. Clone PCLMock and switch to the netstandard branch
2. Open PCLMock in VS2017
3. Set PCLMock.CodeGeneration.Console as the startup project
4. Change the properties of the PCLMock.CodeGeneration.Console per the screenshot below. The working dir should be the directory in which your target code is contained. The contents of Mocks.xml shouldn't actually matter (just make valid XML) until we can move past this problem.
5. Set a breakpoint in Generator.cs line 69 (in GenerateMocksAsync)
6. Run it!

When the breakpoint is hit, you'll see the project has no referenced projects.

Please let me know if this helps. If I have to create a separate repro project to run against, I will find the time to do so.

[kentcb]

OK, forget the above repro instructions - I've recreated this in a very simple project, attached.

Instructions:

1. Unzip
2. Open BuildalyzerRepro.sln
3. Run the app

All it does is load another solution (bundled) and output the project names and their project references. It gets the names right, but not the reference from the ViewModels project to the Utility project.

Digging deeper now - just wanted to post this ahead of my investigations.

BuildalyzerRepro.zip

[daveaglick]

Cool - that's a perfect repro, thanks. I'll take a look as soon as I get a chance.

[daveaglick]

Buildalyzer 1.0.0 was released to NuGet last night. Can you please try it out when you get the chance and let me know the status of this issue?

FYI - the Buildalyzer 1.0.0 API has changed significantly. Revised documentation is forthcoming, but I wanted to get the release out there ASAP. Hopefully you'll be able to figure out the differences, but if not the source code of the tests is a good place to look or wait until better docs are out next week.

[kentcb]

I can no longer repro this with 1.0.0. Thanks!