Support for VS2015

51 views
Skip to first unread message

Michael Ketting

unread,
Feb 20, 2015, 4:32:25 AM2/20/15
to testdri...@googlegroups.com
Hello Jamie!

I'm an avid user of TDD.NET and am wondering if you have any news/updates on VS2015 compatiblity for TDD.NET.

Best regards, Michael

Jamie Cansdale

unread,
Feb 20, 2015, 5:44:25 AM2/20/15
to TestDriven.NET Users
Hi Michael,

> I'm an avid user of TDD.NET and am wondering if you have any news/updates on
> VS2015 compatiblity for TDD.NET.
>
Yes, the latest Beta (3.8.2873) works with VS 2015. :)

I should really update the website!

Kind regards,

Jamie.

--
http://www.testdriven.net
http://twitter.com/jcansdale
http://weblogs.asp.net/nunitaddin


On 20 February 2015 at 09:32, Michael Ketting
> --
> You received this message because you are subscribed to the Google Groups
> "TestDriven.NET Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to testdrivenuse...@googlegroups.com.
> To post to this group, send email to testdri...@googlegroups.com.
> Visit this group at http://groups.google.com/group/testdrivenusers.
> For more options, visit https://groups.google.com/d/optout.

Michael Ketting

unread,
Feb 20, 2015, 5:56:30 AM2/20/15
to testdri...@googlegroups.com
Hi Jamie!

Great, thanks! For some reason, I missed the Beta link :o

Tests are now executing in VS2015! I noticed that the XUnit-based tests for the EntityFramework 7 show the progress bar at 100% green from the get go. I'm assuming that's a bug, although not sure if it's XUnit related or VS2015 related.

Best regards, Michael

Jamie Cansdale

unread,
Feb 20, 2015, 6:16:03 AM2/20/15
to TestDriven.NET Users
> I noticed that the XUnit-based tests for the EntityFramework 7 show the progress
> bar at 100% green from the get go. I'm assuming that's a bug, although not sure
> if it's XUnit related or VS2015 related.
>
Alas this is xUnit related. The xUnit test runner knows how many test
classes there are but not how many tests (before execution completes).
TestDriven.Net's progress bar needs to know how many tests there are
for the progress bar to work.

Unfortunately fixing this in an elegant way would involve disruptive
changes to both TestDriven.Net and xUnit. This is aggravated by the
fact they're distributed independently and there is a large deployed
base of both.

It might be possible to come up with some heuristic so the xUnit test
runner can guess the total number of tests remaining based on the
number of tests/test classes executed and the test classes remaining.
I think this is kind of how the windows installer progress bar works
(which is why it jumps around a lot).

Regards,
On 20 February 2015 at 10:56, Michael Ketting

Michael Ketting

unread,
Feb 20, 2015, 7:24:38 AM2/20/15
to testdri...@googlegroups.com
Good to know. Thanks for the details. Since I'm usually using nunit, it's not that big a deal for me.
Btw, did you knwo the EF Team is plugging TDD.NET?
https://github.com/aspnet/EntityFramework/wiki/Getting-and-Building-the-Code

As for a workaround, just counting the classes was already my first idea before I read the rest of your reply. I'm thinking that this heuristic might just be finegrained enough. After all, the bar is just 100-120px wide, so with any reasonably sized project, you'd already get 100+ test classes and the bar would be as precise as it could be.


> I think this is kind of how the windows installer progress bar works
> (which is why it jumps around a lot).
Yeah, just recently had the same issue with a progress bar for doing HTTP transfer and working with the buffer size. Sometimes, progress will get messy :)

Best regards, Michael

Adam Ralph

unread,
Oct 6, 2015, 6:56:24 AM10/6/15
to TestDriven.NET Users
Is VS2015 support still in beta? Or does the stable release now support it?

Jamie Cansdale

unread,
Oct 6, 2015, 7:00:31 AM10/6/15
to TestDriven.NET Users
Hi Adam,

The VS 2015 support works fine and I wouldn't consider it Beta. This
version also supports NUnit 3.0 Beta 2, but the RTM version of NUnit
3.0 hasn't been released yet. I was holding off releasing an RTM
version until NUnit 3.0 was released.

I'm also in the middle of moving house, which doesn't help!

Regards,

Michael Ketting

unread,
Apr 4, 2016, 9:53:28 AM4/4/16
to TestDriven.NET Users
Hi Jamie!

Just noticed v3.9.2911 brings Options support for VS2015. Unfortunately, at least with VS2015 Update 2 Enterprise (didn't get to try it with Update 1), there is just a generic error message in the Options dialog ("An error occurred loading this property page"). Also, the About link is broken in VS2015, I only get a an error popup with the NullReferenceException message text.

Err... also, it looks like it broke the run-test context menus when I upgraded because all the TestDriven.NET commands are missing from the Solution Explorer and there is only a single "Abort Test Run" option in the Tools menu, and that one's grayed out. Do you have any suggestions about that one? Aside from resetting VS and hoping things get better?

Best regards, Michael

Michael Ketting

unread,
Apr 4, 2016, 10:36:28 AM4/4/16
to TestDriven.NET Users
Hi Jamie!
Okay, I can now confirm that things work with VS2015 Update 1. Unfortunately, Update 2 completely breaks things - verified on two seaprate machines where I did an upgrade from Update 1 to Update 2.
Best regards, Michael

Jamie Cansdale

unread,
Apr 4, 2016, 4:21:22 PM4/4/16
to TestDriven.NET Users
Thanks for letting me know! I'll investigate..

Crazy thing is, it works with VS 15:
https://twitter.com/jcansdale/status/716168444077613056

I wonder what is different in Update 2?
> Visit this group at https://groups.google.com/group/testdrivenusers.

Adam Ralph

unread,
Apr 4, 2016, 4:22:54 PM4/4/16
to TestDriven.NET Users
Hi Michael,

Thanks for the heads up. It seem like update 2 may be a can of worms right now, see also https://twitter.com/mat_mcloughlin/status/716608603579359232

Jamie Cansdale

unread,
Apr 4, 2016, 4:25:27 PM4/4/16
to TestDriven.NET Users
> Thanks for the heads up. It seem like update 2 may be a can of worms right
> now, see also https://twitter.com/mat_mcloughlin/status/716608603579359232
>
Not good. Has anyone else tried TD.Net on Update 2?

Thanks,
> Visit this group at https://groups.google.com/group/testdrivenusers.

Jamie Cansdale

unread,
Apr 5, 2016, 4:16:43 AM4/5/16
to TestDriven.NET Users
Hi Michael,

You have likely already done this, but if not, could you try running
the TestDriven.Net installer again on one of the machines with Update
2 on?

I've had one report of TestDriven.Net working with Update 2.
On 4 April 2016 at 15:36, Michael Ketting <michael...@rubicon.eu> wrote:
> Visit this group at https://groups.google.com/group/testdrivenusers.

Michael Ketting

unread,
Apr 5, 2016, 5:14:02 AM4/5/16
to TestDriven.NET Users
Hi Jamie!

Yep, tried to do a re-install as well as an uninstall and install. Am now also trying to do a blank installation of VS2015 Update 2 on another VM that hasn't had VS2015 before.

Best regards, Michael

Michael Ketting

unread,
Apr 5, 2016, 7:51:30 AM4/5/16
to TestDriven.NET Users
Okay, I think I know what's the difference:
* When using the update-2 option in the VS installer, it works.
* When doing a blank installation of VS2015+Update-2, it works.
* When downloading an updated installer ISO and installing via the setup from the ISO, TestDriven.NET is broken.

I'll try doing a repair installation next. If that doesn't help and there're no additional ideas, I'll go for broke and uninstall/install Visual Studio. At least, I can do a settings backup first :)

Best regards, Michael

Michael Ketting

unread,
Apr 5, 2016, 2:57:28 PM4/5/16
to TestDriven.NET Users
New update:
I've tried uninstalling/installing VS2015, but no luck. I also tried resetting VS settings, also no luck. On a hunch, I tried using a different Windows Account on the same machine, again, no luck (which is really weird). The one thing I haven't tried yet was to uninstall VS2015 Update 2 and installing VS2015 with Update 1. That's something I'll try sometime in the next day or so.

Anyway, it certainly looks like this isn't just some settings/registry key but it still has to surive the reinstall. Do you have any ideas?

Best regards, Michael

Jamie Cansdale

unread,
Apr 5, 2016, 6:37:39 PM4/5/16
to TestDriven.NET Users
Thank you very much for researching this! I'm on holiday with my 2
year old and the moment, so this really is a big help. :)

Any chance you could do the following:

1) Open Sysinternals' Process Monitor:
https://technet.microsoft.com/en-us/sysinternals/bb896645

2) Add the following filter:
'Process Name' is 'devenv.exe' then 'Include'

3) Open Visual Studio 2015 with Update 2

4) Save and send me a link to the log file.

My suspicion is that some interop assembly that TestDriven.Net depends
on has been dropped from the Visual Studio 2015 Update 2 installer.
The log file will hopefully show me what is going wrong.

Regards,
Jaime.

Michael Ketting

unread,
Apr 6, 2016, 3:52:18 AM4/6/16
to TestDriven.NET Users
You're welcome! And thanks for taking the time for this while relaxing :)

Sent you the link via direct mail. Looking forward to your findings. If you got some other ideas/requests, just let me know.

Best regards, Michael

Michael Ketting

unread,
Apr 7, 2016, 4:57:32 AM4/7/16
to TestDriven.NET Users
Update: Jamie and I managed to solve this via direct mail. The reason might not actually have been VS 2015 Update 2 but me installing it for single-user instead of machine wide. This resulted in some needed Registry keys (HKLM\SOFTWARE\Wow6432Node\MutantDesign\TestDriven.NET) missing.

Thanks for the great assisst, Jamie!

Best regards, Michael

Adam Ralph

unread,
Apr 7, 2016, 6:27:31 AM4/7/16
to TestDriven.NET Users
Great stuff guys!

So is this a problem that needs fixing in TD.NET, or is it simply unavoidable if VS 2015 is installed for all users, but then update 2 is installed for only a single user?
...

Michael Ketting

unread,
Apr 8, 2016, 2:15:22 AM4/8/16
to TestDriven.NET Users
VS can only be installed for all users. I haven't tried all the combinations, but it might be unavoidable with the current version of TD.NET if  you select the single-user option.

Best regards, Michael

Jamie Cansdale

unread,
Apr 8, 2016, 12:29:15 PM4/8/16
to TestDriven.NET Users
Once upon a time you could install TestDriven.Net using a limited user
account for just the current user. This might have been useful in
certain scenarios, say for students using Visual Studio on a shared
computer. Unfortunately the situation has changed in recent versions
of Visual Studio which make this no longer possible. I'm planning to
remove the (broken) option to install for just the current user.

This is the issue/bug that Michael found. If you install using the
default settings, TestDriven.Net will work fine with Visual Studio
2015 Update 2.

I hope that makes sense.

Regards,
Jamie.

Adam Ralph

unread,
Apr 10, 2016, 3:41:04 AM4/10/16
to TestDriven.NET Users
Thanks very much guys. Great work all round.
Reply all
Reply to author
Forward
0 new messages