Comments
4 comments
-
bjoern,
I assume you're talking about when reflector pro offers to switch your project to reference regenerated assemblies? I can't think of how reflector pro would try to write to the csproj file without wanting to make a change from how it was before. It should just skip over changing any references in your csproj files that are already right.
As a workaround, could you answer "no" when the prompt appears, if you know that there actually aren't any changes to make?
Cheers, -
When I select assemblies for decompilation the first time, it adds the following tags to the csproj file:
<UseVSHostingProcess>true</UseVSHostingProcess>
When I add another assembly for decompilation at a later point in time and it's finished decompiling it, I get the checkout dialog from my source control. When I actually check it out and compare the two versions, nothing changed.
For a test, I just removed that tag and added another assembly for decompilation and this line got then added to the csproj file again.
As a workaround, you're absolutely right, I can just cancel the checkout operation, get a little error message, but then everything works just fine. So it's not blocking me from using Reflector Pro, it would just be awesome to get rid of that checkout attempt. -
Ah, I see. If you switch off the VS hosting process and close and open VS with it switched off, reflector pro shouldn't try to touch it anymore.
The reason that it needs modifying is that we switch it off and on again if it's on, to make it let go of file handles that often stop reflector pro from working.
Let me know if that helps, -
gotcha. Yes, that did indeed fix it.
That was a really quick fix
Add comment
Please sign in to leave a comment.
everything works really well in the last build that I'm using (914), I have only one last wish before you take it out of Beta:
When the decompilation process is finished, you're trying to modify the csproj file. Which I guess, the first time, it's fine, because you're adding that one tag. But every subsequent time that I modify something in the decompilation dialog the csproj file wants to be changed again, even though nothing gets changed.
Now, it would be awesome if you could avoid the subsequent change requests, because my source control system wants to checkout the file every time. I could cancel the checkout, but I get the un-beautiful "error" then that the command could not be completed. And if I do checkout the file, I either need to undo the checkout or get an error during checkin that the file hasn't changed.
I hope you can follow
Thanks!