R#6 integration in master
Vladimir Okhotnikov
Another issue is that R# 6 integration just does not work for me -
meaning that R# does not see the OW dependencies and highlights the
types and namespaces as errors even though both build-wrap and rebuild
in VS work.
Surely enough I tried purging everything I could find related to R#
caches (and in fact it did work with OW1 and R# 5.1). I also restarted
the VS, triggered the rebuilds and even compiled custom openwrap package
after updating the dlls in libs/resharper-6.0.0 with the ones from my
installation of R# (mine have the revision part of the version 688,
while the ones on github - 685). Still nothing helped.
Seems that I'm stuck and if anyone can advice how to fix that or tell me
what to do to provide more information to fix the problem - I will be
most grateful. Obviously, I know nothing about R# development - only
about using it :)
Regards,
Vladimir Okhotnikov
Sebastien Lambla
If you go to the output window, do you see the OpenWrap menu, and if yes, can you let me know what the output is? And can you let me know if you see the OpenWrap plugin in the ReSharper plugins (either in the about window, or resharper > options > plugins).
It's possible that I've built on top of what was supposed to be the RTM dlls, and JetBrains pulled the rug under my feet again and released a different build.
Vladimir Okhotnikov
answers inline
On 12.09.2011 23:52, Sebastien Lambla wrote:
> Ah that's interesting.
>
> If you go to the output window, do you see the OpenWrap menu, and if yes, can you let me know what the output is?
No, I only see 'Build' and 'Test' in the output window.
> And can you let me know if you see the OpenWrap plugin in the ReSharper plugins (either in the about window, or resharper> options> plugins).
About:
JetBrains ReSharper 6.0 Full Edition
Build 6.0.2202.688 on 2011-06-29T18:14:16
Plugins: none
Visual Studio 10.0.40219.1.
Copyright � 2003�2011 JetBrains s.r.o. All rights reserved.
R# - Options - Plugins says 'No plugins installed'
BTW, both VS and R# are installed to non-default location (too little
space on C:), can that have something to do with the issue?
Sebastien Lambla
What's supposed to happen when you update a project to 2.0 is that, once you've built once, the msbuild task kicks in, hooks itself in the VS process, add a solution addin to your solution and initialize OpenWrap from the COM world. If you don't have the output window, it means the msbuild task hasn't kicked in or the COM solution add-in didn't run properly. As the solution-level plugins are independent from resharper it's not a resharper issue.
So a few more things to check:
1. Is MSBuild running out of process for your build? See http://msdn.microsoft.com/en-us/library/ms171468.aspx for why you may be running out of process. There's a couple of things we're gonna do to make hooking up to VS possible from out of process scenarios (needed for the next version of VS), such as adding the solution addin manually when init-wrap is called and using out-of-process DTE, but so far it's not implemented.
2. Is the OpenWrap COM integration installed? You'd see it at HKCU/Software/Classes/OpenWrap.VisualStudioIntegration2010, if it's not there that could mean that either it didn't get installed or the install failed
3. Do you have both 3.5 and 4.0 installed or just one of the two?
I don't *think* there'd be a problem with having VS installed on another drive.
If all this fails, can you attempt opening up two instances of VS: Use the second one to debug the process of the first one, then open your solution in the first one and send me the debug output, that ought to give me an idea of what's going on.
Seb
-----Original Message-----
From: openwra...@googlegroups.com [mailto:openwra...@googlegroups.com] On Behalf Of Vladimir Okhotnikov
Sent: 12 September 2011 22:56
To: openwra...@googlegroups.com
Subject: Re: [openwrap-devl] R#6 integration in master
Hi
answers inline
On 12.09.2011 23:52, Sebastien Lambla wrote:
> Ah that's interesting.
>
> If you go to the output window, do you see the OpenWrap menu, and if yes, can you let me know what the output is?
No, I only see 'Build' and 'Test' in the output window.
> And can you let me know if you see the OpenWrap plugin in the ReSharper plugins (either in the about window, or resharper> options> plugins).
About:
JetBrains ReSharper 6.0 Full Edition
Build 6.0.2202.688 on 2011-06-29T18:14:16
Plugins: none
Visual Studio 10.0.40219.1.
Copyright (c) 2003-2011 JetBrains s.r.o. All rights reserved.
Vladimir Okhotnikov
surprised :)
I have added the following to .csproj
> <Target Name="BeforeBuild">
> <Error Text="InProcess" Condition="$(BuildingInsideVisualStudio)"/>
> </Target>
And got the error on rebuild, which must mean that msbuild is running
inside VS if I understood the link correctly.
I have actually edited openwrap.cshrap.targets like this
> <InitializeVisualStudioIntegration
> EnableVisualStudioIntegration="$(OpenWrap-EnableVisualStudioIntegration)"
> />
> <Error Text="Integration enabled" Condition="$(OpenWrap-EnableVisualStudioIntegration)"/>
And got the error (even 2 instances in fact) after I've done a rebuild
in a solution with 2 projects. Still no OpenWrap in output window.
> 2. Is the OpenWrap COM integration installed? You'd see it at
HKCU/Software/Classes/OpenWrap.VisualStudioIntegration2010, if it's not
there that could mean that either it didn't get installed or the install
failed
There is no such branch in the registry.
> 3. Do you have both 3.5 and 4.0 installed or just one of the two?
I believe both (don't really remember, but our primary development is
for 3.5)
It seems I have isolated the problem... the thing is I'm always running
the VS as admin (it is required for our web projects which are hosted in
IIS). The setting is set in the compatibility tab of the studio startup
shortcut, so I'm not even always remembering about it...
Anyway, I have cleared the checkbox, run the studio non-elevated and
after the rebuild I've got the OW tab with messages in it. R#
integration is working in non-elevated environment as well.
Now, if it just worked as well in elevated case... I really need to run
it as admin most of the time.
Regards,
Vladimir Okhotnikov
Sebastien Lambla
It could be that in admin mode the HKCU points to a different part of the registry and the COM registration fails, preventing VS from calling up the COM object successfully.
I'll have a test tonight and see how it goes.
Vladimir Okhotnikov
does just the same).
Regards,
Vladimir Okhotnikov