Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test With > NUnit not working in 4.0 Beta 2 #71

Closed
jcansdale opened this issue Nov 8, 2016 · 10 comments
Closed

Test With > NUnit not working in 4.0 Beta 2 #71

jcansdale opened this issue Nov 8, 2016 · 10 comments
Assignees
Labels
Milestone

Comments

@jcansdale
Copy link
Owner

jcansdale commented Nov 8, 2016

NOTE: Restore option to test using the old NUnit 2.5.10 GUI from project context menu.

After upgrade to latest beta 2 version, in VS2015 if I right click a project and choose Test With - > Nunit, the nunit console GUI does not open, and I have no error.

It worked like a charm before the upgrade, where should I look to troubleshoot this problem?

Thanks a lot in advance.

@jcansdale jcansdale added the bug label Nov 8, 2016
@jcansdale jcansdale self-assigned this Nov 8, 2016
@jcansdale
Copy link
Owner Author

Almost certainly caused by this:

[16504] initing command: System.NullReferenceException: Object reference not set to an instance of an object. 
[16504]    at TestDriven.Services.Commands.GuiApplicationTarget..ctor(String applicationName, Utilities utilities) 
[16504]    at TestDriven.Services.Commands.GuiApplicationHandler.Create(Object parent, Object configContext, XmlNode section) 
[16504]    at MutantDesign.ManagedAddIns.Services.CommandsService.CommandComponent..ctor(DTE dte, AddIn addIn, BindingsStore bindingStore, Command commandSection) 
[16504]    at MutantDesign.ManagedAddIns.Services.CommandsService.AddNamedCommand(Command commandSection) 
[16504]    at MutantDesign.ManagedAddIns.Services.CommandsService.initNamedCommands(CommandsSection section) 

@jcansdale
Copy link
Owner Author

Could you give this build a try:
TestDriven.NET-4.0.3438_Extraterrestrial_Beta2.zip

@jcansdale jcansdale added this to the v4.0-RTM milestone Nov 9, 2016
@alkampfergit
Copy link

Actually I have some problem uninstalling the actual version, I've launced the new installer, it tried to uninstall the actual beta2 version then it failed.

image

Then I decided to uninstall manually

image

I got an error from VS2010 (I only have shell installed)
image

Finally this error

image

I'll try after a reboot.

@jcansdale
Copy link
Owner Author

😢

What happens if you just run the setup.exe?

@alkampfergit
Copy link

The very same error, with the old installer and the new installer, it seems that something got wrong in my installation :/

@jcansdale
Copy link
Owner Author

jcansdale commented Nov 11, 2016

I wonder if you might have a borked install of .NET v1.1? Could you try renaming the following directory and having another go:
\Windows\Microsoft.NET\Framework\v1.1.4322
(this would force the TD.Net installer to execute using a different version of .NET)

It's a long shot, but worth a try...

@alkampfergit
Copy link

alkampfergit commented Nov 11, 2016

Pretty radical solution, but when I try to rename that folder the rename failed because the folder is in use.

This error seems to be typical of .msi installer.

@alkampfergit
Copy link

  1. Fixed the uninstall problem with this microsoft fix (https://support.microsoft.com/en-ca/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed)
  2. installed this extraterrestial version
  3. Problem is solved :) thanks.

@jcansdale
Copy link
Owner Author

Pretty radical solution, but when I try to rename that folder the rename failed because the folder is in use.

It happens from time to time that .NET 1.1 is borked and people only notice when TestDriven.Net's installer doesn't work. I'm surprised you have something installed that's actively using .NET 1.1. 😄

Fixed the uninstall problem with this microsoft fix (https://support.microsoft.com/en-ca/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed)

Thank you very much for the link, I'd never come across this before. In the past I've suggested (the no longer supported) Msizap.exe when someone's installer registry was corrupted. It's good to know there is an alternative and supported option!

Good to hear the problem is solved.

@alkampfergit
Copy link

Never heard of that link before, but the problem is somewhat due to some broken registry link for .msi package. That tool listed all application that are found to be installed in the registry, I just selected testdriven.net and it told me that there were a couple of error that were fixed, application uninstalled correctly and I was able to install again TestDriven.Net ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants