Wierdness observed, suggestions??

I have testdriven.net, ghostdoc and resharper installed as VS2003 addins. There were installed in that order. Recently I've observed some wierdness and would like your comments as to what it could be.

Since yesterday I've been getting the following error message. I can't Identify any other 'user' of the file.

Could not write to output file 'C:\Documents and Settings\pprice\My Documents\Visual Studio Projects\Api\library\obj\Debug\library.dll' -- 'The process cannot access the file because it is being used by another process. '


Also, since yesterday - and I don't recall playing with any setting that might have turned this on - I have little green circles with some figure inside, and an up arrow right next to it (I think) w/ tooltalk that says 'Implements method from interface IInterfaceName.XYZ' Probably this is a feature, because it's true. I don't see any way to turn the little green circles off - and I find them distracting.

Of further concern - the last time I deleted the impacted dll, so that it could be rebuilt, VS2003 suddenly couldn't 'see' and unrelated source code file. It was there in the filesystem - a 'search files and folders' turned it up, just where it was expected to be - but VS2003 continued to disagree that there was a file of that name in that location.

I ended up copying it to another location, deleting it from the project, then copying it back to it's location and adding it.

So - known issues? Do a virus scan immediately? VS2003 just be's that way sometimes?

Thanks,

MarFarMa

2 comments
Comment actions Permalink

Hello Pauli,

please look at my comments inline.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I have testdriven.net, ghostdoc and resharper installed as VS2003
addins. There were installed in that order. Recently I've observed
some wierdness and would like your comments as to what it could be.

Since yesterday I've been getting the following error message. I
can't Identify any other 'user' of the file.

Could not write to output file 'C:\Documents and Settings\pprice\My
Documents\Visual Studio Projects\Api\library\obj\Debug\library.dll' --
'The process cannot access the file because it is being used by
another process. '



It is difficult to find the true source of this problem. There is a known
issue with
VS 2003 with assembly locking - take a look at this article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;313512


Also, since yesterday - and I don't recall playing with any setting
that might have turned this on - I have little green circles with some
figure inside, and an up arrow right next to it (I think) w/ tooltalk
that says 'Implements method from interface IInterfaceName.XYZ'
Probably this is a feature, because it's true. I don't see any way to
turn the little green circles off - and I find them distracting.


Yes, it's definitely a feature of ReSharper. And, frankly speaking, nobody
before found it distracting. I'm afraid there is no way to disable it
without
disabling the entire ReSharper's highlighing which can be done via
ReShaper|Options|Highlighting|Enable ...


Of further concern - the last time I deleted the impacted dll, so that
it could be rebuilt, VS2003 suddenly couldn't 'see' and unrelated
source code file. It was there in the filesystem - a 'search files
and folders' turned it up, just where it was expected to be - but
VS2003 continued to disagree that there was a file of that name in
that location.

I ended up copying it to another location, deleting it from the
project, then copying it back to it's location and adding it.



More information about this issue is needed, but it hardly relates to
ReSharper
at the first glance. Can you repeat it and describe in more detail?


0
Comment actions Permalink

Thank you for the reference to the KB article. It appears to be my situation exactly. I had turned copy local off - due to this issue in FitNess:


+“Most likely this is a dll problem. Since VS, by default, copies dlls
into your project's debug folder, two versions of fit.dll end get
loaded during test execution. .NET chokes with this.

Try removing fit.dll from fitnesse\dotnet or set the "copy local"
option for the fit.dll reference to false.

Micah Martin
Object Mentor, Inc.
www.objectmentor.com”+


whereas, this alternate solution does the trick:

The other thing you can do is make sure that you
explicitly name all of
the DLLs:

!define COMMAND_PATTERN {%m %p}
!define TEST_RUNNER {dotnet\FitServer.exe}
!define PATH_SEPARATOR {;}
!path dotnet\fit.dll
!path c:\path\to\my\project\bin\Debug\myProject.dll



As for the margin green dot markers - I guess I can live with them. The thing I find so annoying about them is I can't quite make out the graphic. The figure in the circle, and the arrow (I think it's an arrow) are so small on my monitor, at the resolution I'm working at, that it's illegible. As it is, I find myself straining at them, as if, if only I looked at them longer, I could make out the graphic.

I hope not to duplicate the missing source code problem. I like to think that it's a side effect of the VS2003 bug referenced above, and now that I have the workaround implemented, I won't see it again.

MarFarMa

0

Please sign in to leave a comment.