The FrameworkReference 'Microsoft.WindowsDesktop.App.WPF' was not recognized

.net 4.8 builds fine with dotnet build.
No errors as I can see from launching the testhost executables.

Magbr wrote:.net 4.8 builds fine with dotnet build.
No errors as I can see from launching the testhost executables.

Can you confirm that you are able to run tests under other versions of .NET?

Are you able to produce this issue in a small sample project that is disconnected from your work?

I believe this is somehow related to the magnitude of the solution(60 projects). It doesn't happen in the small console sample.

Tests run fine in other assemblies.

Would it be a problem that the .net 4.8 assembly references assemblies with other .net framework versions?

Magbr wrote:
Would it be a problem that the .net 4.8 assembly references assemblies with other .net framework versions?

Unless you have the preload assembly references setting enabled, this is unlikely to be the cause of the problem.

The process is self terminating before NCrunch can even properly initialise it, which means this is very structural. It could be something in your environment.

Does switching the version of .NET used by the test project in question make any difference?

Remco wrote:

Magbr wrote:
Would it be a problem that the .net 4.8 assembly references assemblies with other .net framework versions?

Unless you have the preload assembly references setting enabled, this is unlikely to be the cause of the problem.

Does switching the version of .NET used by the test project in question make any difference?

It's not enabled.

Ooo interesting, it turns out the 4.4.0.8 update fixed builds of the 4.8 projects. However the ones that aren't building now are actually netcoreapp2.2 projects...

Also interestingly if I change those to core 3.1 they build...!




Side note: whenever I make a change, the gui uncollapses some tests every time. Even though nothing in that assembly is pinned. Quite annoying

Are these problems inconsistent or do they happen for the same projects every time?

The same projects are uncollapsed every time

Magbr wrote:The same projects are uncollapsed every time

How about the build issues?

Are you able to reproduce the netcoreapp2.2 build issues in a sample project?

Magbr wrote:The same projects are uncollapsed every time

Hi, could we get back to this? I believe I got the other issues sorted.

However this one is so annoying. I've noticed an additional thing. If I change the test code everything is fine. But if I change some param in an InlineData attribute that's when it happens. Have to scroll and close a lot of things down usually.

Thanks!

Magbr wrote:
However this one is so annoying. I've noticed an additional thing. If I change the test code everything is fine. But if I change some param in an InlineData attribute that's when it happens. Have to scroll and close a lot of things down usually.
Thanks!

This one is by design. The Tests Window is designed to expand to show newly added tests when they are detected by the discovery system. When you change an InlineData attribute, you physically create a new test in the discovery result. If you want to keep these tests hidden, simply unselect the 'Show unexecuted tests' option on the Tests Window toolbar. The tests should automatically hide again once they have been executed by NCrunch (assuming they pass and the 'Show passing tests' filter option is disabled).

Note that the same logic applies to tests that show up with a new failure result. Similarly, if you want to hide these tests, there is a toolbar option for them.

Remco wrote:

Magbr wrote:
However this one is so annoying. I've noticed an additional thing. If I change the test code everything is fine. But if I change some param in an InlineData attribute that's when it happens. Have to scroll and close a lot of things down usually.
Thanks!

This one is by design. The Tests Window is designed to expand to show newly added tests when they are detected by the discovery system. When you change an InlineData attribute, you physically create a new test in the discovery result. If you want to keep these tests hidden, simply unselect the 'Show unexecuted tests' option on the Tests Window toolbar. The tests should automatically hide again once they have been executed by NCrunch (assuming they pass and the 'Show passing tests' filter option is disabled).

Note that the same logic applies to tests that show up with a new failure result. Similarly, if you want to hide these tests, there is a toolbar option for them.

it's fine that it expands to show new tests, but it also expands projects where there are no new tests. Which is quite tedious to close every time we edit an InlineAttribute. Which is quite often during parameterized integration testing..

Magbr wrote:
it's fine that it expands to show new tests, but it also expands projects where there are no new tests. Which is quite tedious to close every time we edit an InlineAttribute. Which is quite often during parameterized integration testing..

Are you making use of any random data in your tests? The Tests Window should only be expanding tree nodes when the data underneath those node changes. If you have tests with inconsistent names (i.e. due to random parameters), this might cause an issue.

Remco wrote:

Magbr wrote:
it's fine that it expands to show new tests, but it also expands projects where there are no new tests. Which is quite tedious to close every time we edit an InlineAttribute. Which is quite often during parameterized integration testing..

Are you making use of any random data in your tests? The Tests Window should only be expanding tree nodes when the data underneath those node changes. If you have tests with inconsistent names (i.e. due to random parameters), this might cause an issue.

Oh yes, that makes sense. Some tests use auto generated data. Is it possible to disable this behavior?

Magbr wrote:.net 4.8 builds fine with dotnet build.
No errors as I can see from launching the testhost executables.

I had similar issues, have a look here, it may helps you:

https://forum.ncrunch.net/yaf_postst3045_Visual-Studio-16-8-RTM---NCrunch-Error.aspx

Br

Magbr wrote:
Oh yes, that makes sense. Some tests use auto generated data. Is it possible to disable this behavior?

You can ignore the tests using the Ignored Tests option. However, it isn't possible for NCrunch to control the manner in which your tests are generated or how they behave at runtime - that's up to your test code and the test framework.

Remco wrote:

Magbr wrote:
Oh yes, that makes sense. Some tests use auto generated data. Is it possible to disable this behavior?

You can ignore the tests using the Ignored Tests option. However, it isn't possible for NCrunch to control the manner in which your tests are generated or how they behave at runtime - that's up to your test code and the test framework.

I was thinking like disable expand on discovery of new tests.

Actually the two tests that are expanded, doesn't have anything generated in the test name, parameterization etc. they're just [Fact]'s.

E.g.
[Fact]
public async Task SendReceiptOnEmail()

Fyi this is the first test in that test assembly.