Setup Problems

Can't enable NCrunch in VS2019 16.3.0 Preview 2

Started by kimbirkelund on 4,539 views

Hi

I realize that previews of VS aren't supported, but in case there's already a workaround or something I'm just posting since it's quite annoying that NCrunch isn't working :)

After upgrading this is how the NCrunch menu looks:

External image

The test window looks like this:

External image
Hi!

Thanks for posting this. We noticed this yesterday, we've got a fix committed for it but no release out yet. I'll have a look to trigger a dev release for this.
That awesome. Looking for to the fix :)

Kudos on the fast reply.
Hi All,

Below are links to a release that supports the new VS preview. This release also has a change to the grid protocol, so if you use distributed processing you need to upgrade the grid nodes as well.

NCrunch_Console_3.31.0.1.msi
NCrunch_Console_3.31.0.1.zip
NCrunch_GridNodeServer_3.31.0.1.msi
NCrunch_GridNodeServer_3.31.0.1.zip
NCrunch_LicenseServer_3.31.0.1.zip
NCrunch_VS2008_3.31.0.1.msi
NCrunch_VS2010_3.31.0.1.msi
NCrunch_VS2010_3.31.0.1.zip
NCrunch_VS2012_3.31.0.1.msi
NCrunch_VS2012_3.31.0.1.zip
NCrunch_VS2013_3.31.0.1.msi
NCrunch_VS2013_3.31.0.1.zip
NCrunch_VS2015_3.31.0.1.msi
NCrunch_VS2015_3.31.0.1.msi.7z
NCrunch_VS2015_3.31.0.1.zip
NCrunch_VS2017_3.31.0.1.msi
NCrunch_VS2017_3.31.0.1.msi.7z
NCrunch_VS2017_3.31.0.1.zip
NCrunch_VS2019_3.31.0.1.msi
NCrunch_VS2019_3.31.0.1.msi.7z
NCrunch_VS2019_3.31.0.1.zip

-----------------------------------------------------------------
Release notes for 3.31.0.1 since version v3.30.0.1
-----------------------------------------------------------------

Fixed a problem with the NCrunch Processing Queue window where part of the window was rendered outside of the form.

Fixed storing the position of the splitter in the NCrunch Processing Queue window.

Fixed a problem with the integration of Visual Studio 2019 16.3.0 Preview 2

Adjusted the handling of NCrunch attribute related test metadata to improve reliability and performance.

Restructured the identification routine used to find test entry points to improve stability and performance.

Retired MSpec's DynamicAnalysis framework utilisation type, as this setting gave no apparent benefits and couldn't be supported with the new entry point identification routine. MSpec is now enabled/disabled using a simple true/false configuration setting.
Thanks Michael, that got it working again for us.
This post has been deleted.

Post a reply

Log in to reply.