Jeff Saurik [1] talks about Anakrino release 10 and it working with .NET v1.1. I can say it sure works with v1.1; that's not the problem, as I ran it for a long time on my WinXP box with both VS.NET 2002 and the Everett betas and RCs without a hitch.
What does happen is that in my experience, it will always crash on Windows Server 2003. I've never managed to run it here, fwiw.
Update: for what it's worth, exemplar still works when run from the command line directly. No nice GUI, but it's better than nothing :)
[1] Great all-around guy; met him a couple years back at a Microsoft
1 Comment
archived from WordPress — closedI have the very same experience with Windows Server 2003.
FWIW, I've managed to replicate the same error msg I get in Win03 in Win XP... twice... using differing methods.
The first method consisted of manually adding an entry to the assemblies node in the anakrino.xml file. The entry pointed to an assembly Anakrino would have no idea where it was kept. Saving the file and launching Anakrino caused it to crash immediately.
Secondly, I've found that the order in which the .NET Frameworks are installed seems to be paramount. After blasting my Win XP system a couple of months ago, I installed the Everett beta first (with dotnetfx v1.1), followed by VS .NET 2002 (with dotnetfx v1.0). Anakrino always crashed whenever I tried to launch it. I fixed this solution by uninstalling both frameworks and installing them in numerical order (v1.0 and then v1.1). After installation, Anakrino worked without a hitch.
Interestingly, I blasted my Win XP system again this morning. I've just installed VS .NET 2003 RTM with dotnetfx v1.1. There is no dotnetfx v1.0 on this system. Anakrino crashes.
I wonder what Jay makes of this...