-
Notifications
You must be signed in to change notification settings - Fork 69
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
IntelliSense is broken in VS #44
Comments
Did this work for you before? If so, has anything changed since it last worked? |
The last time it worked a long time ago. |
As I already know, I have had problems with registry keys and R installation path detection.
|
Can you check if RDotNet.Fsharp.dll is present in the Rprovider directory. Howard On Oct 4, 2013, at 7:31 PM, Sergey Tihon notifications@github.com wrote: As I already know, I have had problems with registry keys and R Error 2 The type provider 'RProvider.RProvider' reported an error: [image: image]https://f.cloud.github.com/assets/1197905/1273576/0477b43e-2d4d-11e3-8ea0-9a55565449c4.png — |
All assemblies in place. #I @"bin/Debug/"
#r @"RDotNet.NativeLibrary.dll"
#r @"RDotNet.dll"
#r @"RDotNet.FSharp.dll"
#r @"RProvider.dll"
... I was able to catch following exception
So now I see the same behavior in VS debugger and new console app with |
Finally, I have found the source of the issue. This is a message from
The full log you can find in the gist. |
It sounds like you need to reset the devpath in the .NET Reflector Visual Studio extension. You can do this by clicking 'Reset the DEVPATH' under the .NET Reflector menu in Visual Studio. At the moment Visual Studio is looking in the folder specified by the devpath for the RProvider dll, rather than the directory you actually put it. Reflector sets the devpath if it has previously had to regenerate an assembly in order to change the assembly GUIDs to match those specified in the corresponding PDB generated by Reflector. |
Hmm, that's strange.. If you look at the environment variables directly, is the DEVPATH environment variable set? If so, you can delete it manually, this should have the same affect as resetting the devpath in the VS extension. |
I see the following error when I try to script using
RProvider
(VS2012 Update 3).All required assemblies are located in the same folder with
RProvider.dll
.The script is following
The text was updated successfully, but these errors were encountered: