.NET Reflector is adjustin your solution to allow all refere

• 
  ya, i wasn't too happy. it not only 'adjusted' my solution, it 'adjusted' the references in my project files, which broke several of them by adding the 'embed interop' flag. :x

  blindahl November 17, 2009 10:59

  - 0 +
• 
  Hi, thanks for the comments, sorry I've taken so long to reply, I've been away.
  
  In fact the only thing reflector is doing when it adjusts your solution is moving references around. It is much less reliable, and takes longer, for websites than for normal solutions. It can also sometimes break some custom properties of the references, like the "embed interop" flag, as you say.
  
  It should only take a minute in the worst case though, so there is definitely a bug you've found using it on your website. If you can narrow down a reproduction situation to something you'd be willing to send me, that'd be very useful.
  
  We are considering how worthwhile it is to automatically retarget your references rather than asking you to do it manually. It would be a lot of work for you to do it manually, and would be too unusable for a lot of people. What do you think?
  
  Thanks,

  Alex D November 23, 2009 08:15

  - 0 +
• 
  IMHO, anything that changes my project files so that it builds differently than how i had it set up is a very bad thing. My references are like they are for a reason - usually because I need to bind to certain versions of the referenced assemblies.
  
  If it means not being able to debug quite as easily, then that's what i'll have to put up with.

  blindahl November 23, 2009 10:25

  - 0 +
• 
  We have now redesigned the regeneration system, so that you are given the choice of whether to let .NET Reflector try to reset your project references. It puts control over the regeneration in your hands.
  
  Let me know what you think,

  Alex D December 08, 2009 06:24

  - 0 +

Add comment

Please sign in to leave a comment.