I installed the latest binaries from
http://xunitcontrib.codeplex.com/releases/view/35006
and followed the suggestions from
http://xunitcontrib.codeplex.com/Thread/View.aspx?ThreadId=79225
because the linked installation instructions are out of date (basically there are more libs to copy to the plugins dir)
Now my resharper shows the plugin in the Plugins diialog, but I have no testing functionality at all. Not even Testdriven.NET seems to recognize the xunit tests (even if I "reinstalled" them via the xunit.installer.exe).
What a drag! Anyone can give me a hand here?
--Jan
A I guess, I just forgot one of the dlls.
Now I have got it working.
Related
I've installed Eclipse 4.2 Juno. Now I want to install aptana for developing ruby, but I get the following error,
Unable to read repository at http://download.aptana.com/studio3/plugin/install/content.jar.
Unable to read repository at http://download.aptana.com/studio3/plugin/install/content.jar.
Read timed out
I assume that by now you have probably solved the problem, but I had exactly the same problem and found the solution after many searches, so for the sake of any others searching here...
The URL you need to enter in the 'Install New Software' dialog is
http://download.aptana.com/studio3/plugin/install
The following answer was correct. I just tested it with Eclipse Juno.
Steps:
Open Eclipse
Help -> Install New Software
Add (on the top right)
Enter the following link for Aptana Plugin with Eclipse Juno: http://download.aptana.com/studio3/plugin/install
Click OK
Put a check mark for Aptana Studio 3
Next -> Next -> Finish
download.aptana.com/studio3/plugin/install did not work for me. I am using Eclipse 4.3 based STS 3.4
Instead I got the appropriate update site link from this site Aptana Update Site
This is the link for Eclipse plugin update site http://d1iwq2e2xrohf.cloudfront.net/tools/studio/plugin/install/studio3/3.4.2.201308081736/
There is also a link to download the plugin and install through archive. I have used the above update site link and no problem at all.
Hope that will help others.
Adding this answer in case somebody still gets this error while using the correct URL from JonB's answer (http://download.aptana.com/studio3/plugin/install )
Restart Eclipse and try again.
This appears to be a transient issue, as mentioned here:
Aptana studio 3 cannot contact download.ecplise.org
It worked for me after a retry.
I also gone through same problem. But Following solution works for me,
In Eclipse, go to "Eclipse Marketplace" and search for Aptana 3 and hit the Install button.
Help -> Eclipse MarketPlace
Eclipse Market place - Aptana 3 Studio plugin
I wondered myself whether to install the standalone or the plugin. I tried the plugin based on aptanaès instructions and it failed on the first try.
As usual SO respondents reported this problem.
I restarted Eclipse, and then did the install with Aptanaès URL
http://download.aptana.com/studio3/plugin/install
and it worked.
My environment was Eclipse JUNO,
As of 01/29/18 and Eclipse Photon, none of the URLs listed as answers here work in Eclipse's built-in software sources panel. However, after some trial and error mashing up Aptana's old download URLs with the ones Appcelerator (which bought Aptana in 2015) uses for its own software, I got:
http://download.appcelerator.com/aptana/studio3/plugin/update/stable
This works, is totally plug-and-play, and is obviously official - no need to go off to some shady 3rd party hosting site. I just wish someone at Appcelerator had spent 15 minutes to post it somewhere.
Is there a way to make visual studio not care about dll versions? Is this a bad idea?
I am resetting up my dev machine and I just installed the latest version of Pex and Moles (version .92). All my projects are on version .91.
We are in the middle of a release and don't want to upgrade right now. Also, I cannot find an installer to version .91.
When I try to compile I get a message that I am missing the reference. (Hence this question)
The version is important.. By definition, there is a difference from each released version to the next (or there would be no need for a new version). Your program may not perform correctly if you are expecting one version and instead have another.
This was a part of what was known as "DLL Hell" in the pre-.NET days... If you needed to use a third party component (Crystal Reports Viewer is one we always had to deal with), you would just use the reference to whatever installed version was on the user's PC. Our retail locations had to have a specific version of Crystal Reports for their bookwork reports to print correctly, and because of that, we had to hold on to an old version forever.. Upgrading Crystal on the PC broke the vendor's bookwork app. On my first ever PC, I had several applications break when I would install or upgrade another. In particular, Real Player broke my telephone answering machine software. Goofy stuff like that...
So, the version IS important, even if it is an annoyance. It's also why I have a bias against third party tools that I have no code for, and can't recompile myself.
If you look at the properties of a referenced DLL, you will see a property "Specific Version". If you set it false, it doesn't track the specific version in the project file.
For this to work, you have to somehow fix the references where ever they are used. You can do this by opening every solution and fixing the references (at which time you could also just update the references to the correct version, paying heed to David's comments).
If you have a lot of solutions, you might use a tool like sed (see this post for windows versions of tool like this Is there any sed like utility for cmd.exe) to just update the project files as needed all at once.
I've been using Scala 2.8RC1 and Scala Eclipse plugin for 2.8 RC1 happily for a few days. However, last night after adding a couple jar files to my environment (apache http client jars) the debugger just stopped stopping at breakpoints in scala code.
Java code stops fine at breakpoints. I tried creating a new mimimal scala app breakpoints don't stop. I've tried switching to sun-jre-1.6.0.20 from the openjdk-1.6.18 I had been using. I've switched to the scala 2.8 nightly and also eclipse plugin for scala nightly builds. No luck.
I would greatly appreciate ideas for fixes. Rather frustrating as the initial experience with 2.8 was really great.
https://www.assembla.com/spaces/scala-ide/tickets/2731-breakpoints-against-objects-in-default-package-are-not-honoured
Says that scala eclipse plugin doesn't stop at breakpoints if you're class is in the default package (no package)
Adding a package and moving my class to it - make the debugger start working again.
It's possible that you've discovered a bug in the Scala tooling for Eclipse. The best place to take the issue is the scala-ide-user list here,
http://groups.google.com/group/scala-ide-user
If you're already sure that you've found a bug you can find instructions for opening a ticket here,
http://scala-ide.assembla.com/wiki/show/scala-ide/Bug_Reporting
I've just encountered this problem. Code is not in default package. I'm getting a warning about missing line numbers, but apparently that bug has been fixed and I can ignore the warning, per https://scala-ide-portfolio.assembla.com/spaces/scala-ide/tickets/1000155-its-impossible-to-add-line-numbers-debug-info-to-compiled-project#/activity/ticket:
It did seem to stop at breakpoints in the main file, though.
Today I had a problem with my old Eclipse 3.4 installation and I had to re-download the entire package. However, I don't think that I got the exact package as before, and I'm having some problems.
The problem can be summarized as follows: when developing a plug-in, I cannot resolve dependencies towards 'org.eclipse.jdt.ui'. When trying to add the missing plugin, in the dialog the closest match is 'org.eclipse.jdt.ui**.source**'. A similar thing happens with other core plugins.
In order to test, I created a new plug-in using the wizard and I obtained a non-compiling plugin: one of the classes uses the class org.eclipse.jdt.ui.JavaUI and it cannot be resolved. Similarly, the MANIFEST.MF includes a dependency towards 'org.eclipse.jdt.ui', but the 'Bundle 'org.eclipse.jdt.ui' cannot be resolved'.
Now a summary of my platform:
I'm running Mac OS X 10.4 Tiger and Java 1.5.0_19-138
I'm running Eclipse Version: 3.4.1 Build id: M20080911-1700
I downloaded the modeling package, which comes in a file called 'eclipse-modeling-ganymede-SR1-incubation-macosx-carbon.tar.gz'
I've performed a fresh installation, in a new folder and using a new workspace.
If I look at the Plug-in Registry view, I can find the 'org.eclipse.jdt.ui' plugin in there, and it appears to be running. By the way, if it is disabled, then the workbench breaks and stops working.
I cannot understand what is happening. Is my installation broken? I wonder if the Eclipse package that I downloaded has an error and they included the sources instead of the compiled files. But in that case, the plug-in shouldn't be working in the workbench, isn't it?
In any case, why I cannot find the plug-in when I'm adding the dependencies, even if I see it in the Plug-in Registry?
Thanks for your help!
Problem solved: just restart the computer.
I don't restart my computer very frequently, so it took me a lot of time to find out that this was the solution. After I restarted it, everything started to work perfectly again. It seems that either Eclipse leaves something in the memory after running, or that some of my initial failures had left something nasty behind. In any case, I had checked and there were no Eclipse related processes running .... weird, but at least now it's fixed!
I am aware that the current release of PEX allows use with the NUnit framework.
The thing is I can't configure it to use the NUnit framework.
In the Options -> PEX: What Exactly do i have to put in the "TestFramework" and "TestFrameworkDirectory".
I Have tried many combinations but failed to achieve any success.
I've went to the DevLabs forum in search for a solution, I've got a solution to the problem.
Here it is:
http://social.msdn.microsoft.com/Forums/en-US/pex/thread/5f7cc37d-0b8e-4bad-af6f-c53c5076e7c2
You have to set the "TestFramework" option to "NUnit" (without quotes) and the "TestFrameworkDirectory" option to the directory where the nunit.framework.dll file is located (if you used the .msi installer it's probably "%ProgramFiles%\NUnit x.y.z\bin\net-2.0\framework").